[asterisk-dev] chan_sip.c - no reply to critical packet
damin at nacs.net
Sat Jan 31 12:04:52 CST 2009
> > [Jan 30 10:49:49] Receiving INFO!
> > [Jan 30 10:49:49] Transmitting (no NAT) to 126.96.36.199:5060:
> > SIP/2.0 403 Unauthorized
> > Via: SIP/2.0/UDP 188.8.131.52:5060;x-ds0num="ISDN 1/0:23 1/0:DS1
> > 17:DS0";branch=z9hG4bK9724104E;received=184.108.40.206
> > From: <sip:2164864965 at 220.127.116.11>;tag=5BD698E8-75
> > To: <sip:2169203080 at 18.104.22.168>;tag=as7f89f1a4
> > Call-ID: 7592F3FA-EE1C11DD-8E78B0F4-24748FB1 at 22.214.171.124
> > CSeq: 102 INFO
> > User-Agent: N2Net Univoice
> > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
> > Content-Length: 0
> This INFO message, and the subsequent 403 response, did not show up in
> your call trace, but they are in the debug log. My suspicion is that
> Asterisk 1.2 is getting confused by the reception of the INFO message
> when the dialog establishment has not been completed yet.
I think I found the source of the issue..
During the initial invite the RPID is set to:
<sip:4404530804 at 126.96.36.199>;party=calling;screen=yes;privacy=off
The Info packet contains an update to the RPID line:
Remote-Party-ID: "Cell Phone OH"
So.. there has to be a way to have the Cisco wait to initiate the SIP call
until the Q.931 data is received so that the RPID is sent in the initial
Anyone have any ideas?
More information about the asterisk-dev