Feature 986 Problem 1

[Tom4848]

NAM 4.0 on MICS....when ext 221 attempts to use the Transfer VM feature, about 75% of the time the call is placed on hold and the display says "no call to connect"; we've replaced the phone with no luck. Any ideas appreciated.
Thanks
Tom

 

[exsmogger]

Try adding another intercom button to 221. There may not be any voice paths available to complete the transfer.

Brian Cox

http://www.jandjcommunications.com

 

[Tom4848]

Are there any settings for the lines that could be causing this?
Thanks
Tom

 

[exsmogger]

I don't think so. Usually it's a problem of insufficient voice paths to complete the transfer. Only other thing I can think of that would affect the voicemail transfer is all the voicemail channels being in use when the transfer is attempted.

Brian Cox

http://www.jandjcommunications.com

 

[Tom4848]

I thought the same thing, but she has three ICM buttons on her phone and it's a 12 channel NAM.....also, the message on her display is no party to connect and the call is siiting there flashing on hold. A response from one of the other groups said to make sure auothold is enabled....make any sense to you?

 

[exsmogger]

Is she putting the call on hold first? This would explain getting the message "No party to connect." Make sure she simply dials F986 with the call still live at her phone.

Brian Cox

http://www.jandjcommunications.com

 

[Tom4848]

no....it's happened to me as well, as soon as you press the F986 button the call goes on hold.....

 

[Norstarguru]

When you Press F986 on any norstar voicemail the call goes on hold and will ask you for a mailbox in the display, did you try a graceful reboot, and what release is the MICS?

 

[Tom4848]

No on the reboot.....3.0 on the software.
Thanks
Tom

 

[Arr]

Tom,
N*G is correct. If in doubt Reboot. Also double check your channel allocations just in case they got scrambled. Also try doing an XFtest to see if your F986 code is still active.. long shot here and wrong message on screen but..
Your 'no party connect' message is congruant with the call being put on hold before the system sees the F986. May not be procedure but an incomplete translation at the port level. Did you try from another set? Maybe try a BERT on the effected port.

PhM

 

[luv2ski]

try 6 icm buttons it should work fine

 

[AlquestTech]

I know this may sound odd, but is there a Cap assigned to this extension?

 

[Arr]

Noticed that if you dial too quickly on some KSUs the call is just put on hold and not transfered. So try dialing F986, waiting for the screen to prompt the Mbox, then enter the Mbox number, THEN when the screen says 'call transfered' press rls.

PhM

 

[Tom4848]

rebooted tonight and made some test calls which of course all worked......we'll see what happens in the morning. Curious about why the 6 intercoms would be a fix...the paths on her phone don't appear to be busy when it fails.
Thanks for all the replies and help; I'll keep you posted.
Thanks
Tom

 

[AlquestTech]

We had the same problem on an attendant station with a CAP module installed.
The power was being shipped remotely. We moved the aux power supply closer and the problem with F986 never returned. Not sure why, but it worked.

 

[Tom4848]

that's odd....we also have a CAP on this set, one of two in the system. Both are being powered remotely off the same transformer (the distance is under 50'). We'll put in individual transformers today and see what happens.
Thanks Again
Tom

 

[phitzer]

any luck with this one after adding 2 transformers? I've got the same problem m7324s with caps. exact same problem!

 

[wip]

What version of MICS Software are you using? Need to known for example NA-MICS 4.0 WI 6.00? There is a problem in some software releases and this completely corrected when
using NA-MICS 5.0 WI 6.02....

--work in progress

 

[atcom]

This problem definitely has to do with the CAP. The thing is, I don't know what the fix is.

 

[phitzer]

I'll try a new transformer