Re: [Sip-implementors] Registration with Authentication scenario

2009-01-26 Thread cool goose
Thank You Dale. On Mon, Jan 26, 2009 at 8:24 AM, Dale Worley wrote: > On Sun, 2009-01-25 at 01:23 -0800, cool goose wrote: > > In this scenario, what is the expected response from UAS? Do the UAS > needs > > to send 401 Unauthorized or 403 Forbidden? If the UAS responds with 403 > > Forbidden, i

Re: [Sip-implementors] Is RFC 2833 a MUST in sending DTMF?

2009-01-26 Thread Johansson Olle E
26 jan 2009 kl. 17.28 skrev Dale Worley: > On Mon, 2009-01-26 at 09:32 +0100, Iñaki Baz Castillo wrote: >> AFAIK some PSTN gateways expect DTMF via RFC2833 but ufortunatelly >> I've not found one of these yet. > > The sipX open-source PBX uses RFC 2833 exclusively. We've found that > all SIP pho

Re: [Sip-implementors] Is RFC 2833 a MUST in sending DTMF?

2009-01-26 Thread Dale Worley
On Mon, 2009-01-26 at 09:32 +0100, Iñaki Baz Castillo wrote: > AFAIK some PSTN gateways expect DTMF via RFC2833 but ufortunatelly > I've not found one of these yet. The sipX open-source PBX uses RFC 2833 exclusively. We've found that all SIP phones support RFC 2833. Many PSTN gateways do also, i

Re: [Sip-implementors] Registration with Authentication scenario

2009-01-26 Thread Dale Worley
On Sun, 2009-01-25 at 01:23 -0800, cool goose wrote: > In this scenario, what is the expected response from UAS? Do the UAS needs > to send 401 Unauthorized or 403 Forbidden? If the UAS responds with 403 > Forbidden, is it valid for the UAC to retry the registration? Retrying after a 403 is not li

Re: [Sip-implementors] Is RFC 2833 a MUST in sending DTMF?

2009-01-26 Thread Scott Lawrence
On Mon, 2009-01-26 at 12:31 +0530, Hasini Gunasinghe wrote: > Hi All, > > In my sip soft phone application, I send DTMF using RFC 2976 (through sip > info message). That works fine and it is related to the SIP stack of our > application. > My questions are: > 1). In implementing the DTMF sending

Re: [Sip-implementors] Is RFC 2833 a MUST in sending DTMF?

2009-01-26 Thread Maxim Sobolev
Johansson Olle E wrote: > audio. Sending DTMF without timestamps and in a different signalling > path totally removes the relation to the audio stream. Well, arguably not much relation to audio stream is really needed for DTMF applications. Relative events ordering, not absolute timestamps, is

Re: [Sip-implementors] Is RFC 2833 a MUST in sending DTMF?

2009-01-26 Thread Maxim Sobolev
Hasini Gunasinghe wrote: > Hi All, > > In my sip soft phone application, I send DTMF using RFC 2976 (through sip > info message). That works fine and it is related to the SIP stack of our > application. > My questions are: > 1). In implementing the DTMF sending functionality, is it a must that we

Re: [Sip-implementors] Is RFC 2833 a MUST in sending DTMF?

2009-01-26 Thread Johansson Olle E
26 jan 2009 kl. 09.32 skrev Iñaki Baz Castillo: >> 2). Which method is more preferred in the context of a SIP Soft phone >> application? and Why? Remember that SIP and RTP sometimes travels different paths. For many applications, it is important that DTMF is timed with the rest of the audio.

Re: [Sip-implementors] Is RFC 2833 a MUST in sending DTMF?

2009-01-26 Thread Iñaki Baz Castillo
2009/1/26 Hasini Gunasinghe : > Hi All, > > In my sip soft phone application, I send DTMF using RFC 2976 (through sip > info message). That works fine and it is related to the SIP stack of our > application. > My questions are: > 1). In implementing the DTMF sending functionality, is it a must that