BCM50 and off-site CP

[pbxn]

I have a recently (Monday) vendor installed BCM 50. Current environment consists of PRI from Option61. All call routing from 61 to BCm works, and visa versa. The issue is when a call goes to voicemail, instead of the mb greeting, I get the CP default login in prompt. To me it seems that the BCM is not passing digits back to the CP, or is this a keycode issue? Waiting on vendor response now, just curious what I can find out while I am in a hold pattern. I'm more of an option guy, and this is my first 50, any insight would be appreiciated.
Thanks
BTW from the outside the CLID is being passed correctly to the BCM, if that helps.

 

[3Sixty]

IS the CP on the BCM or is it the Opt 61?

Marshall

http://www.marshallshouse.co.uk

 

[pbxn]

CP is on the Option61

 

[3Sixty]

Have you got the MCDN keycode for the BCM 50?

Marshall

http://www.marshallshouse.co.uk

 

[3Sixty]

Here is a guide for BCM to BCM from another thread.

BCM Centralized Voicemail

Both systems must have MCDN keycodes and VOIP trunk keycodes installed.

Host BCM Side - 3000 series extensions

Under Dialing Plan, Private Network
Type: CDP
Private network ID 1
Location code: nothing
Private DN length: 4

Under Telephony Services, Lines, VOIP lines

Trunk Type: VOIP (Read only)
Line Type: Pool B
Prime Set: DN 3221
Distinct Rings: none
Auto Privacy: Yes
Use auxiliary ringer: No
Full Auto Hold: No
Redirect to: blank

Under Services, IP Telephony, IP Trunks
H.323 header
FallBack: Enabled
Call Signaling: Direct
Primary Gatekeeper: 0.0.0.0
Back Up Gatekeeper: 0.0.0.0
Alias Names: None
Registration TTL: 60
Gateway Protocol: CSE
H245 tunneling: Disabled
Call Signaling Port: 1720
RAS Port: 0

Click the Remote Gateway Header
Click Configuration, Add Entry
Name: Enter the name of the other side BCM
Destination IP: Enter the IP address of the other side BCM
QoS Monitor: Enabled or Disabled.
Transmit threshold: 0
Receive threshold: 0
Gateway Type: Choose the software level of the BCM of the other side
Gateway Protocol: CSE
Destination Digits: 2 – Enter the beginning digit of the other side’s DNs.

Build a target line for each phone with Rec’d # of the extension.
Services, Telephony Services, Lines, Target Lines

Then assigned the target lines to ring only on their corresponding extensions.

Don’t forget to build a Target Line for the VMDN as well. Just do not assign it to ring on the VM DN.

Telephony Services, Call Routing, Routes
Click Add, route 003 (or any unused route)
External #: blank
Use Pool: B (or whatever pool your VOIP lines are in)
DN Type: private

Click on Destination Codes
Click Add, enter the beginning digit of the other side’s DNs
Then click on the Destination code key, then on the key of the code you just added.
Click the Schedules key
Click the Normal header
Use Route: route 003 (or the route you just built)
Absorb length: 0

Host CallPilot Programming

Assign the target line that has the rec’d digits of the VM DN to be answered by AA, in 0 rings.

Build a Mailbox for each phone including each ext on the far side. Assign them to their corresponding extension numbers.

Under System properties
Enable Network Transfers: check
Redirect DN: check
Enable External Initialization: check

Make sure under F982, that the answer lines box is checked!

[B[Remote side[/B] - 2000 series extensions

Under Dialing Plan, Private Network
Type: CDP
Private network ID 1
Location code: nothing
Private DN length: 4

Under Telephony Services, Lines, VOIP lines

Trunk Type: VOIP (Read only)
Line Type: Pool B
Prime Set: DN 2221
Distinct Rings: none
Auto Privacy: Yes
Use auxiliary ringer: No
Full Auto Hold: No
Redirect to: blank

Under Services, IP Telephony, IP Trunks
H.323 header
FallBack: Enabled
Call Signaling: Direct
Primary Gatekeeper: 0.0.0.0
Back Up Gatekeeper: 0.0.0.0
Alias Names: None
Registration TTL: 60
Gateway Protocol: CSE
H245 tunneling: Disabled
Call Signaling Port: 1720
RAS Port: 0

Click the Remote Gateway Header
Click Configuration, Add Entry
Name: Enter the name of the other side BCM
Destination IP: Enter the IP address of the other side BCM
QoS Monitor: Enabled or Disabled.
Transmit threshold: 0
Receive threshold: 0
Gateway Type: Choose the software level of the BCM of the other side
Gateway Protocol: CSE
Destination Digits: 3 – Enter the beginning digit of the other side’s DNs.

Build a target line for each phone with Rec’d # of the extension.
Services, Telephony Services, Lines, Target Lines

Then assigned the target lines to ring on their corresponding extensions.

Set the Vmsg set to Yes.

Then click on Telco Features
Voice Message Center: Center 1

Then Click on the main Telco Features key
Click Voice Message Center key
Click on Center 1 header
External #: enter the vmail DN of the Host side

Telephony Services, Call Routing, Routes
Click Add, route 003 (or any unused route)
External #: blank
Use Pool: B (or whatever pool your VOIP lines are in)
DN Type: private

Click on Destination Codes
Click Add, enter the beginning digit of the other side’s DNs
Then click on the Destination code key, then on the key of the code you just added.
Click the Schedules key
Click the Normal header
Use Route: route 003 (or the route you just built)
Absorb length: 0

This was put together by mroberts and alot of assistance from people on tek-tips

Marshall

http://www.marshallshouse.co.uk

 

[pbxn]

Yes I do have the MCDN and QSIG keycodes, they had to be installed via try before you buy, because vendor missed them on the order.

Thanks for the other post I will try to check this out while I wait.

 

[pbxn]

I had the user make a test call to my desk so I could see the clid, and the route/rt member displays.

 

[3Sixty]

Then assigned the target lines to ring on their corresponding extensions.

Set the Vmsg set to Yes.

Then click on Telco Features
Voice Message Center: Center 1

Then Click on the main Telco Features key
Click Voice Message Center key
Click on Center 1 header
External #: enter the vmail DN of the Host side


I would confirm you have set up this bit on the bcm 50.

Marshall

http://www.marshallshouse.co.uk

 

[pbxn]

thanks Marshall. Once I got there, I poked around a bit and noticed that the public and privite OLI was not set up. Once I entered in the dn's of the extensions, the CP recognized the # and went straight to their vm boxes.
Thanks again for the posts.

 

[hawks]

You should not have to use the OLI feature if your using CDP.

 

[pbxn]

I'm not 100% sure on the OLI ref. That was something that my vendor gave me to check.

 

[3Sixty]

Hi Hawks

I have set up a variety of different networked switches and if you want the extension number to be outputed accross the network you have to set the private OLI. I have read the same thing regarding the CDP but have never seen it work without the OLI parameter being set.

Marshall

http://www.marshallshouse.co.uk