Dialing sequence does not always complete

[pacpac]

Hi, when dialing a number, it appears the dial-sequence does not always complete. Sometimes it dials through fully, but other times I hear a fast busy tone in the middle of the dialing, and I see this event in the 3CX log:

SIP Server/Call Manager ID: 12294
Call or Registration to 44776@(Ln.10000@xxx) has failed. xx.xx.xx.xx replied: 503 destination is invalid; from IP:xx.xx.xx.xx:5060

Any idea what may cause this and how to fix? Thanks

 

[eddv123]

Hi pacpac,

Which phone do you have ? I know with a Yealink there is a default timer that if left will auto-dial the number without hitting the "OK" key, however this is around 5-10 seconds without any further keys being pressed.

 

[pacpac]

I am trying to get a Panasonic DECT phone connected to my router (Tilgin HG2381) to work with 3CX, but seems to encounter a few issues. There are not many settings I can try. See my previous post here:

https://www.3cx.com/community/threa...ed-options-for-credentials.62312/#post-261871

 

[leejor]

I am trying to get a Panasonic DECT phone connected to my router (Tilgin HG2381) to work with 3CX, but seems to encounter a few issues.

If this not a DECT/SIP set, then I have to assume you are using with an ATA. Dial timers would be set in the ATA. Which ATA is it?

 

[pacpac]

The phone is a standard DECT handset (no SIP/VoIP). I am not connecting using an ATA, I am connecting straight to the router, which has a RJ-11 port and an integrated VoIP feature.

 

[leejor]

...and the ATA, in the router, then connects to...3CX, or a VoIP provider?

Sounds to me like an ATA (in the router) configuration issue, at least, at this point, without more information.

 

[pacpac]

When in the router I set the variables. I can register the phone with 3CX fine, receive incoming calls, but the issue is re outgoing calls. See below the parameters I have available.

 

[leejor]

If you can register and receive calls, then it may not be those settings. Those would appear to have to be correct to be able to register.There may be a local dialplan in the ATA that is affecting dialled numbers.

What does the 3CX Activity Log show when you attempt a call? What digits are being received by the PBX compared to what you actually dial?

 

[pacpac]

In the activity log, I see two entries for each failed call:

12/20/2018 4:39:50 PM - Call to T:Line:10000>>44xxxx@[Dev:sip:[email protected]:5060] from L:19.1[Extn:zzz] failed, cause: Cause: 503 destination is invalid/INVITE from xx.xx.xx.xx:5060
12/20/2018 4:39:50 PM - [CM503003]: Call(C:19): Call to <sip:[email protected]:5060> has failed; Cause: 503 destination is invalid/INVITE from xx.xx.xx.xx:5060

I am trying to dial a UK number (0044xxxxxxxxxx, dialing in full on the phone itself, but above it appears 3CX only registers '44xxxx' and not the complete number. In the outbound rule I have set stripping 2, so 00 is not sent. However, sometimes the number received by 3CX is '44xx', '44xxxx'.. It looks like number-sequence sometimes is shorter and sometimes a couple of more numbers. Ideas?

 

[leejor]

Call to T:Line:10000>>44xxxx@[Dev:sip:[email protected]:5060

This log shows what number was sent out on the trunk after going through the outbound rules. You need to find the log of the call, when first sent (Invite) to 3CX from the ATA. Does that log show the same number you are dialling on the phone?

Perhaps it is an outbound rule issue.

Did you check the ATA for an internal dialplan?

503 destination is invalid/INVITE from xx.xx.xx.xx:5060

Is the IP you X'd out, your system public IP, or which?

 

[pacpac]

This is what the log shows going out from the router:

2018-12-20 16:39:50 Outgoing call 0044xxx 00:00:00

Always the same number entries I see on the 3CX logs.

I cannot see a dial plan configuration on the router's VoIP GUI. The x'd out IPs are the VoIP provider's IP as set as the SIP Trunk on 3CX.

 

[leejor]

Ok, I'm a bit confused.

A full UK (national) number is usually 10 digits, with a leading zero, for 11 total. Or, perhaps longer, if you include the country code , 44. In that case, do you not have to prefix with a 00? You say your outbound rules strip the 00, but the posted logs show only a 6 digit number being sent to your provider, which, i assume, is why the destination is invalid.

Can you explain why the sent digits are fewer that I would expect them to be?

 

[pacpac]

Yes, that is my assumption too, insufficient numbers cause the destination to be invalid. The problem is that the handset does not send all the numbers or the router does not register the numbers properly. I should say that I have tested the DECT phone as a normal landline and it works just fine.

 

[leejor]

Is it just that extension having this issue, or others as well? If you are dialling a "full" number, but the ATA is sending only 6 digits in an Invite, to 3CX, and the DECT set works just fine when connected to a normal POTS phone line, then, I would suspect something with the ATA. Never having used that make ATA/router before, I'm not familiar with all of the options that might affect (modify) any dialled digits.

Did you try using a different phone plugged into the ATA, a regular (non-cordless) analogue phone perhaps?

 

[pacpac]

Just this extension. I have a Grandstream DP715 connected, and that works just fine. I do not have an non-cordless phone easily available to test with, I'll see. Anyways, I might give this handset a miss trying to connect it to the router. If needed, I could always use a PAP2T or similar...