V16 Inbound rules have stopped working / Siptrunk invalid

[Paul Fouche]

Good Morning All,
A client of ours has something weird happen after the V16 update.
The inbound rules are showing. but they are not taking effect.
When i click on add DID rules It says "In order to add an Inbound Rule, a SIP Trunk must be created first.
Go to SIP trunks and Add SIP Trunk."
I look at the sip trunk and its registered no problems.
I have attempted the following.
Export Existing Sip trunk.
Import the sip trunk again, remove old one, re import inbound rules.

As soon as i assign one inbound rule that error happens again.

I then attempted to re add the entire sip trunk with the 100+DID's from scratch.
I then recreated the inbound rules from scratch it took a while.
However it isn't working.

I contacted the provider and they are getting a 404 from our server saying that the DID does not exist.

Any suggestions would be highly appreciated

 

[craigreilly]

Can you add the trunk without the DID's and test first before moving on?
Then manually add a single DID and test.

 

[Paul Fouche]

This somehow just started working.
However when I have a forwarder set it does not work
EG, I have an inbound rule that forwards directly to mobile.
When i dial the inbound number the PABX is giving the provider a 404 error ( basically saying that the DID does not exist on the PABX)
HOWEVER if i change that exact same inbound rule to go to an extension instead of going to a mobile number.. it works perfectly.

 

[craigreilly]

a guess here: forwarding to an outside number is using the original caller id and passing that thru to the provider for the outbound call. they may not allow that number since it is not registered to you, for security reasons and such.
try changing the outbound caller id in the trunk - outbound parameters:

if you have this setting - try using "outbound caller id" from the dropdown list instead.

 

[Paul Fouche]

hey there, Have tried this.
The outbound calling works perfectly if i first direct the call to the extension and then have a forward to mobile rule on the extension with Call deflection 302 enabled..

If i try route a call directly to mobile its like the 3cx does not recognize the DDI

 

[craigreilly]

So you have tried changing caller ID on outbound calls... I thought for sure that was it based on the error message.

 

[AWS2P]

isn't it you have groups or extensions specified in your rule ? if so you need to change your rule because when you try to directly forward to mobile this is a system extension , and this doesn't belong to groups nor users extensions so it's blocked.
see this video ,start at 5:20

 

[Paul Fouche]

isn't it you have groups or extensions specified in your rule ? if so you need to change your rule because when you try to directly forward to mobile this is a system extension , and this doesn't belong to groups nor users extensions so it's blocked.
see this video ,start at 5:20

Well well.. Thank you i didnt think outbound routing would change in between versions.