Unable to make outgoing calls - VOIP

Status
Not open for further replies.

DMarriott

Joined
Jan 23, 2014
Messages
10
Reaction score
0
Hi,

I have just managed to get 3CX up and running and incoming calls work fine, however I cannot get outgoing calls to go through. I have setup the outbound rule to use the VOIP provider but I get the following response when trying a call:

Call or Registration to 0421070214@(Ln.10000@Generic VoIP Provider -) has failed. [ V4 203.59.49.10:5060 UDP target domain=unspecified mFlowKey=816 ] replied: 404 Not found; from IP:203.59.49.10:5060

Can someone please help me with this one? I have spent hours looking over various settings but cant see where I'm going wrong. Internet searches for the 404 error relating to 3CX systems haven't provided any good info...

Cheers,

Dave
 
Are you certain that you are sending the provider, the correct number of digits (correct format)?
 
You may have the outbound rule incorrect.... You may want to paste more info from the capture.
 
Thanks for the replies. I am simply trying to call a mobile phone number, using the same number of digits I would normally use for a regular phone.

Here is a larger capture from the log:
06-Feb-2014 12:49:31.208 Leg L:4.1[Extn] is terminated: Cause: BYE from PBX
06-Feb-2014 12:49:31.208 Leg L:4.4[Line:10000>>0421070214] is terminated: Cause: 404 Not found/INVITE from 203.59.49.10:5060
06-Feb-2014 12:49:31.207 [CM503020]: Call(C:4): Normal call termination. Call originator: Extn:101. Reason: Not found
06-Feb-2014 12:49:31.207 L:4.1[Extn] failed to reach Line:10000>>0421070214, reason Not Found
06-Feb-2014 12:49:31.207 Call to T:Line:10000>>0421070214@[Dev:sip:[email protected]:5060] from L:4.1[Extn] failed, cause: Cause: 404 Not found/INVITE from 203.59.49.10:5060
06-Feb-2014 12:49:31.206 [CM503003]: Call(C:4): Call to <sip:[email protected]:5060> has failed; Cause: 404 Not found/INVITE from 203.59.49.10:5060
06-Feb-2014 12:49:31.049 Leg L:4.3[Line:10000>>0421070214] is terminated: Cause: 404 Not found/INVITE from 203.59.49.10:5060
06-Feb-2014 12:49:31.049 [CM503025]: Call(C:4): Calling T:Line:10000>>0421070214@[Dev:sip:[email protected]:5060] for L:4.1[Extn]
06-Feb-2014 12:49:30.717 Call to T:Line:10000>>0421070214@[Dev:sip:[email protected]:5060] from L:4.1[Extn] failed, cause: Cause: 404 Not found/INVITE from 203.59.49.10:5060
06-Feb-2014 12:49:30.717 [CM503003]: Call(C:4): Call to <sip:[email protected]:5060> has failed; Cause: 404 Not found/INVITE from 203.59.49.10:5060
06-Feb-2014 12:49:30.640 Leg L:4.2[Line:10000>>0421070214] is terminated: Cause: 404 Not found/INVITE from 203.59.49.10:5060
06-Feb-2014 12:49:30.640 [CM503025]: Call(C:4): Calling T:Line:10000>>0421070214@[Dev:sip:[email protected]:5060] for L:4.1[Extn]
06-Feb-2014 12:49:30.304 Call to T:Line:10000>>0421070214@[Dev:sip:[email protected]:5060] from L:4.1[Extn] failed, cause: Cause: 404 Not found/INVITE from 203.59.49.10:5060
06-Feb-2014 12:49:30.285 [CM503003]: Call(C:4): Call to <sip:[email protected]:5060> has failed; Cause: 404 Not found/INVITE from 203.59.49.10:5060
06-Feb-2014 12:49:30.090 [CM503025]: Call(C:4): Calling T:Line:10000>>0421070214@[Dev:sip:[email protected]:5060] for L:4.1[Extn]
06-Feb-2014 12:49:29.721 [CM503027]: Call(C:4): From: Extn:101 ("Boardroom " <sip:[email protected]:5060>) to T:Line:10000>>0421070214@[Dev:sip:[email protected]:5060]
06-Feb-2014 12:49:29.721 [CM503004]: Call(C:4): Route 3: from L:4.1[Extn] to T:Line:10000>>0421070214@[Dev:sip:[email protected]:5060]
06-Feb-2014 12:49:29.721 Line limit check: Current # of calls for line Lc:10000(@Generic VoIP Provider -[<sip:[email protected]:5060>]) is 0; limit is 10

Cheers,

Dave
 
I see from your providers website that calls to mobiles are charged almost twice the rate, for 30 seconds, as an untimed call to a landline. For this reason there may be some action on your part to permit these calls. I would contact your provider, to assist in resolution, as the Not Found, would appear to be coming from them.

DMarriott said:
Cause: 404 Not found/INVITE from 203.59.49.10:5060

Have you attempted calls to landline numbers?
 
Hi Leejor,

