Inbound call from goes to towards bridge completely ignores rules

[PaulEmous]

V16.0.4

As the title says

I've got a TRUNK setup that should forward the incoming call to a local extension. Real simple.

Inbound Rules
DID > 3120xxx0280 > EXT 401
Also have this setup directly in the trunk. Both in office and out of office, out of office is not setup anyway.

However, when I call +3120xxx0280 (trunk / DID), I can see in activity that the call gets registered and match to an outbound rule?

04/14/2020 4:18:18 PM - [CM503010]: Call(C:14): Making route(s) from Line:10001<<00971502xxx38 to <sip:[email protected]:5060/UDP>

I can't find anywhere in the system where this would be set-up. I have an outbound rules "66" that routes to a bridge so 66800 goes as follows > 66 = outboud bridge 10066 > call queue "800" it works great but it's not what I want!

No matter how I try to let calls route from 3120xxx0280 it will always want to push it to 66800


I already restarted the services and rebooted the system.
Please help

 

[diamond9]

Hi, Have you got any inbound rules setup?

 

[PaulEmous]

Yes, sorry that line was missing, updated OP

 

[diamond9]

Try removing your outbound rule for a moment and lets see if that is the issue here

 

[PaulEmous]

I already did. It result in the call not being routed.

 

[diamond9]

can you send your inbound rules hiding any sensitive information

 

[leejor]

Check to be certain that the DID number being sent, matches your rule (exactly). That is usually the cause of rules not being followed. (provider is sending a leading digit) A check of the Activity Log should show why the call is routed back out. This should not normally happen unless it is forwarded by a destination (extension). Post the entire call, from start to finish, X-ing out any sensitive info, if you are still unclear about what is happening.

 

[PaulEmous]

This issue has been breaking my head. Sorry I didnt reply the requested.

Basically what is happening is the following:
I have seperate trunks for the sake of making it easy:
Trunk 020 = Line10000
Trunk 030 = Line10001

If I remove trunk 030 calls pass to the DID 020xxxx are routed as setup (Forward Rules)

However if I add Trank 030, calls to 020xxxx are identified as coming from Line10001 (Info on incoming INVITE from Line:10001) and therefor the route acts like its from the 030 trunk.

04/14/2020 8:03:00 PM - [CM500002]: Call(C:133): Info on incoming INVITE from Line:10001<<0097150xxxx38:
Invite-IN Recv Req INVITE from 91.x.x.x:5060 tid=4f4e.fb686923.0 [email protected]:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 91.x.x.231:5060;branch=z9hG4bK4f4e.fb686923.0
Via: SIP/2.0/UDP 91.x.x.115:5060;rport=5060;received=91.x.x.x;branch=z9hG4bK4f4e.b5e95312.0
Via: SIP/2.0/UDP 91.x.x.115:5080;branch=z9hG4bK39bbc915

 

[leejor]

What type of trunks are you using?

 

[PaulEmous]

Motto 3CX compatible SIP Trunks

 

[leejor]

So the same DID number, is coming in over different trunk groups?

 

[PaulEmous]

It looks like it, but there is no know configuration that supports that in my setup. Motto claims they aren't linked.

 

[leejor]

If you have multiple trunk groups, from the same provider, and DID service from them, then there must be some sort of "overflow" arrangement, at their end, to accommodate one group, no longer being registered. It is beginning to sound like it may be a provider configuration issue. However, with out seeing the full 3CX Activity log of a call, routing back out, i can't say for certain why that is happening.

 

[PaulEmous]

Can I send it to you?

 

[leejor]

Send it as a PM.

 

[PaulEmous]

I spend a good day on it, presented my findings to the SIP trunk provider and said they where also clueless. I remoted the trunk. Problem solved. Other trunk works fine.

Done.