National Short Digit Outbound Rules

Status
Not open for further replies.

amanjuman

Trial User
Joined
Oct 3, 2020
Messages
36
Reaction score
1
Hi,

I'm having an issue with short digits number outbound rules.
In Bangladesh, most of the call centers have numbers like 16XXX. For example, The City Bank call center number is 16234
So I have trunk ready which allowed calling directly those numbers. If I use that trunk on IP Phone or SIP app, it works file to call 16XXX digits number.
However, when I do that from 3CX it always says "Destination is not available or not registered or there are no route available"
and this is the log

01/03/2022 11:54:17 PM - Call to T:Line:10002>>16234@[Dev:sip:[email protected]:5060;transport=TCP] from L:26.1[Extn:1009] failed, cause: Cause: 480 Temporarily Unavailable/INVITE from XX.YY.ZZ.XY:5060

Here is the Outbound rule:
Screenshot 2022-01-03 at 23-56-31 3CX Phone System Management Console.png

Also, I'm wondering how can I configure Outbound rules for 3 digits numbers like 101, 102, 911 while my extensions are 4 digits based.
Thanks
 
Hi @amanjuman

I suspect there is something wrong with your outbound parameters in the your trunk settings. 3CX has more parameters that might need configuring that an IP phone so there might be something wrong there. Your outbound rules look correct from the screenshot you shared so don't make any changes there for now.
I see that the transport used is TCP so that might also be an issue if your provider does not support TCP. Try to force the trunk to UDP from the Options tab of the trunk settings.

Also, I'm wondering how can I configure Outbound rules for 3 digits numbers like 101, 102, 911 while my extensions are 4 digits based.
The PBX will try to match an internal extension first and if it does not find a match if will route the call through the trunk if an outbound rule is matched. You could create an additional outbound rule for 3 digits and use that.
 
Do "normal" calls (non 5 digit calls), using the same trunk group, complete correctly?
 
@YiannisH_3CX
The trunk providers support UDP and TCP which is totally fine. Here is the trunk outbound parameters
1641302029485.png
Let me know if you have any suggestions so I'll try.
@leejor I tried to call without rules and the same issue, so I guess the Outbound rule that I configured is needed and fine.
 
Your outbound parameters are the ones in the generic template which might not be compatible with your provider. I would try to remove the Remote Party-ID headers and set them to default value and try again. Of that fails then you will need to speak to your provider for the best settings to use.
 
1641303000616.png
@YiannisH_3CX
Tried these as leave default and didn't work so reverted back as it was. I'll talk with Trunk support, see if that is able to help. One question, If the provider like to add their trunk to the 3CX Trunk list what would be the procedure? So I would suggest them follow that.
 
Status
Not open for further replies.

Forum statistics

Threads
112,326
Messages
591,901
Members
165,479
Latest member
Senergia