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

Officelinx 11 not recognizing the extension when dialing the pilot number

fondog2

Systems Engineer
Jan 19, 2006
335
US
Hello to all,
We are using Officelinx as our centralized voicemail. One of our remote sites when dialing the 5 digit pilot number which goes to hunt 99 dials the access code then to the aar for routing to SIP trunk then to voicemail VM answers and plays the message please enter your mailbox number instead of asking for the password. Extension is built in VM, private unknown is set and see the name and the extension in the SIP trace. route pattern has lev0-prvt, SIP trunk is set to private unknown. What am I missing?
 
I found the issue which was one trunk was skipped when I added the private unknow. Now the only issue is the MWI doesn't light up. On page 2 I have sip-adjunct. Anything else need to be set to trigger this? I haven't looked at the logs yet but I am betting it is sending it but it isn't getting back to the station.
 
I did find this in the logs. Not sure how to read it. Do any of you?

16:16:50.052 [-] [F:processCTI: 'IDMS!<MD>1</MD><RSN>N</RSN><CALLEDID>758071</CALLEDID><CALLERID>526921</CALLERID><CALLERNAME>John Smith</CALLERNAME>'] [E:13]13 Type mismatch
 
I figured out why this was happening. After running several SIP traces I found and this takes a few seconds so don't get in a hurry, but when the voicemail sends the MWI through ASM to CM I was getting a 403 forbidden Invalid domain in the from header. This message was coming from CM back to ASM. I went back through and found the mistake on the signaling group of the trunk. Once I corrected it the light started working. Hope this helps the next person.
 

Part and Inventory Search

Sponsor

Back
Top