Yes we changed the firmware level to 2.1(15) like it the old unit was.
It looks like a lightning strike took out our 412 and CSU/DSU. It would work normally for a few days and then it start losing the config. Then we would have to load a backup config. After replacing it and taking it apart the board looked cooked at almost all of the solder joints.
Strange then... if you weren't on 2.1 before the lightning I might suspect it (don't I always?) but if it was working fine on 2.1 before... did you also have to replace your VMPro server by any chance? Dial by name won't work if users name prompts aren't recorded.
What happens when you try to use the module? Simply states it can't find any matches?
Of course not, but lightning strikes... could have hit the mains also and fried some servers via the AC outlets. Horrible nasty stuff.
From the dial by name token are you going to a transfer or a leave mail? If a transfer, does it ring the phone correctly but mess up leaving VM? If a leave VM token, try changing to a transfer to test. Also, drop an email token between the dial by name and the transfer/leave mail tokens, send yourself an email with $KEY in the body of the email. See what is being passed out of the dial by name.
Try the email thing, and using a transfer token. Don't think a screenshot would help if it was working before - more interested in where in the process the problem is occuring.
Are you using an Assisted Transfer action to transfer the callers? If you are, change it to a Transfer action. We have had this problem with 2.1 sites after upgrading (know issue).
Is there any way that this was not working ever since you upgraded and you have only noticed it now?
OK I drppoed the email token in. Before that I rebuilt the entire module so that might have fixed it. I will know tonight after 5:00 PM CDT. What should I look for in the email?
Assisted transfer and 2.1 hate each other, currently. If you are into pain (you never know some are) try using it from a queued or still queued callflow on a 2.1 IPO....
Yes it would be $KEY in the specific tab. In the email, check to see if it is emailing you the correct extension. For instance, if you use the dial by name to select "Smith" and Mr. Smith's extension is 2043, your email should contain 2043. You don't need to wait for after hours for that part, it won't interfere with operation - join the next result of the email token to your transfer item. Great troubleshooting tool.
Have you got your voicemail email feature working otherwise? It needs to be configured. Well worth the trouble, as I said that email token is a fab troubleshooting tool.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.