[asterisk-dev] chan_sip.c - no reply to critical packet

[Gregory Boehnlein]

> > [Jan 30 10:49:49] Receiving INFO!
> > [Jan 30 10:49:49] Transmitting (no NAT) to 207.166.192.180:5060:
> > SIP/2.0 403 Unauthorized
> > Via: SIP/2.0/UDP  207.166.192.180:5060;x-ds0num="ISDN 1/0:23 1/0:DS1
> > 17:DS0";branch=z9hG4bK9724104E;received=207.166.192.180
> > From: <sip:2164864965 at 207.166.192.180>;tag=5BD698E8-75
> > To: <sip:2169203080 at 207.166.192.174>;tag=as7f89f1a4
> > Call-ID: 7592F3FA-EE1C11DD-8E78B0F4-24748FB1 at 207.166.192.180
> > 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:

Remote-Party-ID: "pending"
<sip:4404530804 at 207.166.192.180>;party=calling;screen=yes;privacy=off

The Info packet contains an update to the RPID line:

Remote-Party-ID: "Cell Phone   OH"
<sip:207.166.192.180>;party=called;screen=no;privacy=off

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
invite....

Anyone have any ideas?