Centralized vmail via VOIP between BCMs 3

[mroberts]

Hi all,

I am currently setting up centrailized vmail between two BCMs (3.6) using VOIP trunks and MCDN protocol. I've ALMOST got it. When I call an extension of the 'other' side, it forwards correctly to the vmail of the Host side but it gives me the general delivery mailbox, not the mailbox built for that extension.

I've got to be missing something small.... the host BCM is just not recognizing that the call is coming from a specific extension number and matching it to a created mailbox.

Any ideas?

MRoberts

http://www.a1teletronics.com

 

[acewarlock]

Thanks mroberts

 

[inet2xtreme]

We have this working on our BCMs. Some of the baseline items that we setup are: Coordinated Dialing Plan (CDP). All five of the BCMs are part of a CDP which was setup prior to this centralized VM setup. The "2" in front is the destination code for the remote system. That might be a difference of how your systems are setup. We also have four digit dialing as part of the CDP.

 

[Crowtalks]

You said:
The only part of the guide that I am having a problem with is where it's showing that the vmail DN is 400, it says to program Destination Code for VMDN to route to host system. In the screen shot pictured it shows the host system as having a destination code of 400 (host VMDN)AND a dest code of 2A.

If you have an active private network set up, then you're almost there. In the example, the '2' was the leading digit of the host's DNs (22xx) and the '400' was a stupid example of the VM DN. A better example would be, say, 2571.
If you have a destination code on the remote of 2A, and your host's VM DN is 2571, then you're probably Ok, though I went ahead and added the VM DN as a code. In the destination digits, you would have 2 2571 in the gateway pointing toward the host.
In the host, you would build a target line with the received digits of the VM DN, set the prime as the VM DN and then add that target line to the line assignment of the VM DN.
Build mailboxes in the host with the remote DN #s and check the boxes under system propeties.
At the remote, dial the host's VM DN and you should hear the password prompt.

 

[mroberts]

Okay!!! Now we're talking!

In my scenario I have 4 digit extensions on both sides. On the host side I have 3000 series extensions. On the remote side I have 2000 series extensions. The Host VMDN is 3471. SO
I should on the host side create a destination number of 2 (which I have)going to the remote side as per the CDP I have set up.
On the remote gateway, I should have destination digit of 2 and use CSE protocol.

On the remote side I should have a destination code of 3 going to the host die as per the CDP. Then in the remote gateway I should put destination digits of 3 3471 and use CSE protocol???

MRoberts

http://www.a1teletronics.com

 

[Crowtalks]

This is actually the way our DNs are numbered.

As far as the protocol and the gateways, If you already have four digit dialing set up between the system, don't screw with it. All we are doing is adding a destination digit on the remote gateway to point to the host's VM DN and a destination code on the remote as well. The destination code, will emulate the other one there that is already pointing to the host, (absorb 0, same route)
For your CDP, the host gateway has 2 as the destination code to see the remote, right?

In the remote gateway , as you stated, you should have 3 3471 (the two numbers separated by a space). In your call routing, on the remote, your destination codes are most likely 3A.

I added our VM DN also, which in your case would be 3471. I'm assuming the destination digits at each site is it's starting DN digit.

 

[Crowtalks]

To expand on the last sentence: I added our VM DN also, which in your case would be 3471. I'm assuming the destination digits at each site is it's starting DN digit.

I meant that I added it as a destination code on the remote, in the call routing.

 

[mroberts]

Okay, now I am completely confused. Here is my complete set up, someone please go through this and find my mistake!!! PLEASE!

Host BCM 400 3.6sw - 3000 series extension- VMDN 3471
Ext3221 is the main phone. It has target line 242 assigned to appr&rng on the set. Target line 241 has the rec'd #: 3221 on both the private and public.

VMDN 3471 has target line 242 assigned to appr&rng on it. Target line 242 has the rec'd#: 3471 on both the prvate and public. The prime set for target line 242 is 3471. The voice message center is NONE.

In CallPilot Line administration I also have target line 242 set to be answered by AA, in 0 rings. I have a mailbox 2261 built. I assigned it to ext 2261 with msg waiting and initialized it.I have Enable Network Transfers checked, Redirect DN checked and Enable External Initialization checked.

I have VOIP lines 001, 002 set up in Pool A. I have a destination code of 2 pointing to route 003 which uses Pool A with a DN type of Private.

