[asterisk-dev] SIP DTMF INFO Singal-Update?

[Victor Toofic]

Hi!

Sometimes I get the message: "WARNING[4232]: chan_sip.c:8847
handle_request_info: Unable to retrieve DTMF signal from INFO message"
because in the body of the message there is a "Signal-Update" instead of
"Signal".

Im wondering what's the difference between "Signal" and "Signal-Update" in
the body of a DTMF INFO message? I think Im having some troubles because
of that.

Would be trivial to add "Signal-Update" to the code? or are there other
things that should be considered?

--
Thanks..
Victor Toofic


-- SIP/GSX_MTY-0062c420 answered SIP/5060-ae20c770
-- Attempting native bridge of SIP/5060-ae20c770 and SIP/GSX_MTY-0062c420
<-- SIP read from 200.XXX.XXX.103:5060:
INFO sip:8147776391 at 200.XXX.XXX.179:5060 SIP/2.0
Via: SIP/2.0/UDP 200.XXX.XXX.103:5060;branch=z9hG4bK05B3c8750e5d75d9476
From: <sip:018002668377 at 200.XXX.XXX.103>;tag=gK059e75f9
To: "8147776391" <sip:8147776391 at 200.XXX.XXX.179>;tag=as590f7015
Call-ID: 1473cbfe791b6ab04bbacc4d281d1c8e at 200.XXX.XXX.179
CSeq: 32167 INFO
Max-Forwards: 70
Content-Length:   27
Content-Type: application/dtmf-relay

Signal= 1
Duration= 2600

--- (9 headers 2 lines) ---
Receiving INFO!
* DTMF-relay event received: 1
Transmitting (no NAT) to 200.XXX.XXX.103:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 200.XXX.XXX.103:5060;branch=z9hG4bK05B3c8750e5d75d9476;received=200.XXX.XXX.103
From: <sip:018002668377 at 200.XXX.XXX.103>;tag=gK059e75f9
To: "8147776391" <sip:8147776391 at 200.XXX.XXX.179>;tag=as590f7015
Call-ID: 1473cbfe791b6ab04bbacc4d281d1c8e at 200.XXX.XXX.179
CSeq: 32167 INFO
User-Agent: Prepago 
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Contact: <sip:8147776391 at 200.XXX.XXX.179>
Content-Length: 0
X-Asterisk-HangupCause: Normal Clearing


---
set_destination: Parsing <sip:8147776391 at 200.XXX.XXX.103:5060> for address/port to send to
set_destination: set destination to 200.XXX.XXX.103, port 5060
Reliably Transmitting (no NAT) to 200.XXX.XXX.103:5060:
INFO sip:8147776391 at 200.XXX.XXX.103:5060 SIP/2.0
Via: SIP/2.0/UDP 200.XXX.XXX.179:5060;branch=z9hG4bK7a0dba83;rport
From: <sip:018002668377 at 200.XXX.XXX.179:5060>;tag=as6f830f95
To: <sip:8147776391 at 200.XXX.XXX.103:5060;bgid=16780900;bgt=public>;tag=gK0631d1a4
Contact: <sip:018002668377 at 200.XXX.XXX.179>
Call-ID: 134623513_12713 at 200.XXX.XXX.103
CSeq: 102 INFO
User-Agent: Prepago 
Max-Forwards: 70
Content-Type: application/dtmf-relay
Content-Length: 24

Signal=1
Duration=250

---
<-- SIP read from 200.XXX.XXX.103:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 200.XXX.XXX.179:5060;branch=z9hG4bK7a0dba83;rport=5060
From: <sip:018002668377 at 200.XXX.XXX.179:5060>;tag=as6f830f95
To: <sip:8147776391 at 200.XXX.XXX.103:5060;bgid=16780900;bgt=public>;tag=gK0631d1a4
Call-ID: 134623513_12713 at 200.XXX.XXX.103
CSeq: 102 INFO
Content-Length: 0


--- (7 headers 0 lines) ---
<-- SIP read from 200.XXX.XXX.103:5060:
INFO sip:8147776391 at 200.XXX.XXX.179:5060 SIP/2.0
Via: SIP/2.0/UDP 200.XXX.XXX.103:5060;branch=z9hG4bK05B3c881c77d75d9476
From: <sip:018002668377 at 200.XXX.XXX.103>;tag=gK059e75f9
To: "8147776391" <sip:8147776391 at 200.XXX.XXX.179>;tag=as590f7015
Call-ID: 1473cbfe791b6ab04bbacc4d281d1c8e at 200.XXX.XXX.179
CSeq: 32168 INFO
Max-Forwards: 70
Content-Length:   33
Content-Type: application/dtmf-relay

Signal-Update= 1
Duration= 305

--- (9 headers 2 lines) ---
Receiving INFO!
2007-11-30 11:17:00 WARNING[4232]: chan_sip.c:8847 handle_request_info: Unable to retrieve DTMF signal from INFO message from 1473cbfe791b6ab04bbacc4d281d1c8e at 200.XXX.XXX.179
Transmitting (no NAT) to 200.XXX.XXX.103:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 200.XXX.XXX.103:5060;branch=z9hG4bK05B3c881c77d75d9476;received=200.XXX.XXX.103
From: <sip:018002668377 at 200.XXX.XXX.103>;tag=gK059e75f9
To: "8147776391" <sip:8147776391 at 200.XXX.XXX.179>;tag=as590f7015
Call-ID: 1473cbfe791b6ab04bbacc4d281d1c8e at 200.XXX.XXX.179
CSeq: 32168 INFO
User-Agent: Prepago 
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Contact: <sip:8147776391 at 200.XXX.XXX.179>
Content-Length: 0
X-Asterisk-HangupCause: Normal Clearing