I have a customer who had 4 Nortel 1

[twlcolorado]

I have a customer who had 4 Nortel Meridian systems linked with PRIs with Callpilot as a centralized voicemail. One was a very old Option 11C, which we replaced with a CM. We used QSIG on the PRI to link the CM to the main CS1000. Calls are processing properly, but when a call covers from the CM to the CS and on to Callpilot, I get a message that you have reached a voice mail system but the person at extension xxxx does not subscribe, even though the mailbox exists. You can log in to the mailbox fine from the CM.

Any ideas?

 

[DAVIDPAYNE]

You mat need to add those extension into the public-un table for the trunk group that is setup for voice mail.

 

[mattKnight]

I get a message that you have reached a voice mail system but the person at extension xxxx does not subscribe

I can't be 100% sure, but I reckon you have something wrong with the private / public numbering table. In effect, the CS is receiving data that it can't reconcile to a mailbox (maybe too many or too few digits)
At least, that's where I'd look first.

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[twlcolorado]

Both of those tables have been set up correctly per Avaya. Until I set them up, I got a message asking me to log in. Now, it is recognizing the extension, but not that it has a mailbox.

 

[kyle555]

So, you've got 3 elements to the call. Who's it for? Who's it from? and Who's sending this to me?
Normally, that should be "the voicemail pilot number" and "an outside caller's CLID" and "joe's extension 101 because of a forward no answer condition" or something.

"Who's it from?" sounds fine if Joe can call voicemail and be prompted for his password.

Now, how does CM get to voicemail? Normally - if you've not done this before - a phone has a coverage path that determines no answer treatment. The coverage path goes to a hunt group, 99 by convention - h99 in point 1 of the path, hunt 99 points to the AAR access code with digits to pitch to the voicemail trunk, and then AAR matches to a route and trunk and sends the call over.

Now, the call type in AAR should usually be unku (at least for Avaya voicemails) and youre route pattern would specify an addressing format in the bottom right - like lev0-pvt. All of those ducks in a row between dialed number, call type in ARS/AAR, numbering format in the route pattern, etc will determine if the call is private networking or public networking and whether the public or private unknown numbering table is called upon.

I'd suggest you make sure you're using private networking as the CallPilot/CS1k qsig setup might be that it needs to see numbering as private/local/on-net/whatever to get Joe's mailbox to answer. It unfortunately isn't as simple as ticking a private box and is rather complex, but ultimately based on what routing elements you triggered on.
Here's a good support notice where they broke something in there and they kind of give an overview of what I'm talking about:

https://downloads.avaya.com/css/P8/documents/101034284

All to say though, if you do it right, you can use that 1 PRI for PSTN access and private on-net calling and voicemail and if you manage CM numbering right, you'll always send your DID as CLID on the public type calls and always your short extension on the private ones.

 

[twlcolorado]

That is kind of the direction I have been going. Avaya had me change the aar table to lev0, and it had no effect. It sounds like it needs to be private all around. Unfortunately, this is a U.S. government site, and I am not local, so I have no direct access now that I am off site. Let me talk to my contact and see if I can get him to look at some of those things.

I do have some experience with CM, but only in the last couple of years (and way before that, all the way back to System 75), so I am still figuring this out.

Do you know which exact fields need to be set as private?

Thanks for everyone's ideas on this.

 

[kyle555]

well, AAR access code must be defined, coverage paths to hunt 99, hunt 99 must have the aar access code and vm pilot, aar must have it as type calltype unku, route as lev0-pvt numbering, private unknown table populated (which it sounds like you do), then maybe the qsig parts to check.

 

[twlcolorado]

I will check. Most of that is already done.

 

[jimbojimbo]

Not sure on this one but if my memory serves me you need to send a diversion header from CM to get to the correct mailbox.

 

[twlcolorado]

They are using Qsig on a PRI. I believe that a diversion header is a feature of SIP. Is that correct?

 

[kyle555]

Yeah, but "display system-parameters features" and head over to the qsig page. There's similarly relevant settings in there worth doublechecking.

 

[twlcolorado]

Thanks for all the help. I changed the trunk group formats to lev0-pvt and private, and now calls are routing to the Callpilot mailbox. Thanks again.