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 John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

CS1000M MG and Cisco Unity Voicemail Integration 1

Status
Not open for further replies.

tfp2006

Programmer
Apr 28, 2006
51
US
I have a CS1000M MG Rls 4.00T using a Cisco Unity voicemail Rls 4. Sometimes the Unity does not receive the caller id from the M2616 digital integration port and sends the calls to the default mailbox instead of the users. When I trace the calls it look like I am sending the caller id even on ones that fail. It seems like the problem starts out with a few failures and progresses to most of the calls failing to the wrong mailboxes. The customer spoke to Cisco but since this started not long after the PBX was patched they are pointing to the PBX. I dont know if its the patches but I would need to take all 253 of them out of service to test. Any suggestions would be appreciated.
 
Here are things I would consider or confirm with the 2616 integration ports:

~Set the CLS of the 2616 port to "HPR" (High Priority)

~Evenly distribute the 2616 TNs amoung different cards.

~Make sure the 2616 TNs do not have CLS TDD. I doubt that is a required CLS and it can degrade overall display update speed.




~~~
[small]GHTROUT.com | Get the Input/Output Manuals | Tek-Tips FAQs | Recent Replies[/small]
 
I had to take out mplr21888 because it caused one way talk path between cisco and nortel, this patch is supposed to fix the one way talk path, instaed it caused it. Take out all the patches and test, then put them in one by one, testing after each one, thats what I did.
 
Thanks. It only uses 1 2616 port with an add on module programmed with all 16 voicemail ports for caller id. The actual ports are analog and we tested them all. As for the patches perhaps I will look at them on ESPL and see if any pertain to caller id.
 
Hmm...I see. Well, check for TDD for sure, although I bet it is just ADD. TDD would drive the Cisco nuts.

CLS HPR could help, as well putting that TN in a low traffic loop and in card slot 0 (the first TN on the first card slot of a low traffic shelf in Group 0 is the highest CPU priority you can get)





~~~
[small]GHTROUT.com | Get the Input/Output Manuals | Tek-Tips FAQs | Recent Replies[/small]
 
GHTROUT- Thanks I will check theses items out. By the way your website is great!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top