Thanks guys! This makes sense.<br><br><div class="gmail_quote">On Fri, Feb 22, 2008 at 9:47 AM, Wes Sisk <<a href="mailto:wsisk@cisco.com">wsisk@cisco.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
Short Version:<br>
Your provider has made changes.<br>
<br>
Long Version:<br>
CM sends out CONNECT with DisplayIE. Your provider's switch does not
like the DisplayIE so they send back a status message. The status
message says callstate state=0x04. When CM receives this message it
has already proceeded to the connected state. CM detects this as a
state mismatch and clears the call. <memoryfade> I believe it
is DMS protocols which do not like the DisplayIE</memoryfade>.
We are attempting to 'fix' this scenario, but our 'fix' actually makes
us non-compliant with ISDN protocols by strict interpretation. See
CSCeg56289.<br>
<br>
Possible fixes short of upgrade to the newest fix:<br>
1) uncheck 'display ie delivery' on the gateway config page in CM<br>
2) change ISDN switch types. Also have your telco change the
switchtype configured on their d-channel.<br>
<br>
/Wes<br>
</div></blockquote></div><br><br clear="all"><br>-- <br>Ed Leatherman<br>Senior Voice Engineer<br>West Virginia University<br>Telecommunications and Network Operations