Hi Uttam, Here is my SBC, even is not forwarding the call to leg 2... Its first sending the 100 Trying in the correspondence of Initial Invite and then immediately sending 488 back to source UA.
UA -------- INVITE---------------------- SBC UA <---------100 Trying----------------SBC UA<--488 Not Acceptable Here ---SBC what i feel that due to list of codec....PACKET size is getting increased hence it sending 488.. So if its not sending the call to leg2, then how it can select the choose the codec. Could you please correct me if i am wrong.. Also, i am currently checking the points you mentioned. Thanks, Nitin Kapoor On 30 July 2010 13:49, Uttam Sarkar (usarkar) <[email protected]> wrote: > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of > Nitin Kapoor > Sent: Friday, July 30, 2010 1:36 PM > To: [email protected] > Subject: [Sip-implementors] RTP payload list in OFFER > > Dear All, > > I am facing the issue with my SBC, where my source is sending me the > complete list of RTP payload and my SBC is returning back 488 Not > Acceptable > here. > > v=0 > o=BroadWorks 148094714 1 IN IP4 209.58.101.249 > s=- > c=IN IP4 195.189.150.38 > t=0 0 > m=audio 6300 RTP/AVP 18 0 8 35 36 2 38 39 40 41 42 43 44 45 46 47 4 80 3 > 56 > 118 101 > a=rtpmap:118 G729B/8000/1 > a=fmtp:118 annexb=yes > [US] Isn't payload type 18 specifies that g729. Why payload type 118 is > doing the same. > a=rtpmap:101 telephone-event/8000 > a=fmtp:101 0-15 > a=rtpmap:120 no-op/8000 > [US] I don't see any reference of 120 in the m line. > > Your SBC should choose the codec from the list and answer the call with > that codec. > > Now when i checked the IANA RTP payload list, and observed that most of > them > are still unassigned. Could anyone please check the above SDP and > payload...and please help me whether it is correct to send 488 to > source...or not. > > And also if anything wrong in above, so please pinpoint it. I also feel > that > because of this CODEC packet size is increasing and causing the issue. > > Thanks, > 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
