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

mm 5.2 not recognizing all digits being entered

Status
Not open for further replies.

tweege

Programmer
May 24, 2004
447
US
having a problem with my mm not recognizing all the digits being entered. it commonly happens when entering password, but also happens in other places where tui input is required.

for example, i dial my mm number from my extension and enter my password. it tells me invalid login and asks me to enter my mailbox number. when i enter the mailbox number and password it takes it everytime. however, i have discovered that if i enter a random number before i enter my password, it works everytime.

logs have been collected and it has been determined that cm is sending the correct digits, and that mm is getting those digits, but does not always recognize them.

both our bp and avaya have been on this for several weeks. we have updated to the latest service packs with no resolution. has anyone else ever seen this issue?
 
What is your integration method? What version of MM are you running? What PBX are you using (and version)?

Is your phone registered to (or connected to in the case of TDM) the same PBX MM is integrated with?

 
sip integration, modular messaging 5.2, comm manager 5.2. phones are registered to same cm as mm.
 
Are you using direct SIP connect or you are using SES or Session Manager to connect to MM?

What VoIP codec are you using? It should be G711 I believe. Is G711 also an available VoIP codec for the phone/network region/codec set?

 
it is direct sip connect, nothing in between it and the cm. it is using g.711 codec. it worked fine for years...this problem has just cropped up in the last couple months.
 
nothing has changed on the mm and cm side, other than staion MAC's. it does not happen on every user, and does not happen everytime on the ones it does happen on
 
it ended up being an issue with one of our medpro boards. we reset the board in question, and updated the firmware on it. all has been fine since.

thanks, tim
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top