[v164]

I still can't receive an ENUM call via SipBroker. However, I noticed the modem light flashing, showing the UDP packet arriving. For some reason, my ATA was not accepting the call. To get to the bottom of the matter, I captured some of these packets and analysed the contents. Below are the SIP "INVITE" messages that arrived.


050xxxxxxxx is my 050 phone number
xxx.xxx.xxx.xxx is my public IP address
6173305xxxx is my PSTN number, which is mapped to

sip:050xxxxxxxx@xxx.xxx.xxx.xxx

at e164.org


Here are the SIP "INVITE" messages that arrived...

<< test call via e164.org - this works >>

INVITE sip:050xxxxxxxx@xxx.xxx.xxx.xxx SIP/2.0
Via: SIP/2.0/UDP 204.50.80.11:5060;branch=z9hG4bK042cc19c
From: "6044845289" <sip:6044845289@204.50.80.11>;tag=as056c135d
To: <sip:050xxxxxxxx@xxx.xxx.xxx.xxx>
Contact: <sip:6044845289@204.50.80.11>
Call-ID: 5d6...edited.out...48@204.50.80.11
CSeq: 102 INVITE
User-Agent: Asterisk PBX
Date: Sun, 02 Apr 2006 11:45:49 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
Content-Type: application/sdp
Content-Length: 289


I then used Voxalot Web Callback to get an incoming call via SIP Broker. For "Your Number", I entered 6173305xxxx, via SIP Broker, and for "Number to Dial", I entered 15166875089 (an ENUM test number), via SIP Broker.

<< call using SIP broker. My ATA ignores this; it doesn't ring >>

INVITE sip:050xxxxxxxx@xxx.xxx.xxx.xxx SIP/2.0
Record-Route: <sip:24.196.79.163;ftag=as6e3737c3;lr=on>
Via: SIP/2.0/UDP 24.196.79.163;branch=z9hG4bK2618.863f3e15.0
Via: SIP/2.0/UDP 71.13.117.133:5061;branch=z9hG4bK3ad516b5;rport=50 61
From: "<my 6-digit Voxalot user ID>" <sip:blah@sipbroker.com>;tag=as6e3737c3
To: <sip:*0136173305xxxx@sipbroker.com>
Contact: <sip:blah@71.13.117.133:5061>
Call-ID: 0e3...edited.out...61d@sipbroker.com
CSeq: 102 INVITE
User-Agent: Asterisk PBX
Max-Forwards: 16
Date: Sun, 02 Apr 2006 12:09:38 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length: 338



The key difference seems to be in the "To: " line.

(Edited 2006-05-28: the problem is actually the "lr=on" part of the Record-Route header - see subsequent post for details)

Test call from e164.org:

To: <sip:050xxxxxxxx@xxx.xxx.xxx.xxx>


Test call from SIPBroker:

To: <sip:*0136173305xxxx@sipbroker.com>


It seems that my ATA looks at the "To: " line, says to itself "I'm not *0136173305xxxx@sipbroker.com", and ignores it.

So that seems to be the cause of the problem. But is the fault with SIP Broker, or with my ATA?