In IP telephony, IP trunks, H.323 trunks, I have Call Signaling: Direct. Gateway protocol: CSE. On the remote gateway I have the destination IP, No QOS (we don't have any fallback programmed) Gateway type 3.6 and destination digits of 2.

Under Dialing Plan, Private Network I have Type: CDP. Private network ID 1, location code: nothing and prvate DN length of 4.

On the remote side - 2000 series extensions - test phone is 2261 which has target line 241 assigned to appr&rng on the phone. Target line 241 has the rec'd #: 2261 on both the private and public numbers - VMsg set is set to yes. Voice message center is center 1. In Telco Features the voice message center is set to External #: 3471. the MSg waiting strings are there automatically. The phone is fwded to 3471 (host VMDN)in 2 rings.

I have Route 003 pointed to Pool A which has the two VOIP trunks in it. DN Type is Private. I have Destination codes 3A pointed to Route 003 absorb length 0 and Destination code 3471 pointed to Route 003, absorb length 0.

I disabled the CallPilot vmail on this remote side as well.

Under Dialing plan I have it set up for Type: CDP, Private Network ID 2 and Private DN length set to 4.

Now when I call Ext2261 from Ext 3221, it rings the phone on the other side just fine, after two rings, it shows up in ext 3221's screen saying Calling line 242 (vmdn 3471's target line), then it goes to a fast busy!!!!
If I go over to extension 2261 and just pick up the handset and dial ext3471 on the host side, it picks up with the Host's general delivery mailbox.

HELP!!

under IP telephony trunks I have it set for Call Signaling: Direct, Gateway Protocol set at CSE. On the remote Gateway I have the desintation IP, QOS disabled Gateway Type 3.6 and the destination digits 3 3471.

I have



MRoberts

http://www.a1teletronics.com

 

[biv343]

I doubt this is causing your problems, but your PNI should be the same on both sides - one of your sites is 1, and the other is 2.

 

[mroberts]

Well, I had them both at one and thought maybe it was supposed to be different.... didn't make a difference but I will change it back. ;-)

MRoberts

http://www.a1teletronics.com

 

[Crowtalks]

You might want to try setting up a target line on the host system that is exclusive to the VM DN. Try taking the appear and ring on target line 242 off the 3221 ext and you already have 3471 prime for the 242 target line, so that is good.
I agree that the private network ID is suppose to be the same for every node on the network, It's the destination digits that vary

 

[mroberts]

I have target line 242 on the host site Prvate to: 3471 the VMDN already.

Target line 242 is NOT appr$rng on ext 3221. Just target line 241 which has rec'd # 3221.

I changed the private network ID... both have it set to 1.

Thanks for all your help
Melissa

MRoberts

http://www.a1teletronics.com

 

[mroberts]

I'm still coming up with a fast busy when I call an extension on the remote side, it follows the forwarding to 3471. I know this because on the Host system phone's display I see it say calling line 242 (which is the target line on the host side for the VMDN 3471. But then it waits a couple seconds then goes to Fast Busy.

Now I am not even getting the General Delivery mailbox as I was Friday evening.!!!

MRoberts

http://www.a1teletronics.com

 

[3Sixty]

Why have you set the target line 242 to ring on the voice mail extension on the BCM. I normally just switch it on the call pilot as you stated above.

Marshall

http://www.marshallshouse.co.uk

 

[mroberts]

Either way gets the same result. I have assigned the VM DN's target line 242 to appr&rng on the VM DN and I have removed it and just had the CallPilot's AA assigned to pick up line 242. Either way, I still get a fast busy after the phone forwards to 3471.

MRoberts

http://www.a1teletronics.com

 

[3Sixty]

Can you ring 3471 from the site and get answered by the voicemail?

Can you ring from an extension on the same site and get the voicemail?

Marshall

http://www.marshallshouse.co.uk

 

[mroberts]

GOT IT!!!!! Unbloody believeable! I forgot to check F982 and make sure the 'answer lines' box was checked!

That was it! It's working fine now!!!

Thank you all for the support!!!


MRoberts

http://www.a1teletronics.com

 

[bkrike]

DOH!
it's still a good thread for future reference

 

[senk1s]

Yes this is a good reference ...
MRoberts, when you get a chance coudl you come up with a cheatsheet like the one you did for the Norstar Centralized VM?
Thanks in advance

 

[mroberts]

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


MRoberts

http://www.a1teletronics.com

 

[senk1s]

As they say, all i had to do was ask !!
Thanks MRoberts