Inbound Routing by Rules with PSTN gateway

[fredf]

With the newest version of 3CX installed, I have a Nortel BCM-400 installed as a PSTN device. I have added 4 DIDs and Inbound Rules to the gateway.

Now, when I set up the BCM-400 in 3CX, I installed it as Port 22. In the Port 22 config screen is where I added the DIDs, but Port 22 also has its own inbound route setting. When reading a post by mhanson "Inbound Routing By DID with a PSTN Gateway", he describes a similar issue related to DID's that I also experienced - that was resolved in R4. My question is related to Inbound and Outbound Rules, if the PSTN device is connected during office hours to the default extension 1000, which is neither setup or registered, 3CX WILL process the DID's (as of R4), but does not seem to process the Inbound or Outbound Rules if the Office Hours default extension is not registered, the 3CX will return "Target is not registered: Ext:Ext. 1000. Attempt to reach failed. Call is terminated". My Inbound call rules route properly for other registered extensions. In my PSTN setup, are Rules only processed if the extension is registered?

thanks

fredf

Server Log

14:34:27.949 [CM503008]: Call(16): Call is terminated

14:34:27.934 [CM503015]: Call(16): Attempt to reach <sip:[email protected]:5060> failed. Reason: Not Registered

14:34:27.934 [CM503015]: Call(16): Attempt to reach <sip:[email protected]:5060> failed. Reason: Not Registered

14:34:27.934 [CM503016]: Call(16): Target is not registered: Ext:Ext.1000

14:34:27.934 [CM503010]: Making route(s) to <sip:[email protected]:5060>

14:34:27.934 [MS210000] C:16.1:Offer received. RTP connection: 10.1.1.251:28280(28281)

14:34:27.934 Remote SDP is set for legC:16.1

14:34:27.934 [CM505003]: Provider:[BCM400] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Nortel Networks BCM VoIP Gateway release_41 version_41.530.0.33] Transport: [sip:10.1.1.26:5060]

14:34:27.902 [CM503001]: Call(16): Incoming call from 2523546132;phone-context=national.e164@(Ln.10004@BCM400) to <sip:[email protected]:5060>

14:34:27.887 [CM503012]: Inbound office hours rule (unnamed) for 10004 forwards to DN:1000

14:34:27.887 Looking for inbound target: called=752;phone-context=unknown; caller=2523546132;phone-context=national.e164

14:34:27.824 [CM500002]: Info on incoming INVITE:
INVITE sip:752;[email protected]:5060;maddr=10.1.1.26;transport=udp;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.1.1.251:5060;branch=z9hG4bK-4a0329b3-1c5ae5ed-6f290322
Max-Forwards: 70
Contact: <sip:2523546132;[email protected]:5060;maddr=10.1.1.251;transport=udp;user=phone>
To: <sip:752;[email protected]:5060;user=phone>
From: <sip:2523546132;[email protected]:5060;user=phone>;tag=40d41b68-fb01010a-13c4-4a0329b3-4d963110-4a0329b3
Call-ID: [email protected]
CSeq: 1 INVITE
Allow: INVITE, UPDATE, INFO, ACK, OPTIONS, CANCEL, BYE, NOTIFY, PRACK
Supported: 100rel, sipvc
User-Agent: Nortel Networks BCM VoIP Gateway release_41 version_41.530.0.33
Privacy: None
Content-Length: 0
x-nt-corr-id: [email protected]

 

[leejor]

In the call forwarding settings for extension 1000, have you set a destination for calls when the device isn't registered? Where do you want the inbound calls to go when there is no device registered?

 

[fredf]

ALL of the calls would be routed using either DID or Rules, no calls would actually be routed to 1000. Other routes would include registered remote devices (like a sip account on a VoIP modem or router), remote sip accounts, 3CX extensions, Skype accounts, bridged 3CX extensions, remote KEY systems, etc.

 

[leejor]

Well no matter how you would like the call to route, at the moment, going by the logs, it's trying to put the call through to extension 1000, which isn't registered and therefore, not knowing what to do with it, terminates it.It's trying to put the call through to 752 and doesn't have a place to send it other than (the default?) Ext 1000.Have you tried setting the call forward options on EXT 1000, when unregistered, to forward to another internal or external number? Normally an incoming call will go to an extension (either internal or external), a ring group or the automated attendant. What sort of call routing have you built to direct the incoming calls?

 

[fredf]

thanks leejor, here are a couple of examples that might help explain:

DID's on the BCM400 PSTN (these work fine in R4)
72* - routes a number beginning with 72 (on the BCM, dial 7 for the SIP GW, then your destination number) to extension 2000, which is a registered SIP account on a Draytek VoIP DSL router in a remote office where the FXS ports are connected to a Norstar ICS on lines 7 and 8. Extensions there are 221 - 236.

74* - routes like above, but to a different office. Return calls from remote offices, choose line 7 or 8, dial the extension, Rules will route the call to a BCM extension, to a different office, or other route based on the destination number pattern.

An Outbound Rule example that would apply to all outbound dialing, not just the BCM400, would be calls to Skype accounts via the Skype Provider using the speed dial numbers setup in Skype. The Outbound rule named "skype" is for any number prefix of 75, 3 numbers in length, strip the 1st digit and then route to "skype" provider. This rule works fine except for the BCM400 - it gets stuck going to the unregistered extension 1000. This is actually the example that you see in the log.

I am still learning a lot about how 3CX actually processes calls. My assumption (which could be totally wrong) is that inbound calls would go through the DID list and the Rules "before" being routed to the assigned action to the PSTN or Provider. Then I run into the routing options for "office hours" and "not office hours" - which makes sense to handle calls there first - so I guess I may be trying to go about this in the wrong way. Perhaps I simply need a BCM400 DID for 75* and a Rule for 75* - that may solve it. I will set that up today and reply back here. OOPS, a DID on the BCM400 for 75* is not an option since there is no direct way to route it to the Skype Provider like you can in the Outbound Rules.

thanks for thinking leejor

fredf