Leonmeijer Posted May 8, 2009 Report Posted May 8, 2009 Hello, I'm trying to make an outbound call, but I receive the message: 404-User not found. I've recently updated to the latest version of PBXnSIP, here is a part of the log, it shows opening socket 0.0.0.0 (??? strange). Can someone help me out with this? Inbound and local calls work fine. Trunk status is 200 registered. [9] 2009/05/08 19:19:41: UDP: Opening socket on 0.0.0.0:53872 [9] 2009/05/08 19:19:41: UDP: Opening socket on 0.0.0.0:53873 [5] 2009/05/08 19:19:41: Identify trunk (domain name match) 1 [9] 2009/05/08 19:19:41: Resolve 171: aaaa udp 192.168.1.100 38930 [9] 2009/05/08 19:19:41: Resolve 171: a udp 192.168.1.100 38930 [9] 2009/05/08 19:19:41: Resolve 171: udp 192.168.1.100 38930 [9] 2009/05/08 19:19:41: SIP Tx udp:192.168.1.100:38930: SIP/2.0 100 Trying Via: SIP/2.0/UDP 192.168.1.100:38930;branch=z9hG4bK-d8754z-9e62d636fc601f2d-1---d8754z-;rport=38930 From: "Leonmeijer" <sip:100@LMeijerNL>;tag=f0713b67 To: "" <sip:@LMeijerNL>;tag=15f0a5ce7a Call-ID: Yjc2OTRjM2RiNWMyMWEzYmY1NzU1ZTE2MzNhY2RmMTg. CSeq: 1 INVITE Content-Length: 0 [7] 2009/05/08 19:19:41: No authentication of user because call comes from trusted trunk [6] 2009/05/08 19:19:41: Sending RTP for Yjc2OTRjM2RiNWMyMWEzYmY1NzU1ZTE2MzNhY2RmMTg.#15f0a5ce7a to 192.168.1.100:11242 [9] 2009/05/08 19:19:41: Dialplan: Evaluating !^(\+?[0-9]*)@.*!sip:\1@\r;user=phone!i against @lmeijernl [5] 2009/05/08 19:19:41: Dialplan lmeijerdial: Match @lmeijernl to <sip:@194.120.0.198;user=phone> on trunk lmeijertrunk [5] 2009/05/08 19:19:41: Charge user 100 for redirecting calls [8] 2009/05/08 19:19:41: Play audio_moh/noise.wav [9] 2009/05/08 19:19:41: UDP: Opening socket on 0.0.0.0:59496 [9] 2009/05/08 19:19:41: UDP: Opening socket on 0.0.0.0:59497 [9] 2009/05/08 19:19:41: Resolve 172: url sip:0@194.120.0.198;user=phone [9] 2009/05/08 19:19:41: Resolve 172: udp 194.120.0.198 5060 [9] 2009/05/08 19:19:41: SIP Tx udp:194.120.0.198:5060: INVITE sip:0@194.120.0.198;user=phone SIP/2.0 Via: SIP/2.0/UDP 192.168.1.253:5060;branch=z9hG4bK-6c44f0f681147789b0e72d692ea603a2;rport From: "LMeijer.nl" <sip:Leonmeijer@194.120.0.198>;tag=20060 To: <sip:0@194.120.0.198;user=phone> Call-ID: 3feda46a@pbx CSeq: 30996 INVITE Max-Forwards: 70 Contact: <sip:Leonmeijer@192.168.1.253:5060;transport=udp> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/3.3.1.3177 Related-Call-ID: Yjc2OTRjM2RiNWMyMWEzYmY1NzU1ZTE2MzNhY2RmMTg. Content-Type: application/sdp Content-Length: 268 EDIT The begin of the log shows the following: [1] 2009/05/08 21:37:28: Starting up version 3.3.1.3177 [8] 2009/05/08 21:37:29: Found interface on 192.168.1.253 with netmask 255.255.255.0 [8] 2009/05/08 21:37:29: Found interface on 127.0.0.1 with netmask 255.0.0.0 [9] 2009/05/08 21:37:29: UDP: Opening socket on 192.168.1.253 [7] 2009/05/08 21:37:29: Found time zones HST AKDT AKST PDT PST MDT MST CDT CST2 EDT EST ADT AST NDT NST BST CET GMT+2 GMT+3 GMT+4 GMT+5 GMT+6 GMT+7 GMT+8 GMT+9 CST CAT IST AUS1 AUS2 AUS3 AUS4 AUS5 AUS6 GMT [8] 2009/05/08 21:37:29: Timer frequency is 500 us [1] 2009/05/08 21:37:29: Working Directory is C:\Program Files\pbxnsip\PBX [9] 2009/05/08 21:37:29: UDP: Opening socket on 192.168.1.253 [7] 2009/05/08 21:37:29: UDP: Opening socket on 0.0.0.0 [5] 2009/05/08 21:37:29: Starting threads [7] 2009/05/08 21:37:29: TCP: Opening socket on 0.0.0.0:800 <--- 0.0.0.0 ??? [7] 2009/05/08 21:37:29: TCP: Opening socket on 0.0.0.0:4430 [7] 2009/05/08 21:37:29: UDP: Opening socket on 0.0.0.0:161 [7] 2009/05/08 21:37:29: UDP: Opening socket on 0.0.0.0:69 [7] 2009/05/08 21:37:29: UDP: Opening socket on 0.0.0.0 [7] 2009/05/08 21:37:29: UDP: Opening socket on 0.0.0.0:5060 [7] 2009/05/08 21:37:29: TCP: Opening socket on 0.0.0.0:5060 [7] 2009/05/08 21:37:29: TCP: Opening socket on 0.0.0.0:5061 [9] 2009/05/08 21:37:29: Resolve 1: url sip:194.120.0.198 [9] 2009/05/08 21:37:29: Resolve 1: udp 194.120.0.198 5060 [9] 2009/05/08 21:37:29: SIP Tx udp:194.120.0.198:5060: Quote
Vodia PBX Posted May 8, 2009 Report Posted May 8, 2009 The "0.0.0.0" just means "bind it to all local IPv4 addresses". That is just UNIX style of telling the operating system to which IP address the socket should be bound (Windows does it the same way). That is absolutely okay. We just included the "0.0.0.0" to make that point clear. The 404 not found has nothing to do with this. Quote
Leonmeijer Posted May 8, 2009 Author Report Posted May 8, 2009 The "0.0.0.0" just means "bind it to all local IPv4 addresses". That is just UNIX style of telling the operating system to which IP address the socket should be bound (Windows does it the same way). That is absolutely okay. We just included the "0.0.0.0" to make that point clear. The 404 not found has nothing to do with this. Oke, but what might be the 404 problem then? looks like the pbx is not forwarding the call to the internet or the pbx is looking in its internal database for this number. Quote
Vodia PBX Posted May 8, 2009 Report Posted May 8, 2009 Oke, but what might be the 404 problem then? looks like the pbx is not forwarding the call to the internet or the pbx is looking in its internal database for this number. The PBX believes the call comes from a trunk that redirects the call; using user 100 ("assume call comes from ..."). Is that indended? Usually this is only used for Exchange trunks. Quote
Leonmeijer Posted May 8, 2009 Author Report Posted May 8, 2009 The PBX believes the call comes from a trunk that redirects the call; using user 100 ("assume call comes from ..."). Is that indended? Usually this is only used for Exchange trunks. Thanks for spotting that:) clearing that field solved the problem, I've also changed the domain to "localhost". Thanks. Leon Quote
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.