Hello Nitin Kapoor,
If you remove G723 from the first offer then the re-invite will be avoided and you do have time to find out why SBC is rejecting the re-invite with 488. The maxptime:30 is there because of G723. As the answer choose G729 now maxptime must be reduced to 20. Regards! Valdemar -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Pavesi, Valdemar (NSN - US/Irving) Sent: Wednesday, November 30, 2011 5:14 PM To: ext Nitin Kapoor Cc: [email protected]; [email protected] Subject: Re: [Sip-implementors] 488 Not Acceptable Here A-side: 1_OFFER: v=0 o=Sonus_UAC 16515 29422 IN IP4 209.58.46.49 s=SIP Media Capabilities c=IN IP4 209.58.46.40 t=0 0 m=audio 11516 RTP/AVP 4 18 101 a=rtpmap:4 G723/8000 a=fmtp:4 bitrate=6.3 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=maxptime:30 1_ANSWER: v=0 o=MSCUSA02 0 0 IN IP4 66.165.172.105 s=sip call c=IN IP4 200.182.99.92 t=0 0 m=audio 37540 RTP/AVP 18 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no 2_OFFER: v=0 o=Sonus_UAC 16515 29423 IN IP4 209.58.46.49 s=SIP Media Capabilities c=IN IP4 209.58.46.40 t=0 0 m=audio 11516 RTP/AVP 18 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=sendrecv a=maxptime:20 SIP/2.0 488 Not Acceptable Here Via: SIP/2.0/UDP 209.58.46.49:5060;branch=z9hG4bK02B20d77dccba82feaf To: <sip:[email protected]>;tag=3530024869-419042 From: <sip:[email protected]>;tag=gK027a69ac Call-ID: [email protected] CSeq: 22385 INVITE Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE, MESSAGE, PUBLISH Contact: <sip:[email protected]:5060> Call-Info: <sip:66.165.172.105>;method="NOTIFY;Event=telephone-event;Duration=1000" Content-Length: 0 Based on msg there are no reason to reject it by SIP/2.0 488 Not Acceptable Here ++++++++++++++++++++ B_SIDE: sip.Call-ID == [email protected] No. Time Source Destination Protocol Info 3 3.065749 66.165.172.105 89.221.47.103 SIP/SDP Request: INVITE sip:[email protected], with session description 4 3.112791 89.221.47.103 66.165.172.105 SIP Status: 100 Trying 5 7.545399 89.221.47.103 66.165.172.105 SIP/SDP Status: 180 Ringing, with session description 7 15.350865 89.221.47.103 66.165.172.105 SIP/SDP Status: 200 OK, with session description 8 15.351406 66.165.172.105 89.221.47.103 SIP Request: ACK sip:[email protected]:5060 17 915.748573 66.165.172.105 89.221.47.103 SIP Request: BYE sip:[email protected]:5060 18 915.897753 89.221.47.103 66.165.172.105 SIP Status: 200 OK We do see the SDP-ANSWER , one on 180 and a new OFFER from b-side on 200ok. Sdp_answer from 180 : v=0 o=- 262762 262762 IN IP4 89.221.47.103 s=IMSS c=IN IP4 89.221.47.103 t=0 0 m=audio 14238 RTP/AVP 18 101 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=fmtp:18 annexb=no sdp_answer from 200ok: v=0 o=- 262762 262763 IN IP4 89.221.47.103 s=IMSS c=IN IP4 89.221.47.103 t=0 0 m=audio 14238 RTP/AVP 18 101 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=fmtp:18 annexb=no ++ o=- 262762 262762 IN IP4 89.221.47.103 o=- 262762 262763 IN IP4 89.221.47.103 In reality the rfc says : " if media session is the same the session-version must remains" Regards! Valdemar From: ext Nitin Kapoor [mailto:[email protected]] Sent: Wednesday, November 30, 2011 2:56 PM To: Pavesi, Valdemar (NSN - US/Irving) Cc: [email protected]; [email protected] Subject: Re: [Sip-implementors] 488 Not Acceptable Here Hello Valdemar,. Yes i do have. I am attaching the filtered traces. Thanks, Nitin On Wed, Nov 30, 2011 at 3:52 PM, Pavesi, Valdemar (NSN - US/Irving) <[email protected]> wrote: Hello Nitin Kapoor, Do you have the first OFFER and ANSWER ? The first offer CODECS: 4 18 101 , we have to see the ANSWER , at moment looks ok , the session-ID is "o=Sonus_UAC 16515 29422" v=0 o=Sonus_UAC 16515 29422 IN IP4 209.58.46.49 s=SIP Media Capabilities c=IN IP4 209.58.46.40 t=0 0 m=audio 11516 RTP/AVP 4 18 101 a=rtpmap:4 G723/8000 a=fmtp:4 bitrate=6.3 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=maxptime:30 now the second OFFER , by re-invite codec G729 , the CODEC now is a new One and the maxptime can be changed to 20 , and the session-ID tell us that there is a new offer , session-id increase " o=Sonus_UAC 16515 29423" v=0 o=Sonus_UAC 16515 29423 IN IP4 209.58.46.49 s=SIP Media Capabilities c=IN IP4 209.58.46.40 t=0 0 m=audio 11516 RTP/AVP 18 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=sendrecv a=maxptime:20 +++++++++++++++++++++ G723 --> packetization period can be 10 , 20 , 30 ms G729 --> The max packetization period is 20 ms +++++++++++++++++++++ Codec Information Bandwidth Calculations Codec & Bit Rate (Kbps) Codec Sample Size (Bytes) Codec Sample Interval (ms) Mean Opinion Score (MOS) Voice Payload Size (Bytes) Voice Payload Size (ms) Packets Per Second (PPS) Bandwidth MP or FRF.12 (Kbps) Bandwidth w/cRTP MP or FRF.12 (Kbps) Bandwidth Ethernet (Kbps) G.711 (64 Kbps) 80 Bytes 10 ms 4.1 160 Bytes 20 ms 50 82.8 Kbps 67.6 Kbps 87.2 Kbps G.729 (8 Kbps) 10 Bytes 10 ms 3.92 20 Bytes 20 ms 50 26.8 Kbps 11.6 Kbps 31.2 Kbps G.723.1 (6.3 Kbps) 24 Bytes 30 ms 3.9 24 Bytes 30 ms 33.3 18.9 Kbps 8.8 Kbps 21.9 Kbps G.723.1 (5.3 Kbps) 20 Bytes 30 ms 3.8 20 Bytes 30 ms 33.3 17.9 Kbps 7.7 Kbps 20.8 Kbps G.726 (32 Kbps) 20 Bytes 5 ms 3.85 80 Bytes 20 ms 50 50.8 Kbps 35.6 Kbps 55.2 Kbps G.726 (24 Kbps) 15 Bytes 5 ms 60 Bytes 20 ms 50 42.8 Kbps 27.6 Kbps 47.2 Kbps G.728 (16 Kbps) 10 Bytes 5 ms 3.61 60 Bytes 30 ms 33.3 28.5 Kbps 18.4 Kbps 31.5 Kbps G722_64k(64 Kbps) 80 Bytes 10 ms 4.13 160 Bytes 20 ms 50 82.8 Kbps 67.6Kbps 87.2 Kbps ilbc_mode_20(15.2Kbps) 38 Bytes 20 ms NA 38 Bytes 20 ms 50 34.0Kbps 18.8 Kbps 38.4Kbps ilbc_mode_30(13.33Kbps) Regards! Valdemar -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of ext Nitin Kapoor Sent: Wednesday, November 30, 2011 1:53 PM To: [email protected] Cc: [email protected] Subject: [Sip-implementors] 488 Not Acceptable Here Dear Friends, I am facing the problem with one of my customer where first the calls has been connected successfully and then UAC sends the re-invite my SBC sends 488 back to UAC. When UAC sends the Initial OFFER i had below SDP. (UAC --- SBC) and i can see the "ptime" value is 30 and calls established. v=0 o=Sonus_UAC 16515 29422 IN IP4 209.58.46.49 s=SIP Media Capabilities c=IN IP4 209.58.46.40 t=0 0 m=audio 11516 RTP/AVP 4 18 101 a=rtpmap:4 G723/8000 a=fmtp:4 bitrate=6.3 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=maxptime:30 Now when UAC sends the re-invite we have below SDP. If you can see in re-invite "ptime" value has been changed.. Is that acceptable? Or you have seen any other thing in SDP. v=0 o=Sonus_UAC 16515 29423 IN IP4 209.58.46.49 s=SIP Media Capabilities c=IN IP4 209.58.46.40 t=0 0 m=audio 11516 RTP/AVP 18 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=sendrecv a=maxptime:20 Could anyone please give some shadow on this. Thanks in Advance. Regards, Nitin Kapoor _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
