Inbound DID logged as 'anonymous', not triggering inbound rules

[kl116004]

I'm trying to get an inbound DID rule working. Currently, calls that should trigger are getting the default rule on the Patton gateway. I have edited the DIDs to have a leading * to catch any leading digits.

When I turn on verbose logging to see what is happening, this is what I find(going to censor confidential phone numbers with #######):

07/01/2018 4:27:32 PM - [CM500002]: Call(C:10): Info on incoming INVITE from Line:10002<<740#######:
Invite-IN Recv Req INVITE from 192.168.0.12:5062 tid=0e8b84a2b7e27c43c Call-ID=1ac805fa5c50a905:
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 192.168.0.12:5062;branch=z9hG4bK0e8b84a2b7e27c43c
Max-Forwards: 70
Contact: <sip:740#######@192.168.0.12:5062;transport=udp>
To: <sip:[email protected]>
From: "WIRELESS CALLER"<sip:740#######@192.168.0.12:5062>;tag=4c9303c3d1
Call-ID: 1ac805fa5c50a905
CSeq: 31052 INVITE
Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, INFO, REFER, REGISTER
Content-Type: application/sdp
Proxy-Authorization: Digest username="10002",realm="3CXPhoneSystem",nonce="414d53595b39393422:2d1ccdb8f6b8fa370fde957c1df4f912",uri="sip:[email protected]",response="fe08ae466b13216b2ac253e37c6c3780",algorithm=MD5
Supported: replaces
User-Agent: Patton SN4114 2JS2JO EUI 00A0BA0E447A R6.9 2017-03-13 H323 SIP FXS FXO M5T SIP Stack/4.2.14.18
Content-Length: 265

My guess is the problem is no DID is getting passed, the called number shows as anonymous. Correct me if I'm wrong, but the number I'm calling FROM is picked up ok, so that should mean CID data is coming through, at least partially, right? The number I am calling is a remote forward on the telco end, and I've tried calling both the public, forwarded number, and the unlisted local number it actually goes to, with the same result.

Please help.

 

[YiannisH_3CX]

Hello @kl116004

How was the Patton device configured and connected to the PBX? Did you use the configuration file generated from the PBX or was the device manually configured?
If the 3CX configuration file was used the Patton device should send the line number in the TO: field for example "00000"

 

[kl116004]

Hello @kl116004

How was the Patton device configured and connected to the PBX? Did you use the configuration file generated from the PBX or was the device manually configured?
If the 3CX configuration file was used the Patton device should send the line number in the TO: field for example "00000"

OK, that explains what I'm seeing from my OTHER Patton gateways. This is the SN4114 with 2 FXS and 2 FXO ports. Since I will use both the FXS and FXO ports, I had to use the Patton wizard to configure both FXS and FXO. Sounds like I need to bark up the Patton tree, right?

 

[leejor]

If these are gateways then only CID will be oassed on to 3CX. PSTN gateways don't support DID info.

 

[kl116004]

OK, that explains what I'm seeing from my OTHER Patton gateways. This is the SN4114 with 2 FXS and 2 FXO ports. Since I will use both the FXS and FXO ports, I had to use the Patton wizard to configure both FXS and FXO. Sounds like I need to bark up the Patton tree, right?

Alright, I've found where the function is that's taking the called-e164 and changing it to 000000, 000001 etc. So I can replicate those settings on my third gateway.