] Getting SIP Response Code from HANGUPCAUSE
The only place where it is reasonable to customize is in the
specification of the channel in the configuration file.
That is where
you would customize, for example, whether DTMF is inband,
SIP INFO, or
RFC 2833, as well as what codecs
Well, unfortunately for you, that is the exact opposite of
the philosophy of the Asterisk codebase. Every attempt is
made to genericize the channel driver interface so that you
do not need to know the details of the underlying driver.
Where we have failed to do so in the past, we are
.
- Raj
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Philipp Kempgen
Sent: Friday, October 26, 2007 11:37 AM
To: Asterisk Users
Subject: Re: [asterisk-users] Getting SIP Response Code from
HANGUPCAUSE
Eric ManxPower Wieling wrote:
On 10
On Saturday 27 October 2007 08:14:05 Torbjörn Abrahamsson wrote:
Well, unfortunately for you, that is the exact opposite of
the philosophy of the Asterisk codebase. Every attempt is
made to genericize the channel driver interface so that you
do not need to know the details of the
The only place where it is reasonable to customize is in the
specification of the channel in the configuration file.
That is where
you would customize, for example, whether DTMF is inband,
SIP INFO, or
RFC 2833, as well as what codecs will be negotiated for that
particular
I think you can use the 'ngrep' command to see the sip packets coming in
using the sip listening port. I dont know the exact command though, you will
have to lookit up urself. you will see the sip packets coming into ur system
and in those packets you can see the response code.
On 10/25/07,
Rizwan Hisham wrote:
I think you can use the 'ngrep' command to see the sip packets coming in
using the sip listening port. I dont know the exact command though, you will
have to lookit up urself. you will see the sip packets coming into ur system
and in those packets you can see the response
Eric ManxPower Wieling wrote:
On 10/25/07, Douglas Garstang [EMAIL PROTECTED] wrote:
I'd like to grab the SIP response code that comes back from an INVITE. The
HANGUPCAUSE gives the converted ISDN cause code. Anyone know of a way to get
the SIP response code instead?
There is an RFC for
, October 26, 2007 6:18:50 AM
Subject: Re: [asterisk-users] Getting SIP Response Code from HANGUPCAUSE
I think you can use the 'ngrep' command to see the sip packets coming in using
the sip listening port. I dont know the exact command though, you will have to
lookit up urself. you will see the sip
On Friday 26 October 2007 16:13:11 Douglas Garstang wrote:
Thanks. I am quite familiar with ngrep. I was asking how I could get the
SIP response code from the dial plan.
You cannot. And you shouldn't have to. The dialplan should be generic
to all protocols, not customized to SIP.
--
Tilghman Lesher wrote:
On Friday 26 October 2007 16:13:11 Douglas Garstang wrote:
Thanks. I am quite familiar with ngrep. I was asking how I could get the
SIP response code from the dial plan.
You cannot. And you shouldn't have to. The dialplan should be generic
to all protocols,
On Friday 26 October 2007 19:47:27 SIP wrote:
Tilghman Lesher wrote:
On Friday 26 October 2007 16:13:11 Douglas Garstang wrote:
Thanks. I am quite familiar with ngrep. I was asking how I could get the
SIP response code from the dial plan.
You cannot. And you shouldn't have to. The
SIP wrote:
Tilghman Lesher wrote:
On Friday 26 October 2007 16:13:11 Douglas Garstang wrote:
I was asking how I could get the
SIP response code from the dial plan.
You cannot. And you shouldn't have to. The dialplan should be generic
to all protocols, not customized to SIP.
That's
I'd like to grab the SIP response code that comes back from an INVITE. The
HANGUPCAUSE gives the converted ISDN cause code. Anyone know of a way to get
the SIP response code instead?
Doug.
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the
14 matches
Mail list logo
