Re: [Sip-implementors] few queries regarding SDP implementation formultiple bit rates for g.722 codec

2007-08-07 Thread Attila Sipos
m=audio 9292 RTP/AVP 9 a=rtpmap:9 G722/48000 a=rtpmap:9 G722/56000 a=rtpmap:9 G722/64000 I'm not sure this would always work as desired. I think the effect will be that a receiver of this SDP will just end up selecting the last one in the list. Also, I think the rates are incorrect. The number

[Sip-implementors] Special Information Tones

2007-08-07 Thread Hari Vuppaladhadiam
Hi I wanted to understand when is SIT (Special Information Tone) played? Is this the error tone for BAd/Non-Existing number? Can anyone point me to relevant RFC? Regards Hari ___ Sip-implementors mailing list

Re: [Sip-implementors] few queries regarding SDP implementation formultiple bit rates for g.722 codec

2007-08-07 Thread Roman Shpount
Hi All, m=audio 9292 RTP/AVP 9 a=rtpmap:9 G722/48000 a=rtpmap:9 G722/56000 a=rtpmap:9 G722/64000 This is definitely incorrect. The only clock rate supported by G.722 is 16KHz, which should be specified as 8KHz for compatibility reasons (see RFC 3551 4.5.2). This means the offer should be:

Re: [Sip-implementors] Special Information Tones

2007-08-07 Thread Bayan Towfiq
Hari, Yes, an example of where a SIT tone is used on the PSTN would be when the caller has dialed a bad or non-existing number. The SIT tone is generally played on the PSTN before a failure announcement. ITU recommendation E.182 defines tones that should be heard by the caller in various

Re: [Sip-implementors] RE-INVITE Problem [packet capture inside]

2007-08-07 Thread Dale . Worley
From: Stefan Sayer [EMAIL PROTECTED] The offerer may change the stream, but the answerer? Uh, yes. I answered a different question than was asked. In regard to how the answer may be different from the offer, the rules are in section 6.1 of RFC 3264. In many cases, the answerer may add

Re: [Sip-implementors] RE-INVITE Problem [packet capture inside]

2007-08-07 Thread Paul Kyzivat
Dale has covered this. For the original poster, Stefan: there is a lot of written information on this subject that you don't seem to be familiar with. The most obvious are RFCs 3261 and 3264. For a more complete treatment, see