when I make a call using S60, the S60 receives 200 ok with SDP, and it sends out ack message, but after about 30 seconds, it sends out bye.
Can anybody tell me what is the criteria to drop a call?
when I make a call using S60, the S60 receives 200 ok with SDP, and it sends out ack message, but after about 30 seconds, it sends out bye.
Can anybody tell me what is the criteria to drop a call?
" when I make a call using S60, the S60 receives 200 ok with SDP, and it sends out ack message, but after about 30 seconds, it (the S60 originated the session i.e. UAC?) sends out bye. Can anybody tell me what is the criteria to drop a call?"
So what happens here is that the S60 calls some other client, gets 200 OK, sends SIP ACK? Audios are OK in both direction? After 30s the S60 (UAC, the S60 originated the call) sends SIP BYE without any user action?
The 30s timeout is too short that this would be due a SIP transaction timeout due to broken SIP message routing inside the session, and also in that case the BYE would have been sent by UAS due it has not got the ACK. There would also be re-transmissions of the 200 OK not mentioned, and thus if I interpreted the sentense above correctly this is not the case.
Another possibility could be that the RTCP is activated with the client provisioning (e.g. via OMA DM) and no RTCP RR packets are received, either the other client does not support RTCP, blocked by a firewall or dropped a NAT device (due the public port for the RTCP may be different than RTP port+1). If RTCP is enabled, disabling it might help.
It is possible that there is some other reason, as in many other cases, the IP logs might help.