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

CM to MM ANI Problem using SIP

Status
Not open for further replies.

TDMorIP

Programmer
Mar 6, 2008
266
US
im having some issues getting the correct ANI to MM.
if i call a DID it routes to the extension and MM picks up with the mailbox....but if i call a VDN which points to a vector and allows the call to route to digits with cov y, it rings the sation.....but when gets to MM it is wrong and plays the default AA. CM 5.2.1 SP4, SES with newest SP and MM 5.2.1 Single Server with SP4P1. Public #ing is correct, tried change the the VDN to override no go either. list trace on the station or the TAC seems to show anything worthwile. had the same issue with a caller app coing off a vdn to vector. fix for that was to use the vector to send it to antoher vdn with a new vector that had messaging for active and tweaked the overides to get it to work....
anyone see this problem with SIP yet??
 
well i figured out what makes it work.....but i question why it fixed it. as to where the extension i am routing to is in the public table, the VDN is not. as soon as i added that # it worked. Does that sound correct?

 
can you give me a little more detail on what you did? we have this issue as well. it happens when an agent calls a vdn/vector that has a route to step that points to a vm extension. if you log the agent out of the phone, it works fine. if the agent is logged in, we get the standard AA welcome instead of the "please leave a message for".

i changed the vector from route to xxxxx to messaging skill xx and that fixed it. however, i don't want to change 1000 vectors so i'm looking for something else.
 
add the agents # to the pub. i think that should do the trick. i would basically add an entry for every possible dialplan extensiono in the pub for the VM trunk group.

 
the agent ID is a DID so is in the table. if the agent calls the mm box x18600 directly then we get the "please leave a msg". if the agent calls vdn x13442 then he gets prompted with the "welcome" aa. this occurs when the vector behind x13442 does a route to x18600 w/ cov y. if i change the vector step to a queue messaging skill 99 extension 18600, this works fine.

the problem appears to be with the way SIP handles the call through a vdn when an agent calls the vdn.
 
what release MM and CM do you have? i dont think its the SIP route but i ditched the SIP server and went direct...
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top