Hi, RFC 3555: annexb: indicates that Annex B, voice activity detection, is used or preferred. Permissible values are "yes" and "no" (without the quotes); "yes" is implied if this parameter is omitted.
So, Snom phone support G.729ab codec. Best Regard Bao Jianyi -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aswin Bhupalam Sent: Tuesday, July 19, 2005 1:17 PM To: [email protected] Cc: Sushil (E-mail); Uttam Kumar Sarkar Subject: [Sip-implementors] G 729 a & b negotiation All, say "a=" line is not having 'annexb' parameter, which one(g729a or g729b) should we take as default. Snom phone sends an INVITE with the following SDP: v=0 o=root 743184990 743184990 IN IP4 10.50.10.146 s=call c=IN IP4 10.50.10.146 t=0 0 m=audio 10014 RTP/AVP 18 101 a=rtpmap:18 g729/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv Which codec is being negotiated here?(g729a or g729b) Dave, I found your mail regarding the same question. kindly let me know if you've found something useful. Regards, Aswin Bhupalam. -----Messaggio originale----- Da: sip-implementors-bounces at cs.columbia.edu [mailto:sip-implementors-bounces at cs.columbia.edu] Per conto di David Stuart Inviato: giovedì 8 luglio 2004 20.10 A: sip-implementors at cs.columbia.edu Oggetto: [Sip-implementors] g729 annex B negotiation Hi All, What is the correct way to negotiate annex B when using g.729 (as opposed to A)? They both use the same payload type, 18. I see two different mentions of this, RFC 3555 section 4.1.9, and RFC 3108 sec 5.6.3.2 but they seem to be saying different things. Can anyone point me to the correct example as to how to achieve this? -- David Stuart, SIPquest Email: dave (at) sipquest (dot) com Phone: 254-8886 x234 Web: http://www.sipquest.com/ Address: 106 - 350 Terry Fox Drive, Kanata Ontario, K2K 2P5 _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