I have tried calls to landlines as well and get the exact same error. It was even a lineline hosted by the same provider.

Do you still think its worth contacting them or would this suggest there is still a problem with my 3CX settings? Previous to setting up 3CX, we were simply using a normal analogue handset plugged into the VOIP router and makings calls via that using the same provider as I have programmed into 3CX. The router has now had its local VOIP disabled so that the relevant ports could be forwarded to the 3CX server. Given that incoming calls work fine, I still think it must be a setting in 3CX that I have wrong but just dont know where...

Cheers,

Dave
 
Ok... you didn't say that you had used this provider previously, with success, using another device.

Since you can receive calls, the trunk is obviously registering properly with the provider.

Another user found a difference when using VoIP Provider as opposed to SIP Trunk.
http://www.3cx.com/forums/outbound-call-not-possible-38835.html
What template are you using for this trunk?

If you are still pulling out your hair (unless someone else who has experience with this provider and 3CX speaks up), i would contact you provider and see if the are able to provide any information on what is happening when you attempt a call. Obviously some provider don't have the resources (manpower) to do this, but you might get lucky.
 
Hi Leejor,

Sorry for not mentioning the previously working VOIP. Yes, 3CX is showing that the provider is registered (hence the incoming calls work)

I had read that post but I already have it set up as a VOIP Provider rather than SIP trunk (which is what solved that persons issue).

As you say, I've hoped that people will give me some pointers as I'm out of ideas myself. If no others ideas come in, I'll try contacting my provider and see if they can shed any light on the error message. Unfortunately, in the past they have generally only been able to give good advice to those customers using the providers branded routers and that's about it. I guess if they are able to tell me why I'm receiving the 404 error, that is probably the best bet at this stage.

Thanks,

Dave
 
As a bit of a last resort, if you have the time, would be to use Wireshark to compare a call from ATA or VoIP set (programmed to use that provider), that hopefully works, and one from the 3CX trunk.

You might want to consider posting the 3CX settings page for your trunk, Xing out (of course), any "sensitive" information.

I would imagine that you've gone over all of this...

http://whirlpool.net.au/wiki/iiNetPhone
 
I dont have an ATA to test with but I have a few screen shots of the VOIP Provider settings if that helps at all...
 

Attachments

  • 3CXsettings1.PNG
    3CXsettings1.PNG
    26.5 KB · Views: 1,703
  • 3CXsettings2.PNG
    3CXsettings2.PNG
    33 KB · Views: 1,700
  • 3CXsettings3.PNG
    3CXsettings3.PNG
    13.5 KB · Views: 1,691
I don't see any glaring errors in your settings (of course, I don't use the same provider).

You may want to "play" with the Location of Destination Number settings. You are using the defaults, which work in most cases, but, your provider may want something else.

