[cisco-voip] Help with DID not working on PRI

[Wes Sisk]

Overlap receiving really should only be used in Europe, Asia, and other 
areas that use variable length dial plans.

Be aware though - you have not resolved the overlapping dialplan issue.  
This will likely come back to bite you with some bizarre call routing in 
the future.

/Wes

Voll, Scott wrote:

>Is there any issue with leaving the overlap receiving set to false?
>Because it did work.
>
>Scott
>
>-----Original Message-----
>From: Wes Sisk [mailto:wsisk at cisco.com] 
>Sent: Friday, April 01, 2005 3:00 PM
>To: Voll, Scott
>Cc: cisco-voip at puck.nether.net
>Subject: Re: [cisco-voip] Help with DID not working on PRI
>
>overlap receiving=false should mask the problem.
>
>real problem is not db corruption, but configuration.  Somewhere you 
>have another pattern or DN that overlaps with 9490.  I'd guess 9.@ or 
>9.XXXXXXX.
>
>Get the CSS off the incoming gateway.  Then search each of the 
>partitions in that CSS to find the overlapping pattern.
>
>I have not tried Dialed Number Analyzer (DNA) with this case yet, but it
>
>really should find it.
>
>/Wes
>
>Voll, Scott wrote:
>
>  
>
>>So to fix this I set the overlap to false?  Or do I have a DB
>>    
>>
>corruption
>  
>
>>problem.  
>>
>>Scott
>>
>>-----Original Message-----
>>From: Wes Sisk [mailto:wsisk at cisco.com] 
>>Sent: Friday, April 01, 2005 2:40 PM
>>To: Voll, Scott
>>Cc: cisco-voip at puck.nether.net
>>Subject: Re: [cisco-voip] Help with DID not working on PRI
>>
>>No US ISDN protocols support "SETUP_ACK" that I know of. This usually 
>>happens because you have overlapping DN's/Patterns and have the CM 
>>service parameter overlap receiving set to true.
>>
>>Basically, the telco presents digits, cm ack's those digits, but then 
>>keeps waiting for more digits to resolve the overlap.
>>
>>CSCea42126
>>
>>/Wes
>>
>>Voll, Scott wrote:
>>
>> 
>>
>>    
>>
>>>I started having a problem with a DID yesterday. The DID has always 
>>>worked but know it's giving a fast busy. All other DIDs (400) seem to 
>>>be working over the three PRIs to the PSTN. I'm running CM 4.1.2sr1. 
>>>The DID is on an ATA186 but I have removed the DID all together and 
>>>still having the same problem.
>>>
>>>Here is an ISDN Q931 debug:
>>>
>>>Apr 1 16:21:43.747: ISDN Se3/0:23 Q931: RX <- SETUP pd = 8 callref = 
>>>0x0328
>>>
>>>Bearer Capability i = 0x8090A2
>>>
>>>Standard = CCITT
>>>
>>>Transer Capability = Speech
>>>
>>>Transfer Mode = Circuit
>>>
>>>Transfer Rate = 64 kbit/s
>>>
>>>Channel ID i = 0xA98393
>>>
>>>Exclusive, Channel 19
>>>
>>>Progress Ind i = 0x8283 - Origination address is non-ISDN
>>>
>>>Calling Party Number i = 0x2183, '5035084911'
>>>
>>>Plan:ISDN, Type:National
>>>
>>>Called Party Number i = 0x80, '9490'
>>>
>>>Plan:Unknown, Type:Unknown
>>>
>>>Apr 1 16:21:43.755: ISDN Se3/0:23 Q931: TX -> SETUP_ACK pd = 8 callref
>>>   
>>>
>>>      
>>>
>> 
>>
>>    
>>
>>>= 0x8328
>>>
>>>Channel ID i = 0xA9
>>>
>>>Cat6K#8393
>>>
>>>Exclusive, Channel 19
>>>
>>>Apr 1 16:21:43.783: ISDN Se3/0:23 Q931: RX <- STATUS pd = 8 callref = 
>>>0x0328
>>>
>>>Cause i = 0x82E1 - Message type not implemented
>>>
>>>Call State i = 0x06
>>>
>>>Apr 1 16:21:43.783: ISDN Se3/0:23 Q931: TX -> DISCONNECT pd = 8 
>>>callref = 0x8328
>>>
>>>Cause i = 0x80E5 - Message not compatible with call state
>>>
>>>Apr 1 16:21:43.943: ISDN Se3/0:23 Q931: RX <- RELEASE pd = 8 callref =
>>>   
>>>
>>>      
>>>
>> 
>>
>>    
>>
>>>0x0328
>>>
>>>Apr 1 16:21:43.947: ISDN Se3/0:23 Q931: TX -> RELEASE_COMP pd = 8 
>>>callref = 0x8328
>>>
>>>What does "Message type not implemented" Mean? Any help would be
>>>   
>>>
>>>      
>>>
>>great.
>> 
>>
>>    
>>
>>>Thanks
>>>
>>>Scott
>>>
>>>----------------------------------------------------------------------
>>>      
>>>
>-
>  
>
>>>   
>>>
>>>      
>>>
>>-
>> 
>>
>>    
>>
>>>_______________________________________________
>>>cisco-voip mailing list
>>>cisco-voip at puck.nether.net
>>>https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>>>   
>>>
>>>      
>>>