BCM50 networking w SIP?

[Deweyhumbolt]

A long day driving all over Az., and I get a SIP ? from a co-worker. I will copy/paste. I temporarily left the BCM world, before BCM50 3.0 purportedly, perfected SIP. Any help would be appreciated.

Question asked?

Main site is in CA running CS1000M cabinet rls 4.5
Cleveland is on BCM200 4.0 and San Antonio is on BCM200 4.0 that we just installed. All three sites are equipped with SIP trunks.
Centralized voice mail located in CA CallPilot 703t rls 2.02.
NRS is located in CA as well.
There are two routing tables built on each BCM. One is pointed to CA to be able to call from BCM to CS1000 and other one is to call between BCMs using 4 digit dialing.
If we call BCM DID call will ring 4 times and then roll to callpilot in CA and Will hit correct mailbox. CP will light up MWL.

Problem:

When you call from one BCM to another phone will ring 4 time and then will roll to FDN 2999 but we will get RNA on VM this time.


MVP's, I humbly ask your help.


Adversity is Opportunity

 

[pronei]

1. Do you have NMS licensed on your CallPilot?

2. What is your DCH msgs telling you on the CA site?

3. On the NRS, Check the BCM's config as a Gateway Endpoint, what is in the Tandem field of each BCM?

4. What is the NCOS of the SIP route on the CA site?

 

[Deweyhumbolt]

Thanks, pronei, I will get answers asap.

Adversity is Opportunity

 

[Deweyhumbolt]

1.yes
2.DCH 20 IMSG SETUP REF 00008182 CH 81 0 0 1 TOD 11:31:28
FEAT :CRID
FEAT :NAS
CALLING #:5112 NUM PLAN: PRIVATE/ABBREVIATED (CDP)
CALLED #:2996 NUM PLAN: PRIVATE/ABBREVIATED (CDP)
DCH 20 IMSG CONN ACK REF 00008182 CH 81 0 0 1 TOD 11:31:30
OVL000
>
DCH 20 IMSG DISC REF 00008182 CH 81 0 0 1 TOD 11:31:56
CAUSE :NORMAL CALL CLEARING
DCH 20 IMSG REL COMP REF 00008182 CH 81 0 0 1 TOD 11:31:56

3. blank.

4. NCOS 0

Adversity is Opportunity

 

[pronei]

Bump NCOS to 4. I have had trouble with SIP/H323 trunks set at 0.

In this particular scenario, I am assuming the following:
BCM 1 DN 5112 has called a DN on BCM 2.
BCM 2 user did not answer and FDN to 2999.
CS1000M DN 2999 = Callpilots CDN.

Your DCH Msg above states the call is going to DN 2996 and not DN 2999.

Possible fat finger?

or what is DN 2996?

 

[Deweyhumbolt]

I was doing workaround ACD/NCFW to 2999 still RNA.
We are going to patch up CP and CS1K tonight. Will see?


Adversity is Opportunity

 

[pronei]

Why work around?

Why not just FDN the BCM's phones directly to the CA's Callpilot CDN?

I have very similar situation here.

 

[Deweyhumbolt]

Because, the optimum way you describe didn't work. Just trying things.

Adversity is Opportunity

 

[pronei]

What happens when you dial the callpilot cdn directly from the BCM?

 

[Deweyhumbolt]

They got it figured out. On BCM rounting table entry pointed to BCM GW protocol must be set to CSE. Also, SIP RDB should have network redirect with TRO, set to Yes.

Thanks pronei!


Adversity is Opportunity