V18 Inbound Rule Issue

Status
Not open for further replies.

jcostlow

Gold Partner
Advanced Certified
Joined
Jul 11, 2020
Messages
396
Reaction score
152
  • 3CX Version: 18.0.1608
  • Server OS: Debian 10
  • Is the 3CX Server Hosted and where: Locally installed
  • IP Phone Make/Model/Firmware: N/A all app
  • Provisioning Method: N/A
  • Trunk Provider or Gateway Make/Model: Telnyx
  • Has the Firewall Checker passed: YES
  • Are custom Phone Templates being used: NO
I have a test system that has been running fine. I noticed when using it to test faxing that it never came through. Upon looking into it the number I have assigned under inbound rules to go to the fax server is going to the IVR.

The "main" number is set to go to the IVR under the SIP trunk settings and inbound rule has this number going to fax. I am not sure why it isn't following that rule.

SIP Trunk
Screen Shot 2021-07-09 at 10.29.48 PM.png

Inbound Rule
Screen Shot 2021-07-09 at 10.30.25 PM.png
 
Try putting the DIDs as *(10digits) instead of E164. It did the trick for me but I think there's a bug on either Telnyx or the template that makes the SIP INVITE come in as E164 without the +. However, even that in the rules didn't seem to work for me.

As it's an Alpha tho, I expect this to be fixed by either party before the official release.
 
  • Like
Reactions: jcostlow
That did the trick, thanks. I thought I had it working with the numbers in E164 previously. I do see the call coming in 11 digit instead when running the capture.

This is my test box for the alpha to see all the changes and using Telnyx so I can just prepay the account for testing.
 
That did the trick, thanks. I thought I had it working with the numbers in E164 previously. I do see the call coming in 11 digit instead when running the capture.

This is my test box for the alpha to see all the changes and using Telnyx so I can just prepay the account for testing.
Yeah, it used to work with E164 but for some reason it doesn't anymore. I use SIP TLS, maybe that is related to it.

My guess it's that it is a Telnyx issue.
 
Status
Not open for further replies.

Forum statistics

Threads
111,982
Messages
590,121
Members
164,909
Latest member
Jacob.Ive