04-05-2005 04:44 PM - last edited on 03-25-2019 09:21 PM by ciscomoderator
I configured a call handler aa with extention 2000.
Also configure a Cti Route Point with extension 2000 on Callmanager. The Cti Route Point will foward all calls to the voice mail.
When i choose a subscriber as the owner of the call handler, i can dial 2000 and reach the greeting.
But when i choose a public distribution list as the owner of the call handler, i hear system error when dialing 2000. Is there anything missed here?
Solved! Go to Solution.
04-05-2005 09:48 PM
I tried to replicate your issue on Unity 4.0(3) Sr and CCM 4.0(1) but did not have a problem. I changed the owner to a PDL with one subscriber.
I think your problem may actually be the MESSAGES link for the CH; make sure the recipient is valid. If it is NULL, then you would hear failsafe.
04-06-2005 02:45 PM
CSCec53192 Call Handler owned by distribution list causes failsafe
Symptom:
A Call Handler with a distribution list as an owner will cause failsafe.
The following events will be in the event log:
Event Type: Error
Event Source: CiscoUnity_ConvPH
Event Category: Error
Event ID: 141
Date: 10/8/2003
Time: 11:06:49 AM
User: N/A
Computer: SERVERNAME
Description:
Unable to get information from the mailuser. A possible cause could be a
corrupted database entry. The procedure call
IAvDohPropertyManager::QueryInterface(IID_IAvDohMailUser) returned [0x80004002]
on line 690 of file e:\views\cs_UE4.0.2.129\un_Conv2
\AvConvPhoneHandler\AvConvPHAttemptForwardSvr\AvConvPHAttemptForward.cpp.
Event Type: Error
Event Source: CiscoUnity_ConvPH
Event Category: Error
Event ID: 137
Date: 10/8/2003
Time: 11:06:49 AM
User: N/A
Computer: SERVERNAME
Description:
Unable to route the call to a subscriber. The procedure call
RouteCallToSubscriber returned [0x80004002] on line 180 of file
e:\views\cs_UE4.0.2.129\un_Conv2\AvConvPhoneHandler\AvConvPHAttemptForwardSvr
\AvConvPHAttemptForward.cpp.
Conditions:
A Call Handler with a distribution list as an owner will cause failsafe.
The owner of a Call Handler can be seen on the Profile page for the Call
Handler.
This defect will be resolved in Cisco Unity 4.0(4). Applying ES50 onto Cisco
Unity 4.0(3) will resolve the issue.
Workaround:
The owner of the Call Handler can usually be changed to a Subscriber and
still maintain the desired behavior for the Call Handler. The recipient
of the Call Handler message can be a distribution list without a problem.
Upgrading to Cisco Unity 4.0(4) or applying ES50 onto Cisco Unity 4.0(3) will resolve the issue.
04-05-2005 09:48 PM
I tried to replicate your issue on Unity 4.0(3) Sr and CCM 4.0(1) but did not have a problem. I changed the owner to a PDL with one subscriber.
I think your problem may actually be the MESSAGES link for the CH; make sure the recipient is valid. If it is NULL, then you would hear failsafe.
04-06-2005 02:45 PM
CSCec53192 Call Handler owned by distribution list causes failsafe
Symptom:
A Call Handler with a distribution list as an owner will cause failsafe.
The following events will be in the event log:
Event Type: Error
Event Source: CiscoUnity_ConvPH
Event Category: Error
Event ID: 141
Date: 10/8/2003
Time: 11:06:49 AM
User: N/A
Computer: SERVERNAME
Description:
Unable to get information from the mailuser. A possible cause could be a
corrupted database entry. The procedure call
IAvDohPropertyManager::QueryInterface(IID_IAvDohMailUser) returned [0x80004002]
on line 690 of file e:\views\cs_UE4.0.2.129\un_Conv2
\AvConvPhoneHandler\AvConvPHAttemptForwardSvr\AvConvPHAttemptForward.cpp.
Event Type: Error
Event Source: CiscoUnity_ConvPH
Event Category: Error
Event ID: 137
Date: 10/8/2003
Time: 11:06:49 AM
User: N/A
Computer: SERVERNAME
Description:
Unable to route the call to a subscriber. The procedure call
RouteCallToSubscriber returned [0x80004002] on line 180 of file
e:\views\cs_UE4.0.2.129\un_Conv2\AvConvPhoneHandler\AvConvPHAttemptForwardSvr
\AvConvPHAttemptForward.cpp.
Conditions:
A Call Handler with a distribution list as an owner will cause failsafe.
The owner of a Call Handler can be seen on the Profile page for the Call
Handler.
This defect will be resolved in Cisco Unity 4.0(4). Applying ES50 onto Cisco
Unity 4.0(3) will resolve the issue.
Workaround:
The owner of the Call Handler can usually be changed to a Subscriber and
still maintain the desired behavior for the Call Handler. The recipient
of the Call Handler message can be a distribution list without a problem.
Upgrading to Cisco Unity 4.0(4) or applying ES50 onto Cisco Unity 4.0(3) will resolve the issue.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: