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

[Lelio Fulgenzi]

RE: [cisco-voip] Help with DID not working on PRIThe key is to have the DN (whether a translation or route pattern or device) in a partition that exists in the calling search space assigned to your trunks.

Because of the potential of interdigit timeout issues we have all our DID DNs in a seperate partition that are not accessibile by regular search spaces. For example, we have asked our service provider to send all 7 digits to us. Some of those are 767-XXXX numbers which would interfere with our residence numbers that begin 7XXXX. You'll want to keep this in mind. 

I'm sure I've tested in the test centre putting a 7 digit DN on a line on a phone which rings find when I dial the 7digit number from the PSTN.

If you are going the route of a translation pattern to a DN on a phone, the translation pattern's search space has to be able to access that DN on the device.

For example:
  a.. user dials 5551212 and you want this to ring on a phone with extension 666
  b.. PRI recieves dialed digits and performs whatever transformation you have asked for, let's take this example as dropping first three digits, so you get 1212
  c.. PRI search space goes through it's partitions and finds translation 1212 w/ transformation mask of 666
  d.. translation 1212 search space goes through it's partitions and finds a device with DN 666
  e.. device 666 rings

 
  ----- Original Message ----- 
  From: Voll, Scott 
  To: Lelio Fulgenzi ; cisco-voip at puck.nether.net 
  Sent: Friday, April 01, 2005 12:01 PM
  Subject: RE: [cisco-voip] Help with DID not working on PRI


  Thanks Lelio-

   

  I found it not attached to anything.  So I deleted it and added it to my 7960 as a DID and get fast busy again.  But if I delete that and make a translation pattern it works.  Any ideas why I can't add it to a device as a DID?

   

  Scott

   


------------------------------------------------------------------------------

  From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
  Sent: Friday, April 01, 2005 8:46 AM
  To: cisco-voip at puck.nether.net
  Subject: Re: [cisco-voip] Help with DID not working on PRI

   

  if you do a route plan dump to a text file you should find it right away.

   

    ----- Original Message ----- 

    From: Voll, Scott 

    To: Voll, Scott ; cisco-voip at puck.nether.net 

    Sent: Friday, April 01, 2005 11:33 AM

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

     

    Interesting find.  Since I removed the DID from the ATA, I was going to make a Translation pattern and now it gives me a message that it's uses somewhere else.  Any ideas how to find it quickly?  

    Scott

     

    From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Voll, Scott
    Sent: Friday, April 01, 2005 8:28 AM
    To: cisco-voip at puck.nether.net
    Subject: [cisco-voip] Help with DID not working on PRI

    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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20050401/0207b050/attachment.html