VM lamp lighting on remote site question????

[mrgauth]

I have a site connected back to a hub location that I am having a problem getting the lamps to light when VM messages are left. Both sites have Opt11's, but only one has a MM. There are PRI tie lines between the two sites and the lights used to work fine until the remote site bit the dust and we had to replace the CPU and reprogram from scratch. Everything is back up and running except the lamps.

Any suggestions on what I should be looking at. Remember the head end that has the MM has not changed in the slightest. So, nothing in VM should be changed I would think.


Thanks.

 

[mluckie1]

Check the PNI on both OPT 11C's. There is 1 in the RDB and 1 in the NET data block. Check farend, site without mail, and make sure that the MM ACDn is set up as a DSC in CDP.

 

[mrgauth]

As for the DSC, that is in place because you can dial the 4 digit VM DN directly from the remote site. I have DSC 72 and 73 built in the farend pointing to the headend. The voice mail DN is 7390. There is no ACDN built, but all the phones have 7390 as their HUNT and FDN. If you call them you get to MM after 4 rings, so, I know that works.

As for the PNI, that's a problem. The headend has a PNI of 1 on the PRI RDB and in CDB Net_Data, but the remote end does not even come up with the PNI prompt under ISDN on the RDB of the PRI. We were confused on that one ourselves and came to the conclusion that it did no because it does not have package 148 NTWK on that PBX. It was an old CPU and software card from another location that we used to get this up and running. Please don't tell me that we will absolutely need that in order for this to work.

Thanks.

 

[mluckie1]

When the system failed what cards were replaced? Even if you had an OPT11c they would have used your old Dongle and Keycodes so you should have all of the packages you had. If I'm not mistaken you will need the NTWK package for the centralized voicemail to work correctly.

 

[johnpoole]

check the rcap on your dch, mwk turns that on. add a mck key to your set to see if you can light a lamp both local and remote.. that will tell you where the trouble is.. also ld 96, enl msgo x (with x =to the dchl)

1. can you light a lamp on the remote end from the remote end..

2. can you light a lamp the remote from a local set.

3 if 1 =true then lamps will work on rem if 2 is also true the trouble is not the pri.. after that it's cdb or mail..

john poole
bellsouth business
columbia,sc

 

[mrgauth]

I looked in the manual and under RCAP for the dch I did not see MWK.

As for what will light the lamp and where, I will have the tech give it a try both ways. I am 250 miles away from the site unfortunately.

As for the MWK key, that is not absolutely necessary is it to light the lamp? None of the sets at that site had one before, so, I suspect it is not.

As to the previous question about having the software dongle from the old CPU card, no, we don't. It is a long story, but suffice it to say the tech did a booboo and we lost everything and had to take a card out of the storeroom that noone knew anything about til we stuck it in. Seems to be working fine except now for this message waiting thing.


Thanks all.

 

[johnpoole]

mwi is mess waiting to a dms, here is a dch for an opt 11 that gets message lamps from my rls 3, i was surprised to see the rcap on this one

ADAN     DCH 49
  CTYP MSDL
  GRP  1
  DNUM 10
  PORT 2
  DES  PARKRIDGE
  USR  PRI
  DCHL 49
  OTBF 32
  PARM RS422  DTE
  DRAT 64KC
  CLOK EXT
  NASA NO
  IFC  SL1
  SIDE NET
  SEMT 1
  CNEG 1
  RLS  ID  25
  RCAP ND2
  MBGA NO
  OVLR NO
  OVLS NO
  T200 3
  T203 10
  N200 3
  N201 260
  K    7

john poole
bellsouth business
columbia,sc