Outbound rule for all possible numbers

Status
Not open for further replies.

RicardoAL

Free User
Joined
Oct 6, 2021
Messages
7
Reaction score
2
Hello, despite an universal outbound rule to overwrite this, all calls are made from a trunk excluded from the rule.

I thought I could every possible call with this rule:
  • Calls to numbers starting with prefix: +,0-9
  • Calls from extension group(s): ALL (group that includes all users)
  • Make outbound calls on: Selected two other trunks and then block calls, still all calls are made through Slot0 (not listed)
1633520222803.png

My trunk configuration

1633520262724.png

My log

10/06/2021 1:27:46 PM - Exception: DialogUsage::Exception Can't provide an answer @ ServerInviteSession.cxx:501
10/06/2021 1:27:46 PM - Call to T:Line:10001>>0696731XXX@[Dev:sip:[email protected]:5060;transport=UDP] from L:37.1[Extn:10] failed, cause: Cause: 486 Busy Here/INVITE from 81.26.205.188:5060
10/06/2021 1:27:46 PM - [CM503003]: Call(C:37): Call to <sip:[email protected]:5060> has failed; Cause: 486 Busy Here/INVITE from 81.26.XXX.XXX:5060
10/06/2021 1:27:32 PM - [CM303003]: There are no available outbound lines on gateway DIGICOM at this time. First line: Lc:10005(@digicom[<sip:[email protected]:5060/UDP>])
10/06/2021 1:23:09 PM - [CM504005]: Registration failed for: Lc:10005(@digicom[<sip:[email protected]:5060/UDP>]); Cause: Cause: 403 Forbidden/REGISTER from 80.90.88.238:5060
10/06/2021 1:21:27 PM - Exception: DialogUsage::Exception Can't provide an answer @ ServerInviteSession.cxx:501
10/06/2021 1:21:27 PM - Call to T:Line:10001>>0696731XXX@[Dev:sip:[email protected]:5060;transport=UDP] from L:36.1[Extn:10] failed, cause: Cause: 486 Busy Here/INVITE from 81.26.XXX.XXX:5060

Any suggestions would be appreciated. :)

Thank you!
 

Attachments

  • 1633520032112.png
    1633520032112.png
    62.6 KB · Views: 18
Outbound rules are evaluated on a top-down order so you need to put this rule on top of your other outbound rules in order for this to be selected. If this is on the bottom of the list and your call matches another outbound rule first then the call will be routed through the other outbound rule.
 
  • Like
Reactions: RicardoAL
Thanks for your quick reply Yiannis. There's only this one outbound rule and no others.

1633523341815.png
 
How do you know that calls go out though slot0 and not the other trunks? Also i see that slot0 through slot3 are all part of a analog gateway . Since Digicom is not registered then calls would go out through the gateway.
What type of gateway is this and how is it configured?
 
  • Like
Reactions: RicardoAL
For testing purposes I'm calling my own number and thus see that the calls go out of slot0, also in the history below.

The gateway is a Dinstar UC2000VE, the SIPs from the log match the slots/ports 10000 = slot0, 10001 = slot1

What additional information about it's configuration should I provide?

1633524793330.png
1633524829405.png
 
From the log you provided from 3CX I cannot see line 10000 being used so there are either more logs or the calls are going correctly to the gateway and the gateway forwards all calls from port 0.
Unfortunately Dinstar is not a supported gateway so I don't know if that is set up correctly or not so mu only advice is check the 3CX activity log and see if calls are indeed sent from trunk slot0 or not. If calls are sent through slot1 in 3CX then it is up to the gateway to route them correctly out.
 
Thanks for your help up to this point. I didn't realize this device isn't supported as it was provided by the 3CX partner in my country. I will investigate further the routing issue within gateway.
 
  • Like
Reactions: YiannisH_3CX
Status
Not open for further replies.

Forum statistics

Threads
111,993
Messages
590,178
Members
164,933
Latest member
bunthoeun.may