CCIS Voicemail?

[soaressteevan]

Hi friends,



I have one issue. we have 2000IPS system side "A", and side "B" connected on CCIS, and we have installed a third party voicemail software.the voicemail works fine on side "A".but on side "B" PBX people cant access it. 5 and 6 are the numbers to access each other. *9 and #9 is for message waiting lamp. we can leave message wiating lamp on "A" side by *9 followed by ext number,but "B" Side if they do *9 followed by extension number it doesnt permit.



so please let me know if CCIS 3rd party Vicemail works?

if it works is there any changes to be done?



Thanks in advance.

 

[MercuryComm]

If you are using a 3rd party voice mail AND CCIS you must use the MCI link to the voice mail. You can not use in- band signalling to set/cancel lamps for remote sites. Once you have MCI set up you will also get auto mailbox log in provided your voice mail is set up correctly.

 

[soaressteevan]

Hi MercuryComm....!

Thanks for your response.

we are using MCI link to the voice mail. site "A" where 3rd party voicemail is installed when they are trying to dial *9(MW Access code) followed by Extension number of Site "B" it shows Restricted on D'term phones. Both the side within the system MW access code works fine.

 

[BillB66]

I had a similar problem once before and found that it was actually related to a lcr issue.

It was back in 2005 so i cant detail exactly what i did but
these were the notes I made

"for mci MW to work
- determine which pattern the calls are using
eg , when dialling 290 - sent to A129

8A4001>290:0001
8A0001>1:07113
8A5071>000:05 ( RSC Class allowed is 05)

8105>8:3 - set RSC pattern 05 , for 8 to 3 "

Hard to believe it was rlevant , but it fixed my isue at the time .

hope it helps

 

[MercuryComm]

Try hooking up your laptop to the MCI port on the voice mail computer using a cable between your computers com port and the MCI port on the voice mail. Start up Hyper term or equivelent (set to the same configuration as the MCI port i.e. baud rate, stop bits, parity, etc.) and leave a message for a user. If the MCI port on the voice mail is working correctly you should see a "J" record from the voice mail telling the system to set lamps, cancel lamps, etc. This way you can confirm that you are in fact getting MCI records sent and that the voice mail is not sending lamp codes as in band or sending them on the analog ports. If you are not getting any "J" records you may need to re-do some config settings in the voice mail.

"we are using MCI link to the voice mail. site "A" where 3rd party voicemail is installed when they are trying to dial *9(MW Access code) followed by Extension number of Site "B" it shows Restricted on D'term phones."

You will get this (restricted) since the physical extension for site "b" is not in site "a" data base. You can't test by using your above listed method...The info must come from the MCI link to the CPU or APOO card in order for it to work. Did you program up the MCI port in the 2000 on either the CPU port or an APOO?

 

[BillB66]

I can email you a MCI simulator which you can you to test setting MCI features ?

 

[soaressteevan]

Thank you Guys for your reply.

Dear Mr.BillB66,

when we had programmed site B for A129 we were not able to access from site A, but now we have programmed Site B as 813(Network Station) now we are able to access,but only MW lamp *9 can not. and restriction class is fine. we have allowed in the particular class.

Dear Mr.MercuryComm,
We are getting all the strings from both sites. we have taken MCI port through CPU port sub dont have any AP00 Card.