Not going call to a specific number

[Bash]

Hi
Having trouble to call to a specific number through SIP trunk after upgrading to V.16. Here is the situation:
The number is 5 digits (29911)
The outbound rule configured as:

Call to numbers starting with prefix: 299
Call from extensions: (blank)
Calls to numbers with a length of: 5
Route1: My_SIP_Trunk, Strip Digit: 0, Prepend (Blank)

I can call 29933, 29910 etc, but not able to call 29911. It says 484: Address incomplete. When i call to 29911 from my mobile, it works!

I appreciate any insight here.

Thank you

 

[Bash]

I appreciate any insight on this topic. Thanks

 

[Clément Rousseau]

did you asked your trunk provider about it ? logs of trunk provider are often more helpfull than 3cx logs.

When you said I can call 29911 from mobile, you dont talk about a 3cx application but a classic mobilephone network operator, right ? (just to be sure)

 

[Bash]

Yes, i can call with a classic mobile phone. Not from 3cx application. The problem i feel that, the last 2 digit (xxx11) is conflicting with something. i can guess the start digit conflicts. not sure of last digits.

 

[Bash]

by the way it was working fine till we upgraded to v.16.

 

[leejor]

What does the 3CX Activity log show for the call? Does it show the number matching an outbound rule, and the call being passed onto your provider? If so, then there may be a rejection message from the provider to provide a clue. If that is the case, then you'd have to discuss the fate of the call with them.

 

[Bash]

the 3cx log shows the same message 484-address incomplete.
I wonder why it happened after the v.16 upgrade.

 

[leejor]

Could you post the Activity log of a working call, and one of the failed call?

 

[leejor]

Might be a long shot, but...

I'm wondering if it has anything to do with the SIP ID change in version 16.

Some users have had issues unless this is enabled...
Network Settings -> FQDN -> Allow calls from/to external SIP URIs

Perhaps a conflict with something that exists in your system?

 

[Bash]

Tried checked and unchecked. No luck.

 

[JohnS_3CX]

Hi Bash,

Seems you can easily replicate this issue. Why not run a capture to see exact messages exchanged by the phones and the PBX?

We can see what the phone sends at least and see whether it is complete.

 

[Bash]

I will do that capture tomorrow.Thanks.

 

[Bash]

in the capture i found somewhere "Unrecognized SIP header"
Is there any specific reason for this? Only the number mentioned in the subject question has this issue.

Thanks

 

[Bash]

I dig further and found another error from the SIP gateway, which shows: Invalid number format (Address Incomplete)"

Does this mean, the gateway is expecting different number format?

 

[cobaltit]

I dig further and found another error from the SIP gateway, which shows: Invalid number format (Address Incomplete)"

Does this mean, the gateway is expecting different number format?

We have no idea what your gateway is so that makes it hard to answer the question. You might want to provide more information like so:

https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

 

[Bash]

Apologies for incomplete info.
The gateway is Patton Smartnode 5480. The wireshark screenshot is attached where the error was occured..

 

[leejor]

Assuming the 484 message is coming from the gateway itself, and not from your provider, relayed back through the gateway, then...

Is it possible, that at some point in the past, that number, or part of the number, was input into the gateway, for some routing/blocking reason, and a match is being made?