We are replacing our Nortel 81C with Meridian Mail with a Cisco Call Manager and an Unity server.
Right now our 81c acts as a hub for all inbound DID to 10 Nortel Opt 11s and also voice mail is centralize throught the 81C on Mer. Mail.
When we have tested putting Unity in place as a replacement for Mer. Mail. (QsIG on the 81c) any ACD queues configure to Night CAll Forward to Unity will not work right. The callers ID is attached as the begining of the ANI and Unity does not recognize it as a legitmate subscriber or call handler.
Example subscriber = 4510 (an ACD queue). Caller calls 4510 from cellphone# 616 555-1212. When it gets to Unity it thinks you want to go to a subscriber of 6165551212 which does not exist so it says "from a touch tone phone you may dial an extension at any time.
This does not happen when a Meridian phone is forwarded to Unity or call no answer to Unity. Only on an ACD queue that is logged out (or acts like a dummy ACD like a CTI route point).
Any suggestions?
Right now our 81c acts as a hub for all inbound DID to 10 Nortel Opt 11s and also voice mail is centralize throught the 81C on Mer. Mail.
When we have tested putting Unity in place as a replacement for Mer. Mail. (QsIG on the 81c) any ACD queues configure to Night CAll Forward to Unity will not work right. The callers ID is attached as the begining of the ANI and Unity does not recognize it as a legitmate subscriber or call handler.
Example subscriber = 4510 (an ACD queue). Caller calls 4510 from cellphone# 616 555-1212. When it gets to Unity it thinks you want to go to a subscriber of 6165551212 which does not exist so it says "from a touch tone phone you may dial an extension at any time.
This does not happen when a Meridian phone is forwarded to Unity or call no answer to Unity. Only on an ACD queue that is logged out (or acts like a dummy ACD like a CTI route point).
Any suggestions?