Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MICS 4.1 with NAM 4.0

Status
Not open for further replies.

kmpp

Vendor
Feb 25, 2012
71
US
I have a customer with a MICS 4.1 and a NAM 4.0. the lines are PRI with DID's to most all sets. The problem is ext. 4213
their 800 number is pointed at this DID and works fine, I have this ext forward no answer after 4 rings to VM dn 4264, but
the call ends up at the Gen. delivery MB. There is a mailbox built for 4213 and seems to work fine except inbound outside
calls don't go to this mailbox.

Any suggestions? Thanks
 
It's possible that the Delayed Ring Transfer (DRT) feature routes the calls to the voicemail before the Forward No Answer feature does. The DRT feature only applies to unanswered external calls. It would explain why internal calls properly go to the mailbox built for DN 4213.

Have a look at these settings to find out if DRT is causing the issue:

Lines > [Target Line for 800 Number] > Trunk/Line Data > Prime Set
System Programming > Feature Settings > DRT to Prime
System Programming > Feature Settings > DRT Delay
 
Plus check the prime set for the Trunks.
Sometimes the target line will get corupted, delete the target line unassign it and make a new target line on a different target line number and reassign.
 
Thanks for info, I was finally able to get back out the site.
I tried these suggestions:
800# pointing to ext. 4213 Line type-public (tried private 4213)> rec.# 4213> busy to prime> prime set 4213>clid 4213
DRT to prime tried no and set to yes with 6 and 10 rings.
I also deleted target line 158(4213) and built target line 163(4213)and reassigned to 4213, no change.
Also i discovered that if you make an intercom call to this ext. 4213 it goes to GD mailbox.
I turned off GD on voice mail and that did not work.
I noticed that the GD mail box had over 2,800 messages, never seen this before. They are in the process of going through them
and deleting.
This system was recently moved by someone and problems have come up, previously it had worked fine, according to customer.
This is a new customer so don't know all that was done previously tried to check all areas.
Obviously missing something.
Any help appreciated
 
There apparently is a limit, at MB prompt it says "Mailbox Full
 
Also, I deleted MB 4213 and rebuilt it.
They also have automatic set relocation on.
 
kmpp said:
Also i discovered that if you make an intercom call to this ext. 4213 it goes to GD mailbox.

Right now, this is your main issue. It has to be solved before you can even start hoping that unanswered calls on Target Line 163 end up in Mailbox 4213.

kmpp said:
Also, I deleted MB 4213 and rebuilt it.

We'll start from there and double check everything along the way.

Make Sure Mailbox 4213 Is Created
[ol 1]
[li]Check that Mailbox 4213 exists.[/li]
[li]Check that Mailbox 4213 is assigned to DN 4213.[/li]
[/ol]

Make Sure Extension 4213 Is Actually Extension 4213
[ol 1]
[li]Go to extension 4213.[/li]
[li]Press Feature *0, then press an Intercom button: the display shows the extension number.[/li]
[/ol]

Make Sure Mailbox 4213 Is Initialized
[ol 1]
[li]Go to extension 4213.[/li]
[li]Press Feature 981. The display should prompt for a password ("Pswd:"), and not for a login ("Log:").[/li]
[li]Check that the default password has been changed.[/li]
[/ol]

Make Sure Mailbox 4213 Answers Internal Calls for Extension 4213
[ol 1]
[li]Go to another extension than 4213.[/li]
[li]Press an Intercom button and dial 4213.[/li]
[li]Check that Mailbox 4213 answers the internal call after 4 rings.[/li]
[/ol]

Make Sure Mailbox 4213 Answers External Calls for Extension 4213
[ol 1]
[li]Go to any extension.[/li]
[li]Press an Intercom button, dial the destination code to get an external line and dial the 800 number for Target Line 163.[/li]
[li]Check that Mailbox 4213 answers the external call after 4 rings.[/li]
[/ol]

If something isn't right, reboot the NAM and start again from the beginning.

Let us know what you find.
 
I have gone through all of these steps, I am going back to site next week and will check all again.
Reboot was on my list of things to do if I could't get this resolved, I have also talked to customer about resetting
NAM and starting over, but the only problem seems to be ext. 4213
When you say reboot NAM your'e talking about graceful shutdown through feature 915?

Thanks for the help
 
kmpp said:
When you say reboot NAM your'e talking about graceful shutdown through feature 915?

Yes.

In addition to "System Shutdown", there is also "System Reboot", which conveniently shuts down and restarts the NAM. In any case, you should use the Graceful option.
 
I will be going out to site the first part of next week and will check all and post results.

Thanks for the help
 
Here are the things I checked today:


MB 4213 exists and assigned to ext. 4213
from ext. 4213 feature *o display shows 4213
from ext. 4213 feature 981 shows log
password has been changed from default.
if I go into 4213 mailbox through log and go to admin and then to call forward y/n and press n the prompt reads
cannot unforward, or words to that effect.
I checked from set 4213 that it was not forwarded feature #4
I took ext. 4213 off of MB 4213 and built MB 4500 with ext. 4213 (Initialized MB 4500), no change when you enter F981 from ext. 4213 the prompt is still log.
I think reboot is in order, this system was moved about a month and a half ago and customer said they have had problems
since.
Also, there are still approx. 1600 messages in the GD mailbox, customer is aware they have to be deleted.



Thanks

 
kmpp said:
from ext. 4213 feature 981 shows log

Right there, this is the problem.

The voicemail acts as if there was no mailbox assigned to extension 4213. Obviously, it shouldn't…

kmpp said:
I think reboot is in order

Me too.

After a reboot, if you still run into the same issue, the next steps would be:
[ol 1]
[li]Reset the NVM programming.[/li]
[li]Replace the NAM hard drive.[/li]
[/ol]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top