[Asterisk-Users] SPA 2000 and 404 not found

[John Todd]

> 
>                                                                                             
>I have a Sipura SPA2000 2 line SIP FXS box with line 1 on port 5060 and line 2
>on 5061. The SPA2000 is on IP address 192.168.17.6, and the asterisk box is
>on 102.168.17.2. Both SPA2000 ports(5060 and 5061) share the same IP address.
>Every minute I repeatedly get the following output:
>
>SIP Debugging Enabled
>10 headers, 0 lines
>Reliably Transmitting:
>OPTIONS sip:192.168.17.6 SIP/2.0
>Via: SIP/2.0/UDP 192.168.17.2:5060;branch=z9hG4bK60fe7596
>From: "asterisk" <sip:asterisk at 192.168.17.2>;tag=as1cf7898d
>To: <sip:192.168.17.6>
>Contact: <sip:asterisk at 192.168.17.2>
>Call-ID: 21b130083154c5857b62f0386128fe01 at 192.168.17.2
>CSeq: 102 OPTIONS
>User-Agent: Asterisk PBX
>Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
>Content-Length: 0
> 
>                                                                                             
>  (no NAT) to 192.168.17.6:5060
>10 headers, 0 lines
>Reliably Transmitting:
>OPTIONS sip:192.168.17.6:5061 SIP/2.0
>Via: SIP/2.0/UDP 192.168.17.2:5060;branch=z9hG4bK0178ca1c
>From: "asterisk" <sip:asterisk at 192.168.17.2>;tag=as6a42fcc6
>To: <sip:192.168.17.6:5061>
>Contact: <sip:asterisk at 192.168.17.2>
>Call-ID: 0e03dbf26416538d39ff24477a86d0fd at 192.168.17.2
>CSeq: 102 OPTIONS
>User-Agent: Asterisk PBX
>Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
>Content-Length: 0
> 
>                                                                                             
>  (no NAT) to 192.168.17.6:5061
>Sip read:
>SIP/2.0 404 Not Found
>To: <sip:192.168.17.6>
>From: "asterisk" <sip:asterisk at 192.168.17.2>;tag=as1cf7898d
>Call-ID: 21b130083154c5857b62f0386128fe01 at 192.168.17.2
>CSeq: 102 OPTIONS
>Via: SIP/2.0/UDP 192.168.17.2:5060;branch=z9hG4bK60fe7596
>Server: Sipura/SPA2000-1.0.9
>Content-Length: 0
> 
>                                                                                         
>
>8 headers, 0 lines
>Sip read:
>SIP/2.0 404 Not Found
>To: <sip:192.168.17.6:5061>
>From: "asterisk" <sip:asterisk at 192.168.17.2>;tag=as6a42fcc6
>Call-ID: 0e03dbf26416538d39ff24477a86d0fd at 192.168.17.2
>CSeq: 102 OPTIONS
>Via: SIP/2.0/UDP 192.168.17.2:5060;branch=z9hG4bK0178ca1c
>Server: Sipura/SPA2000-1.0.9
>Content-Length: 0
> 
>                                                                                             
> 
>                                                                                             
>8 headers, 0 lines
> 
>                                                                                             
>*CLI> sip no debug
>SIP Debugging Disabled
>
>
>Here's what's in sip.conf:
>
>[general]
>port=5060
>bindaddr=192.168.17.2
>tos=lowdelay
>disallow=all
>allow=ulaw
>context=default
>;
>
>; SIP Entry for sipura line 1
>; This phone is allowed to dial extensions and local phone numbers
>;
>[101]
>type=friend
>host=dynamic
>context=house-toll
>reinvite=no
>canreinvite=no
>qualify=300
>secret=xxxxxx
>callerid="Sipura Line 1" <101>
>username=101
>mailbox=101
>
>; Sample for sipura line 2
>; This phone is allowed to dial extensions and local phone numbers
>;
>[102]
>type=friend
>host=dynamic
>context=house-toll
>reinvite=no
>canreinvite=no
>qualify=300
>secret=yyyyyy
>callerid="Sipura Line 2" <102>
>username=102
>mailbox=102
>nat=0
>
>
>Note that 192.168.17.6:5061 seems to have a problem with "404 not found",
>wheras 192.168.17.6:5060 does not.
>
>Could Asterisk be getting confused about a device with two ports sharing the
>same IP address? I don't seem to be seeing any traffic being logged from the
>SPA2000 to Asterisk; it all seems to be going from 192.168.17.2 to
>192.168.17.6. If anyone could shed some light on what is going on here it
>would be sincerely appreciated.
>
>Steve Rodgers
>San Diego, CA
>

The symptoms are caused by your "qualify=" lines.  Every 60 seconds, 
an "OPTIONS" request is sent from Asterisk to the destination.  I 
don't seem to see evidence that supports your statement that packets 
to the 5060 port works and 5061 doesn't; it appears that both 
requests are sending back the same 404 error.

This is a bug with the Sipura; actually, more like a missing feature. 
I would say "Don't worry about it" since the added traffic keeps your 
NAT mappings in place.  I'm sure Sipura will come up with a patch if 
you and all your friends send in bugnotes to them.

JT