Dear Experts,
Can anyone explain me the reason for sending BYE by UAC. I want to know ,if UAC doesnot support "TIMER" functionality whether UAS can send this session expires with support of "timer" in 200ok.is this the reason for sending BYE by UAC. Call flow is like this: INVITE--->NormalSIP Calling 100; Trying<---NormalSIP Calling 183; Session Progress<---NormalSIP Invitation Proceeding 180; Ringing<---NormalSIP Invitation Proceeding 200; Ok<---NormalSIP Invitation Completed ACK--->NormalSIP Session Initiated BYE--->NormalSIP Request Proceeding 200; Ok<---End Request Line INVITE sip:[email protected];user=phone SIP/2.0 Headers From: <sip:[email protected];user=phone>;tag=0300633414 To: <sip:[email protected];user=phone> Max-Forwards: 70 Via: SIP/2.0/UDP ALMAS6.KCELL.KZ:5060;branch=z9hG4bK00000039090783838013 Call-ID: [email protected] CSeq: 52353 INVITE P-Asserted-Identity: <sip:[email protected];user=phone> Accept: application/sdp Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,PRACK,UPDATE P-Charging-Vector: icid-value=281C56A100-0217-16340205;icid-generated-at=ALMAS6.KCELL.KZ Supported: 100rel Content-Type: application/sdp Contact: <sip:ALMAS6.KCELL.KZ:5060;transport=UDP> Content-Length: 427 Status Line SIP/2.0 200 Ok Headers From: <sip:[email protected];user=phone>;tag=0300633414 To: <sip:[email protected];user=phone>;tag=SDocc6098-ds-6937c38b-4f297aae642e8 Via: SIP/2.0/UDP ALMAS6.KCELL.KZ:5060;received=10.6.64.110;branch=z9hG4bK00000039090783838013 Call-ID: [email protected] CSeq: 52353 INVITE Content-Length: 274 Content-Type: application/sdp Session-Expires: 1800;refresher=uas Supported: timer Contact: <sip:[email protected]:5060;transport=udp> Regards Sampat _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
