Can't make outbound with iinet VOIP

[kanine]

I have recently installed the 3CX PBX and have been able to successfully receive inbound calls on the 3CX Voip Phone. However I've not been able to make any outbound calls at all. The outbound rule seems to be picking up the call and trying to direct it, but the phone is just displaying a "Forbidden" message. There seems to be some clues (like the 404 error) in the server log but I've not been able to solve this... Please help.

Server Log (xx's in place of personal info)
17:18:16.234 [CM503020]: Normal call termination. Reason: Not found
17:18:16.234 [CM503016]: Call(17): Attempt to reach <sip:[email protected]:5060> failed. Reason: Not Found
17:18:16.234 [CM503003]: Call(17): Call to sip:[email protected]:5060 has failed; Cause: 404 Not found; from IP:203.xx.xx.xxx:5060
17:18:16.046 [CM503025]: Call(17): Calling VoIPline:98xxxx68@(Ln.10000@iitalk)@[Dev:sip:sip.vic.iinet.net.au:5060]
17:18:15.687 [CM503004]: Call(17): Route 1: VoIPline:98xxxx68@(Ln.10000@iitalk)@[Dev:sip:sip.vic.iinet.net.au:5060]
17:18:15.687 [CM503010]: Making route(s) to <sip:[email protected]:5060>
17:18:15.671 [CM505001]: Ext.10: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone 4.0.10858.0] PBX contact: [sip:[email protected]:5060]
17:18:15.625 [CM503001]: Call(17): Incoming call from Ext.10 to <sip:[email protected]:5060>

 

[leejor]

Call to sip:[email protected]:5060 has failed; Cause: 404 Not found; from IP:203.xx.xx.xxx:5060

Does you VoIP provider trunk show as registered in 3CX?

 

[kanine]

Does you VoIP provider trunk show as registered in 3CX?

Yes it is showing as registered. I did get one step further by prepending 03 on to the number, but I get the message as follows:
18:14:59.125 [CM503020]: Normal call termination. Reason: Forbidden
18:14:59.125 [CM503016]: Call(4): Attempt to reach <sip:[email protected]:5060> failed. Reason: Forbidden
18:14:59.125 [CM503003]: Call(4): Call to sip:[email protected]:5060 has failed; Cause: 403 Forbidden; from IP:203.55.229.194:5060

 

[leejor]

Well at least it shows that you are indeed sending digits through to your provider, just not ones that it likes. I would double check exactly what format they are expecting.

 

[mfm]

Hi,

The error messages are coming from the voip provider, thus only the voip provider can point in the right direction on why they are giving such an error, give them a call and ask them for assitance on the matter, once you have done that come back to the forums with their reply, as it will be crucial in diagnosing the issue.

 

[kanine]

Thanks Mark, will do. I've tried dialling with an without the 03 prefix to no avail as well and done extensive searching for iinet configuration, but still no luck as yet. I'll see if there is anything the provider can help with but I suspect they will tell me this access is not supported.

 

[kanine]

Have tried the VoIP support but they were unable to shed any further light on the issue. So still no further forward at this point.

 

[mfm]

Hi,

So your saying your voip provider COULD NOT tell you why they are rejecting the call. I will be happy to troubleshoot this starting with changing voip provider, its a guessing game unless they provide some light as to why they are rejecting!

If you rally want to stick with this provider then I suggest calling them and saying I need to know why you are rejecting my outbound call. (try and blame it on them, so they get a bit offeneded and answer you)

 

[kanine]

What is the best way to get detailed header information so I can provide this information to the VoIP provider?

They have offered to help me diagnose the issues but need some detailed information on headers in order to isolate the issues.

 

[kanine]

I've installed Wireshark to observe the requests being sent and have noticed that the only difference between a successful call made directly and one placed through 3CX is the following:

Successful - Sent-by port: 5060
Failed - Sent-by port: 2057

Also notice in the contact data of the message header the following on the failed attempt
Contact: <sip:[email protected]:2057>

compared with
Contact: <sip:[email protected]:5060> on the successful attempt.

Does this help pinpoint the issue? It seems to be tied in with this port 2057 being used?