Solved 3CX v15.5 Linux - new Outbound rule with 'Calls to numbers starting with prefix' not working

[ANJOTI]

Hi,

we have 02 SIP Trunk set up, we create an specific rule to number starting with prefix '+5541.....' route is to SIPTrunk-B - even put it on top, all outbound calls keep going to SIPTrunk-A...
Both rules are using the option 'Extension Group' from 'GroupCompany'. Maybe the combination of parameters like 'Extension Group' + 'Calls to numbers starting with prefix' cannot be handled correct.

Our understand was that the order to check outbound rules was 'top>down' but is not working, so we already tried to move the new one down but no sucess...

>>> Did I forget something????

*** Another idea, 3CX team should be create a view of current calls from 'SIP Trunk' page for monitor purposes. Looking information at ActivityLOG is unproductive.

 

[leejor]

Did you setup E.164, in 3CX to convert + to the desired international prefix?

https://www.3cx.com/community/threads/softphone-v15-convert-to-00-as-default.51309/

 

[craigreilly]

definitely put it at the top.
remove the group for testing. even make it from the extension you are testing from.
check the logs for response on why it doesn't match rule 1.

 

[ANJOTI]

- The new rule named 'Rule1' is on the top, and its details is:

- works for 'from extension' 91001 (instead from group);
- route to SIPTrunk-B;
- strip 3 digits (remove +55);
- prepend '0' before dial.​

But it keeps going to SIPTrunk-A as the Activity log:
#############
04/12/2018 2:32:53 PM - Call(C:15): Call from Extn:91001 to +5541xxxxxxxx matches outbound rule 'Rule0'
04/12/2018 2:32:53 PM - [Flow] Call(C:15): has built target endpoint: Out#:>>Rule{Rule0}>>41xxxxxxxx for call from L:15.1[Extn:91001]
04/12/2018 2:32:53 PM - [Flow] Target endpoint for +5541xxxxxxxx is Out#:>>Rule{Rule0}>>41xxxxxxxx
04/12/2018 2:32:53 PM - Looking for outbound rule: dialed = [+5541xxxxxxxx], processed: [4130251000]; from-ext:
04/12/2018 2:32:53 PM - [Flow] Building target endpoint to +5541xxxxxxxx from "Renato Pereira" <sip:[email protected]:5060>

 

[craigreilly]

So is it the Prepend 0? The trunk it works on does not seem to need a Prepend of 0.

I do not have any experience with your providers, just trying to find any hints.

As an alternative, add the other trunk as the secondary route to the failing rule to see if it works or not.

 

[ANJOTI]

Just to clarify:
- the SIPTrunk-A uses e164 format (+[country id]+[local id]+[number itself]);
- the SIPTrunk-B uses just '0'+[local id]+[number itself];

 

[craigreilly]

Can you try to do a sample rule, any thing starting with 0 from your extension...
There has to be something in what the provider is expecting that they are not getting...

But maybe its caller id issue?

Do a wireshark/packet capture and see if it tries to make a call and it gets rejected?

 

[YiannisH_3CX]

I believe that E164 is changing the number before it reaches your outbound rules. Send us a screenshot from your outbound rules settings so we can be sure and at the same time add an outbound rule with "Calls starting with prefix" 0055 strip 4 and add 0 and see if that works

 

[ANJOTI]

It´s anoying, keeps going throught wrong SipTrunk

----

05/10/2018 6:41:04 PM - L:21.2[Line:10000>>+554130xxxx00] got Terminated Send Req BYE from 0.0.0.0:0 tid=a5af7e121f1cc852 Call-ID=HJN4lPxZp6J8i8WbmvlRaA..:
BYE sip:+554130xxxx00@xxxxxxxxxxxxx:5060 SIP/2.0
Via: SIP/2.0/ ;branch=z9hG4bK-524287-1---a5af7e121f1cc852;rport
Max-Forwards: 70
Contact: <sip:user@xxxxxxxx:5060>
To: <sip:+554130xxxx00@xxxxxxxxxxx:5060>;tag=1812115959
From: "+55 51 4063-xxxx"<sip:user@xxxxxxxxx:5060>;tag=5d186c2a
Call-ID: HJN4lPxZp6J8i8WbmvlRaA..
CSeq: 3 BYE
User-Agent: 3CXPhoneSystem 15.5.10244.4 (10244)
Content-Length: 0

---

 

[ANJOTI]

Another info from logs showing that it´s going through wrong outbound rule

05/10/2018 6:51:12 PM - Call(C:22): Call from Extn:91001 to +554130xxxxx00 matches outbound rule 'Rule0'
05/10/2018 6:51:12 PM - [Flow] Call(C:22): has built target endpoint: Out#:>>Rule{Rule0}>>4130xxxxx00 for call from L:22.1[Extn:91001]
05/10/2018 6:51:12 PM - [Flow] Target endpoint for +554130xxxxx00 is Out#:>>Rule{Rule0}>>4130xxxxx00
05/10/2018 6:51:12 PM - Looking for outbound rule: dialed = [+554130xxxxx00], processed: [4130xxxxx00]; from-ext:

---

 

[ANJOTI]

 

[ANJOTI]

Even after set the 'Extension Group' parameter, it keeps going through wrong outbound rule ('0' instead '1')...

 

[ANJOTI]

Fixed!!

After purge logs and dial again to see what happens, search for 'Looking for outbound rule' in the logs and pay attention to 'processed' field/number, for example:

>>> The outbound rule to be used will be based on the 'processed' field/number.

'Looking for outbound rule: dialed = [+554130xxxx00], processed: [4130xxxx00]

 

[YiannisH_3CX]

Glad to see has been resolved and thank you for updating the thread with your solution. As mentioned the E164 was processing the number before reaching the outbound parameters.