The basic thing is CALLEE has to take the subset of codecs offered by CALLER and reply back. But in your case, CALLEE is replying with different set of codecs (97 101) in reply to CALLER codecs ( 102 0 8 106 ) IMHO, since the capabilities mis-match, immdiately end the call using BYE / CANCEL which ever is relevant.
Somesh -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of ext friend friend Sent: Monday, April 27, 2009 2:59 PM To: sip fourm Subject: [Sip-implementors] Query for SDP Negotiation Dear Folks, I have doubt in the following scenario. Caller's sdp : v=0 o=- 1234 1 IN IP4 10.10.20.35 s=- c=IN IP4 10.10.20.35 t=0 0 m=audio 12000 RTP/AVP 102 0 8 106 a=rtpmap:102 iLBC/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:106 telephone-event/8000 Callee's negotiated sdp : v=0 o=- 3449811996 3449811996 IN IP4 10.10.20.4 s=SJphone c=IN IP4 10.10.20.4 t=0 0 m=audio 49164 RTP/AVP 97 101 c=IN IP4 10.10.20.4 a=rtpmap:97 iLBC/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=setup:active a=sendrecv In this case,Is callee's negotiation method is wrong? Callee should send like m=audio 49164 RTP/AVP 102 106 rite? In this case, after call establishment, from caller sending RTP using 102 (UnKnown) from callee sending RTP using 97 (iLBC) So caller hearing callee's audio but callee not able to hear caller's audio. please clarify this issue. Thanks & Regards, vijay Bring your gang together. Do your thing. Find your favourite Yahoo! group at http://in.promos.yahoo.com/groups/ _______________________________________________ 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
