911 ringing busy through remote Office BCM 1

[MrYotsuya]

Hello all,We have a CS1000 Rel 5 (an upgraded Option 11c) with a remote office that has a BCM 200.

Whenever We Dial out from the remote office this output shows up in the PBX:

TIME: 13:35:46 AUG 30, 2011
NAME: IT Department
ORIG DN: 7938
SITE: SCC
LOC: 139 S PEBBLE BEACH

DES: 7938
SET: IP SET
ERL: 260
TER RTMB: 40-96 ACOD: 7840
CALLED#: 911
CALLING#: 6107

I can call from the main office just fine but the remote gives a busy signal. I removed the misdial feature as a troubleshooting measure but still the issue persists. Any Ideas? Thanks!

 

[allenmac]

Can you post the RDB from your TIE route(s)?

 

[MrYotsuya]

sure The Office uses Route 40



TYPE RDB
CUST 00
ROUT 40
DES VZSIP
TKTP TIE
M911P NO
ESN NO
CNVT NO
SAT NO
RCLS EXT
VTRK YES
ZONE 010
PCID SIP
CRID NO
NODE 1002
DTRK NO
ISDN YES
MODE ISLD
DCH 40
IFC SL1
PNI 00001
NCNA YES
NCRD YES
TRO YES
FALT NO
CTYP UKWN
INAC YES
ISAR NO
DAPC NO
MBXR NO
PTYP ATT
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD 7840
TCPP NO
TARG
CLEN 11
BILN NO


PAGE 011

OABS
INST
IDC YES
DCNO 1 *
NDNO 1
DEXT NO
DNAM NO
ANTK
SIGO STD
STYP SDAT
ICIS YES
TIMR ICF 512
OGF 512
EOD 13952
DSI 34944
NRD 10112
DDL 70
ODT 4096
RGV 640
GRD 896
SFB 3
NBS 2048
NBL 4096

IENB 5
TFD 0
VSS 0
VGD 6
SST 5 0
NEDC ORG
FEDC ORG
CPDC NO
DLTN NO
HOLD 02 02 40
SEIZ 02 02
SVFL 02 02
DRNG NO
CDR NO
VRAT NO
MUS NO
RACD NO
MANO NO
FRL 0 0
FRL 1 0
FRL 2 0
FRL 3 0
FRL 4 0
FRL 5 0
FRL 6 0
FRL 7 0
OHQ NO
OHQT 00
CBQ NO
AUTH NO
TDET NO
TTBL 0
ATAN NO
OHTD NO
PLEV 2
ALRM NO
ART 0
SGRP 0

 

[allenmac]

Ok. INAC is yes, so the CS1000 will add the proper Access Code to whatever it receives.

Can you turn on D-Channel messaging and make a test call from the BCM to see what digits the BCM is sending to the CS1000?

 

[MrYotsuya]

Ok I'm a noob with the BCm how would I do that? I do see this on the main Cs1000 prompt:


TIME: 13:35:46
AUG 30, 2011
NAME: IT Department
ORIG DN: 7938
SITE: SCC
LOC: 139 S PEBBLE BEACH
DES: 7938
SET: IP
SET ERL: 260
TER RTMB: 40-96
ACOD: 7840
CALLED#: 911
CALLING#: 6107

 

[allenmac]

Do you know what version of software the BCM is running?

I only have 1 or 2 old BCMs running 3.6/3.7 left on my network.

In BCM Configuration Manager I would navigate to:

Services-->Telephony Services-->Call Routing-->Desitnation Codes

You should see one that looks like '91A'.

Expand the entry, and look at Schedules-->Normal. You should see 2 fields: Use Route, and Absorbed Length.

The Absorbed Length field tells the BCM how many digits to strip off of the Destination code before it sends the remaining digits to the destination in the 'Use Route' field.

If your CS1000 is configured correctly with the Country and International dialing codes in LD 15, then you should be able to send the NPA-NXX-XXXX without the leading 1 to the CS1000.

When the digits get to the CS1000 the call type should be NPA, which will cause the CS1000 to add a 1, and INAC will cause the CS1000 to add the proper access code to the beginning of the dial string (usually 9).

So if the BCM send 202-555-1212 to the CS1000. The CS1000 would automatically reformat the dial string to '9-1-202-555-1212' and then process the call.

 

[allenmac]

My previous posts were assuming that your users were trying to dial a number other than 911.

If your users are trying to dial 911, and getting a busy, then you may have other issues with the way the call is being tagged by any combination of the BCM and CS1000.

If I were troubleshooting this, I would look at a test call during each leg of your network, to try to see what is actually going on.

There is a BCM monitor application that should provide the BCM-outbound data, and D-Channel messaging on the CS1000 should give you the rest.

 

[MrYotsuya]

I did see the BCM monitor but when I had them Dial out it didnt show any routes. I also did not see a D-Channel monitor on that module.

 

[allenmac]

I haven't used it for years, but it was a little convoluted in how you had to set up the d-channel monitoring.

The documentation should explain it, if not, maybe someone in the BCM forum here could explain it.

 

[MrYotsuya]

also I have a BCM 4.0 and there is the 9A route that doesnt strip the 911 number but strips 1 off of the 9911 (as it should)

 

[MrYotsuya]

Thanks I'll Try there! I thought since the calls rout through the CS1000 (they are IP phones) that it maybe something on the CS1k end.

 

[Reusser]

Seems to me - if PBX spitting out the 911 info BCM is sent to PBX ok. Problem might be Telco might be the problem.

Notice Route 40 is SIP

Would recommend doing the following:

when traffic on Rlt 40 is slow, turn on Dchannel messages for Virtual trunks. Dial 911. report back the Dchannel messeges - be dure to incluse incoming messages that might tell why telco is rejecting call.

With SIP, usually CLID is used for Billing and call may not be displaying a valid CLID when 911 is called from BCM.

 

[MrYotsuya]

It was The Telco. We are moving our SIP lines to a new Vendor adn they did not have the lines for this office for some reason! Thanks everyone it was as you said the BCM is sending the info but the Telco is rejecting it.

 

[allenmac]

Usually, you can work with the Telco to get them to pass the call. I had a problem with the last CS1000 I installed. The telco was receiving name display with the 911 call and was rejecting because of that. 2 test calls later, they set their system to ignore name display on 911 calls, and everyone's happy.