From: Barman, Partha (PBarman@necbns.com)
Date: Thu Dec 11 2003 - 12:28:21 GMT-3
Hi John,
CFNA works! If I call a subscriber and the call goes unanswered it goes to Unity fine, same with CFB. But CFA doesn't work. No codec issue here because both gateway and Unity voicemail ports on the same device pool, and we are using g711 throughtout.
We'll give a try to the service parameter change that you suggested.
Thanks,
Partha
-----Original Message-----
From: John Messina [mailto:john@area100.com]
Sent: Wednesday, December 10, 2003 6:05 PM
To: Barman, Partha; ccielab@groupstudy.com
Subject: RE: CallManager w/6608 gateway & disconnect cause 80E5
I noticed your post on the unity forum as well. Assuming there is not a routing issue (unlikely) or codec mismatch (more likely) I have seen the following-(you didn't mention if the same behavior is experienced on CFNA). Have you opened call viewer on unity to confirm the call gets there?
Symptom
**********
Call fails when making a call from PSTN to IP to Unity VM. Problem only occurs When DN is set to CFA or CFB. Call works when set to CFNA.
Workaround
**********
Set the Service Parameter
DisableAlertingPI* to True
and the calls should not fail
Incoming PRI calls may be disconnected by Cisco CallManager.
Conditions:
This may happen when connected to certain ISDN networks. When CallManager is the User side of
the PRI, it may send a
Progress Indicator IE in the ALERTING message sent, which is invalid in some PRI protocols. In the
case where CallManager
immediately CONNECTs the call following this (such as when forwarding to voicemail or answering
with an auto attendant), the
ISDN network's complaint about the Progress Indicator may come after we have already sent the
CONNECT message, causing a
protocol violation, and CallManager will disconnect the call. This would only happen with an MGCP
controlled PRI gateway.
Workaround:
Change the service parameter "DisableAlertingPI" to True.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Barman, Partha
Sent: Wednesday, December 10, 2003 4:55 PM
To: ccielab@groupstudy.com
Subject: CallManager w/6608 gateway & disconnect cause 80E5
I have a 6608 blade with CallManager 3.3.3. Problem is when an incoming call is destined for Unity. As soon as the call from PSTN reaches a Unity VM port through the 6608 gateway, the caller gets a fast busy. Call is disconnected on the 6008 gateway with cause code 80E5 which means "Message not compatible with call state or protocol error threshold exceeded". The messaging sequence between 6608 and PSTN is as follows: Setup <-- Call Proc --> Alerting --> Connect --> Status <-- Connect_Ack <-- Status <-- Disconnect --> Release <-- Release-Comp -->
If you call Unity from an IP Phone, it works fine.
If you call an IP Phone from PSTN through the 6608 gateway, it works fine.
If an IP Phone is forward all to Unity, and you call the IP Phone, as soon as the call reaches Unity, caller receives fast busy.
Any ideas why this could be happening?
Thanks,
Partha
This archive was generated by hypermail 2.1.4 : Sat Jan 03 2004 - 08:25:39 GMT-3