Extension registration issue

[Rob Lloyd]

I had a working system yesterday. Today when I went to check it all my extensions are unregistered and I'm getting 404 not found errors. I can verify that port 5060 is open, my polycom phones are downloading the config files from the tftp directory. XLite is also showing 404.

 

Here is the log file from a phone:

[7] 2008/08/18 20:46:47: SIP Rx udp:192.168.2.53:5060:

REGISTER sip:192.168.2.9:5060 SIP/2.0

Via: SIP/2.0/UDP 192.168.2.53;branch=z9hG4bK722d0ef046C1FE17

From: "500" <sip:500@192.168.2.9>;tag=EA77FDDB-92205626

To: <sip:500@192.168.2.9>

CSeq: 1 REGISTER

Call-ID: ea1787b2-dadb9cb1-d1523344@192.168.2.53

Contact: <sip:500@192.168.2.53>;methods="INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER"

User-Agent: PolycomSoundPointIP-SPIP_550-UA/3.0.3.0401

Max-Forwards: 70

Expires: 3600

Content-Length: 0

 

 

[7] 2008/08/18 20:46:47: SIP Tx udp:192.168.2.53:5060:

SIP/2.0 404 Not Found

Via: SIP/2.0/UDP 192.168.2.53;branch=z9hG4bK722d0ef046C1FE17

From: "500" <sip:500@192.168.2.9>;tag=EA77FDDB-92205626

To: <sip:500@192.168.2.9>;tag=6d75a189fc

Call-ID: ea1787b2-dadb9cb1-d1523344@192.168.2.53

CSeq: 1 REGISTER

Content-Length: 0

 

Any idea what is going on? I have restarted the service and also the server with the same results. I was using the latest 2.0 version and swtiched to version 3. Replacing the 2.0 version back yields the same results.

 

Thanks,

Rob

[Vodia PBX]

I had a working system yesterday. Today when I went to check it all my extensions are unregistered and I'm getting 404 not found errors. I can verify that port 5060 is open, my polycom phones are downloading the config files from the tftp directory. XLite is also showing 404.

 

...

 

Any idea what is going on? I have restarted the service and also the server with the same results. I was using the latest 2.0 version and swtiched to version 3. Replacing the 2.0 version back yields the same results.

 

You can check if there is another process using port 5060 by running netstat (same in Windows and Linux). Sometimes there are softphones which like to sit on that port.

 

If the port 5060 is really taken by the PBX, then check if you have a domain name or alias "localhost". Maybe you changed the name of the domain and then the PBX gets picky with the Request-URI.

[Rob Lloyd]

netstat shows 5060 being used by pbxctrl.exe so I'm not sure what is happening. I can port ping 5060 to the server IP and that works. xlite and my phones still show 404 not found and why would the pbxnsip log files show the same? What can't it find?

 

I can receive calls so I know the service is working.

[Vodia PBX]

netstat shows 5060 being used by pbxctrl.exe so I'm not sure what is happening. I can port ping 5060 to the server IP and that works. xlite and my phones still show 404 not found and why would the pbxnsip log files show the same? What can't it find?

 

I can receive calls so I know the service is working.

 

What about the domain name?

[Rob Lloyd]

I just checked incoming calls again. They re-route to my cell phone and voicemails work fine and get emailed correctly. Just no phone registrations.

 

This is on an SBS2003 server so the domain has not changed - I'm registering to an IP and not a name anyway.

[Vodia PBX]

I just checked incoming calls again. They re-route to my cell phone and voicemails work fine and get emailed correctly. Just no phone registrations.

 

This is on an SBS2003 server so the domain has not changed - I'm registering to an IP and not a name anyway.

 

I mean the domain name in the PBX, not in the server. Typically "localhost", see http://wiki.pbxnsip.com/index.php/Domain.

[Rob Lloyd]

Thanks! that was it. I didn't think renaming that would be a problem. Being a windows guy i was thinking windows domains.