cmrabet Posted November 26, 2008 Report Share Posted November 26, 2008 I Just installed PBXnSIP in Linux (Ubuntu 8.10 64bits) which is aparantly working pretty good. However I can't make my phisical SIP phone to register, also SJPhone is not registering saying that the service is not avaibale. What I have done so far is just create a domain (localhost) and then 1 account (extension). I set the user account name, the password, etc.. in both SIP phisical phone and software SIP phone correctly, however neither of them can register to the PBX server. I checked my NETSTAT -a command, and there are several SIP processes listening (I don't have anything else installed in the server that is using SIP protocol). Also I checked that the port 5060 is opened in the server side since "telnet <server_ip> 5060" is working, and both SIP phones are in the same local network as the server and they can reach it. Is there something I am missing? Thanks and regards, Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted November 26, 2008 Report Share Posted November 26, 2008 I Just installed PBXnSIP in Linux (Ubuntu 8.10 64bits) which is aparantly working pretty good. However I can't make my phisical SIP phone to register, also SJPhone is not registering saying that the service is not avaibale. What I have done so far is just create a domain (localhost) and then 1 account (extension). I set the user account name, the password, etc.. in both SIP phisical phone and software SIP phone correctly, however neither of them can register to the PBX server. I checked my NETSTAT -a command, and there are several SIP processes listening (I don't have anything else installed in the server that is using SIP protocol). Also I checked that the port 5060 is opened in the server side since "telnet <server_ip> 5060" is working, and both SIP phones are in the same local network as the server and they can reach it. Turn SIP logging on and check if you see the REGISTER packets in the log file. If that is not the case, you are still wrestling with the IP subsystem setup. Quote Link to comment Share on other sites More sharing options...
cmrabet Posted November 26, 2008 Author Report Share Posted November 26, 2008 Turn SIP logging on and check if you see the REGISTER packets in the log file. If that is not the case, you are still wrestling with the IP subsystem setup. This is what the PBXnSIP log says about SIP registering (192.168.1.139 is the Phisical SIP phone IP): [9] 2008/11/26 14:16:22: SIP Rx udp:192.168.1.139:5060: REGISTER sip:192.168.1.3:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.139:5060;branch=z9hG4bK28008695836932320;rport From: Chakir Mrabet <sip:100@192.168.1.3:5060>;tag=628526938 To: Chakir Mrabet <sip:100@192.168.1.3:5060> Call-ID: 257201465-1550022549@192.168.1.139 CSeq: 1 REGISTER Contact: <sip:100@192.168.1.139:5060> Max-Forwards: 70 Expires: 60 User-Agent: Voip Phone 1.0 Content-Length: 0 [9] 2008/11/26 14:16:22: Resolve 176: aaaa udp 192.168.1.139 5060 [9] 2008/11/26 14:16:22: Resolve 176: a udp 192.168.1.139 5060 [9] 2008/11/26 14:16:22: Resolve 176: udp 192.168.1.139 5060 [9] 2008/11/26 14:16:22: SIP Tx udp:192.168.1.139:5060: SIP/2.0 404 Not Found Via: SIP/2.0/UDP 192.168.1.139:5060;branch=z9hG4bK28008695836932320;rport=5060 From: Chakir Mrabet <sip:100@192.168.1.3:5060>;tag=628526938 To: Chakir Mrabet <sip:100@192.168.1.3:5060>;tag=71e0278d27 Call-ID: 257201465-1550022549@192.168.1.139 CSeq: 1 REGISTER Content-Length: 0 It seems that the network is working properly between PBXnSIP server and local SIP phones, because they can see each other, but I still don't understand why the phone can't register. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted November 26, 2008 Report Share Posted November 26, 2008 This is what the PBXnSIP log says about SIP registering (192.168.1.139 is the Phisical SIP phone IP): [9] 2008/11/26 14:16:22: SIP Rx udp:192.168.1.139:5060: REGISTER sip:192.168.1.3:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.139:5060;branch=z9hG4bK28008695836932320;rport From: Chakir Mrabet <sip:100@192.168.1.3:5060>;tag=628526938 To: Chakir Mrabet <sip:100@192.168.1.3:5060> Call-ID: 257201465-1550022549@192.168.1.139 CSeq: 1 REGISTER Contact: <sip:100@192.168.1.139:5060> Max-Forwards: 70 Expires: 60 User-Agent: Voip Phone 1.0 Content-Length: 0 [9] 2008/11/26 14:16:22: Resolve 176: aaaa udp 192.168.1.139 5060 [9] 2008/11/26 14:16:22: Resolve 176: a udp 192.168.1.139 5060 [9] 2008/11/26 14:16:22: Resolve 176: udp 192.168.1.139 5060 [9] 2008/11/26 14:16:22: SIP Tx udp:192.168.1.139:5060: SIP/2.0 404 Not Found Via: SIP/2.0/UDP 192.168.1.139:5060;branch=z9hG4bK28008695836932320;rport=5060 From: Chakir Mrabet <sip:100@192.168.1.3:5060>;tag=628526938 To: Chakir Mrabet <sip:100@192.168.1.3:5060>;tag=71e0278d27 Call-ID: 257201465-1550022549@192.168.1.139 CSeq: 1 REGISTER Content-Length: 0 It seems that the network is working properly between PBXnSIP server and local SIP phones, because they can see each other, but I still don't understand why the phone can't register. Did you change the domain name? Make sure it contains the name "192.168.1.3" or "localhost". The domain name is important because the PBX can handle a lot of domains, and needs to figure out which domain to choose. "localhost" is a wildcard matching anything. Quote Link to comment Share on other sites More sharing options...
cmrabet Posted November 26, 2008 Author Report Share Posted November 26, 2008 Did you change the domain name? Make sure it contains the name "192.168.1.3" or "localhost". The domain name is important because the PBX can handle a lot of domains, and needs to figure out which domain to choose. "localhost" is a wildcard matching anything. I had it as "localhost" but it didn't work, however I changed the domain name to "192.168.1.3" and then it worked. Is there any reason for this? Quote Link to comment Share on other sites More sharing options...
pbx support Posted November 26, 2008 Report Share Posted November 26, 2008 I had it as "localhost" but it didn't work, however I changed the domain name to "192.168.1.3" and then it worked. Is there any reason for this? One of the reason could be if the user is created on 192.168.1.3 domain. Other reason may be Ubuntu OS may not like the 'localhost' Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.