I see that your registration time is every 60 seconds, which seems a bit extreme (unless that's what they want). When you register, the provider will suggest a re-registration time, however, setting it manually to less that that will usually override their "suggestion".

In the 3CX logs, you might get some additional information by enabling Verbose mode.
 
I have now tried every possible variation of the "Location of destination number" in the outbound settings but nothing seemed to help. I have turned on "verbose mode" in the log and here is a snapshot from some of my call attempts:
10-Feb-2014 08:44:48.284 Leg L:17.1[Extn] is terminated: Cause: BYE from PBX
10-Feb-2014 08:44:48.234 [CM503020]: Call(C:17): Normal call termination. Call originator: Extn:101. Reason: Not found
10-Feb-2014 08:44:48.234 L:17.1[Extn] failed to reach Line:10000>>0421070214, reason Not Found
10-Feb-2014 08:44:48.233 Leg L:17.4[Line:10000>>0421070214] is terminated: Cause: 404 Not found/INVITE from 203.59.49.10:5060
10-Feb-2014 08:44:48.233 Call to T:Line:10000>>0421070214@[Dev:sip:[email protected]:5060] from L:17.1[Extn] failed, cause: Cause: 404 Not found/INVITE from 203.59.49.10:5060
10-Feb-2014 08:44:48.233 [CM503003]: Call(C:17): Call to <sip:[email protected]:5060> has failed; Cause: 404 Not found/INVITE from 203.59.49.10:5060
10-Feb-2014 08:44:48.048 Leg L:17.3[Line:10000>>0421070214] is terminated: Cause: 404 Not found/INVITE from 203.59.49.10:5060
10-Feb-2014 08:44:48.048 [CM503025]: Call(C:17): Calling T:Line:10000>>0421070214@[Dev:sip:[email protected]:5060] for L:17.1[Extn]
10-Feb-2014 08:44:48.045 Call to T:Line:10000>>0421070214@[Dev:sip:[email protected]:5060] from L:17.1[Extn] failed, cause: Cause: 404 Not found/INVITE from 203.59.49.10:5060
10-Feb-2014 08:44:48.045 [CM503003]: Call(C:17): Call to <sip:[email protected]:5060> has failed; Cause: 404 Not found/INVITE from 203.59.49.10:5060
10-Feb-2014 08:44:47.917 Leg L:17.2[Line:10000>>0421070214] is terminated: Cause: 404 Not found/INVITE from 203.59.49.10:5060
10-Feb-2014 08:44:47.917 [CM503025]: Call(C:17): Calling T:Line:10000>>0421070214@[Dev:sip:[email protected]:5060] for L:17.1[Extn]
10-Feb-2014 08:44:47.913 Call to T:Line:10000>>0421070214@[Dev:sip:[email protected]:5060] from L:17.1[Extn] failed, cause: Cause: 404 Not found/INVITE from 203.59.49.10:5060
10-Feb-2014 08:44:47.913 [CM503003]: Call(C:17): Call to <sip:[email protected]:5060> has failed; Cause: 404 Not found/INVITE from 203.59.49.10:5060
10-Feb-2014 08:44:47.788 [CM503025]: Call(C:17): Calling T:Line:10000>>0421070214@[Dev:sip:[email protected]:5060] for L:17.1[Extn]
10-Feb-2014 08:44:47.728 [CM503027]: Call(C:17): From: Extn:101 ("Boardroom " <sip:[email protected]:5060>) to T:Line:10000>>0421070214@[Dev:sip:[email protected]:5060]
10-Feb-2014 08:44:47.728 [CM503004]: Call(C:17): Route 3: from L:17.1[Extn] to T:Line:10000>>0421070214@[Dev:sip:[email protected]:5060]
10-Feb-2014 08:44:47.728 Line limit check: Current # of calls for line Lc:10000(@Generic VoIP Provider -[<sip:[email protected]:5060>]) is 0; limit is 10
10-Feb-2014 08:44:47.728 [CM503027]: Call(C:17): From: Extn:101 ("Boardroom " <sip:[email protected]:5060>) to T:Line:10000>>0421070214@[Dev:sip:[email protected]:5060]
10-Feb-2014 08:44:47.728 [CM503004]: Call(C:17): Route 2: from L:17.1[Extn] to T:Line:10000>>0421070214@[Dev:sip:[email protected]:5060]
10-Feb-2014 08:44:47.728 Line limit check: Current # of calls for line Lc:10000(@Generic VoIP Provider -[<sip:[email protected]:5060>]) is 0; limit is 10
10-Feb-2014 08:44:47.728 [CM503027]: Call(C:17): From: Extn:101 ("Boardroom " <sip:[email protected]:5060>) to T:Line:10000>>0421070214@[Dev:sip:[email protected]:5060]
10-Feb-2014 08:44:47.728 [CM503004]: Call(C:17): Route 1: from L:17.1[Extn] to T:Line:10000>>0421070214@[Dev:sip:[email protected]:5060]
10-Feb-2014 08:44:47.728 Line limit check: Current # of calls for line Lc:10000(@Generic VoIP Provider -[<sip:[email protected]:5060>]) is 0; limit is 10
10-Feb-2014 08:44:47.728 Call(C:17): Call from Extn:101 to 0421070214 matches outbound rule 'Rule for Generic VoIP Provider -'
10-Feb-2014 08:44:47.727 [CM503001]: Call(C:17): Incoming call from Extn:101 to <sip:[email protected]:5060>
10-Feb-2014 08:44:40.046 [CM504004]: Registration succeeded for: Lc:10000(@Generic VoIP Provider -[<sip:[email protected]:5060>])
10-Feb-2014 08:44:39.633 [CM504003]: Sent registration request for Lc:10000(@Generic VoIP Provider -[<sip:[email protected]:5060>])
10-Feb-2014 08:44:39.006 [CM504004]: Registration succeeded for: Lc:10000(@Generic VoIP Provider -[<sip:[email protected]:5060>])
10-Feb-2014 08:44:38.721 [CM504003]: Sent registration request for Lc:10000(@Generic VoIP Provider -[<sip:[email protected]:5060>])

I am still not able to get a call out. Looks like I'll have to try and get hold of the provider and see if they can help with the error 404. I'm just very skeptical about them helping due to the fact that a) 3CX has nothing to do with them, and b) we had working calls when using the basic VOIP via the router so the problem is surely within the 3CX settings.

Regards,

Dave
 
They obviously don't like something that you are sending them. They should be able to, at least, tell you what it is. Could it be the originators caller ID? Perhaps they think you are attempting to spoof a number.
 
[SOVLED] Re: Unable to make outgoing calls - VOIP

I just wanted to post my results here for anyone in the future that might come across the same problem. After further trolling of the net I found the solution to my issue.
My answer came from here:
http://forums.whirlpool.net.au/archive/1566849

...but essentially the issue was that I needed to put "iinetphone.iinet.net.au" in place of "sip.wa.iinet.net.au", even though thats the way the settings were working back when I was simply using the built-in VOIP on my router.

Either way, I'm happy its now working!
 
Status
Not open for further replies.

Members Online Now

Forum statistics

Threads
111,835
Messages
589,289
Members
164,665
Latest member
dominik.pepel