Inbound routes for PSTN Sangoma by DID

[mtheory3cx]

Recently, I had to rebuild our 3CX server and now our inbound routes aren't coming in by the DID inbound rule. They used to.
Scenario:
3CX v10, Sangoma A101 PRI 1port, Netborder Express Gateway
Sangoma configured as PSTN gateway, port 10000
~25 DIDs

Created the PSTN gateway for Sangoma using 3CX's template. Adding the DIDs and then generated config file.
Imported the config file in Netborder Express after configuring the gateway

Inbound and outbound calls are flowing.

Have been trying to configure each DID to have it's own inbound route (e.g. go to IVR, ring group, etc); however, they follow the PSTN's inbound route.

Sent Sangoma my config files and routing table, they said it was a 3CX issue.

I am not good with SIP knowledge for inbound and outbound parameters. If someone can help, that would be fantastic. Here are my logs for a test phone call:

19:29:09.611 [CM503008]: Call(1544): Call is terminated
19:29:04.327 Session 289955 of leg C:1544.1 is confirmed
19:29:04.235 [CM503007]: Call(1544): Device joined: sip:[email protected]:40600;rinstance=671ccfe7f4076352
19:29:04.231 [CM503007]: Call(1544): Device joined: sip:[email protected]:5066
19:29:04.228 [MS210003] C:1544.1:Answer provided. Connection(transcoding mode[unsecure]):192.168.11.61:7036(7037)
19:29:04.221 [MS210001] C:1544.2:Answer received. RTP connection[unsecure]: 127.0.0.1:40710(40711)
19:29:04.218 Remote SDP is set for legC:1544.2
19:29:04.212 [CM505001]: Ext.802: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX IVR;Rev: 1] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX IVR] PBX contact: [sip:[email protected]:5060]
19:29:04.211 [CM503002]: Call(1544): Alerting sip:[email protected]:40600;rinstance=671ccfe7f4076352
19:29:04.053 [CM503025]: Call(1544): Calling Ext:Ext.802@[Dev:sip:[email protected]:40600;rinstance=671ccfe7f4076352]
19:29:04.050 [MS210002] C:1544.2:Offer provided. Connection(transcoding mode): 127.0.0.1:7038(7039)
19:29:04.020 [CM503004]: Call(1544): Route 1: Ext:Ext.802@[Dev:sip:[email protected]:40600;rinstance=671ccfe7f4076352]
19:29:04.019 [CM503010]: Making route(s) to <sip:[email protected]:5060>
19:29:04.018 [MS210000] C:1544.1:Offer received. RTP connection: 192.168.11.61:16886(16887)
19:29:04.015 Remote SDP is set for legC:1544.1
19:29:04.011 [CM503001]: Call(1544): Incoming call from 5555555555@(Ln.10000@Sangoma) to <sip:[email protected]:5060>
19:29:03.992 [CM503012]: Inbound out-of-office hours rule (unnamed) for 10000 forwards to DN:802
19:29:03.990 Looking for inbound target: called=10000; caller=5555555555
19:29:03.987 [CM500002]: Info on incoming INVITE:
INVITE sip:[email protected]:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.11.61:5066;rport=5066;branch=z9hG4bKd225c3ee-e100-11e1-9fe8-f88d540e3c01
Max-Forwards: 70
Contact: <sip:[email protected]:5066;transport=udp>
To: "2222222222"<sip:[email protected]:5060>
From: "WIRELESS CALLER"<sip:[email protected]:5066>;tag=pxip-callid-1344392943-932606-16337-3060ds-7e93-2863435c
Call-ID: d223619e-e100-11e1-8ea5-be064cef10cc@3CX
CSeq: 27390 INVITE
Expires: 179
Allow: INVITE, ACK, BYE, CANCEL, NOTIFY, INFO, OPTIONS, REFER
Date: Wed, 08 Aug 2012 02:29:03 GMT
Supported: replaces, 100rel
User-Agent: Netborder Express Gateway/4.3.3
Content-Length: 0

 

[mtheory3cx]

Bump? I apologize if my first post was too verbose but I wanted to give as much information as I could.

 

[mtheory3cx]

Bump! Has anyone even installed a Sangoma PRI with Netborder Express? If so, was there anything special you had to do to have inbound calls route through DID? Sangoma told me it is a 3CX SIP rules configuration. Even thoughts or comments would help. Thanks.

 

[mtheory3cx]

UPDATE: For future reference, I'll post the results of my success on this issue in case anyone else needs it. But for some reason, in the inbound parameters of the PSTN, under "call source identification", I shouldn't have had "Request Line URI: User Part" ---> AuthID: authentication

And under Content of SIP fields, I needed to remove that last line: "Request Line URI: User Part ---> "CalledNum" number that has been dialed

After I removed those, inbound routes by DID were working flawlessly. Hope that helps anyone.