[cisco-voip] ISDN/MGCP question

[Avner Izhar]

Have also seen that happens when the internal extension overlapped with a route pattern in ccm.
 
Check your dial plan to see that no internal extension match a route pattern in the first digits.
 
In mgcp, the solution was either to change the route pattern or to set the ccm service parameter called "Discard Non Inband Progress in Overlap Sending" to true.
 
HTH,
------------------------------------------- 
thanks, 
Avner Izhar 
CCIE#15999 (Voice), CCVP, CCSI# 31623 
Technical Training Manager 
CCBOOTCAMP - A Cisco Sponsored Organization (SO) 
Email: aizhar at ccbootcamp.com 
Toll Free: 877-654-2243 
Direct: +1-702-968-5100 = Outside the USA 
FAX: +1-702-446-8012 
YES! We take Cisco Learning Credits! 
Training And Remote Racks: http://www.ccbootcamp.com


________________________________

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Wes Sisk
Sent: Friday, February 22, 2008 06:47
To: Ed Leatherman
Cc: Cisco Voyp List
Subject: Re: [cisco-voip] ISDN/MGCP question


Short Version:
Your provider has made changes.

Long Version:
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.

Possible fixes short of upgrade to the newest fix:
1) uncheck 'display ie delivery' on the gateway config page in CM
2) change ISDN switch types.  Also have your telco change the switchtype configured on their d-channel.

/Wes

Ed Leatherman wrote: 

	Hoping a resident gateway guru can take a peek at this, to see if i'm barking up the wrong tree here
	
	We have a remote office with a legacy PBX of some sort which we have interfaced with our call manager 5.1.3 system via a PRI to a 2811 router (MGCP controlled). Has been working fine for about a year, but the past few days they are no longer able to call IP Phones on our network.. but they can make calls out of our PSTN gateways here on the main campus. Basically they call an IP Phone, it rings here but then has reorder tone. Calls setup and complete fine in the other direction, it's only calls from the remote site to main campus IP phones that cannot connect.
	
	I'm trying to get their telecom partner to take a look at their switch as well to see if anything changed, but trying to do my own troubleshooting in the meantime.
	
	I'm poking around at the trace files, 
	>From the call manager point of view, everything appears to work fine in the ISDN/MGCP call setup from what I understand, up until the CONNECT portion; I send CONNECT message to the remote switch, and get a STATUS message back with an error about IE not implemented, which is then followed up by a DISCONNECT from call manager. Right after I send the DISCONNECT I get the CONNECT_ACK that I was supposed to get from the initial CONNECT message. Then the call tears down normally.
	
	>From the IP Phone side, the media stream opens and then closes immediately according to the trace file.
	
	My question is, is the status message coming in before the connection_ack what is causing call manager to drop the call? 
	Newbie question, can I just uncheck "Display IE Delivery" in CCM to get rid of that error?
	
	OUT:
	CONNECT, pd = 8, callref = 0x8001
	Display i = 'Ed Leatherman'
	
	IN:
	STATUS, pd = 8, callref = 0x0001
	Cause i = 0x81E3 - IE Not implemented
	Call State i = 0x04 - Call delivered, ITU-T standard
	
	OUT (MGCP):
	MGCP Version 0.1
	S0/SU0/DS1-0/23 at HSC-East-VGW-1.nsog.wvu.edu
	Sequence 792352
	NotificationRequest (RQNT)
	RequestIdentifier(X): 17
	RequestedEvents(R): D/[0-9ABCD*#]
	SignalRequests(S)
	QuarantineHandling(Q): process,loop
	
	OUT (ISDN):
	DISCONNECT, pd = 8, callref = 0x8001
	Cause i = 0x80E5 - Message not compatible with call state or protocol error threshold exceeded 
	
	IN (ISDN):
	CONNECT_ACK, pd = 8, callref = 0x0001
	
	
	-- 
	Ed Leatherman
	Senior Voice Engineer
	West Virginia University
	Telecommunications and Network Operations 
	________________________________


	_______________________________________________
	cisco-voip mailing list
	cisco-voip at puck.nether.net
	https://puck.nether.net/mailman/listinfo/cisco-voip
	  


No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.20.9/1293 - Release Date: 2/22/2008 09:21



No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.516 / Virus Database: 269.20.9/1293 - Release Date: 2/22/2008 09:21