IPKALL dids verus PRI dids

Discussion in 'General' started by mike.strock, Jan 15, 2009.

  1. mike.strock

    Joined:
    Sep 6, 2008
    Messages:
    16
    Likes Received:
    0
    I have a DID that I got from IPKall.com which is working fine for incoming calls on my Elastix system.

    I got a PRI now, which delivers all 10 digits in the callerid. So I set up an incoming route as follows:

    Description: xxxxxx5357
    CID Number : xxxxxx5357
    Caller ID Number: xxxxxx5357

    Then under set destination, I have it going to a specific extension. When I run the debugging, and call in using that number, it says that it found the DID in question, but that it didn't find anything to deal with it, so it dropped out and went into my main ring group. I don't want that, I want to have it ring the specific DID only.

    The xxx actually has a real number in it, the correct number.

    -- Accepting call from 'xxxxxx1529' to 'xxxxxx5357' on channel 0/1, span 1
    -- Executing [xxxxxxx5357@from-pstn:1] NoOp("Zap/1-1", "Catch-All DID Match - Found xxxxxx5357 - You probably want a DID for this.") in new stack
    -- Executing [xxxxxx5357@from-pstn:2] Goto("Zap/1-1", "ext-did|s|1") in new stack
    -- Goto (ext-did,s,1)
    -- Executing [s@ext-did:1] Set("Zap/1-1", "__FROM_DID=s") in new stack
    -- Executing [s@ext-did:2] GotoIf("Zap/1-1", "1 ?cidok") in new stack
    -- Goto (ext-did,s,4)

    What am I missing here?

    Thanks.

    Mike.
     
  2. mike.strock

    Joined:
    Sep 6, 2008
    Messages:
    16
    Likes Received:
    0
    I was able to resolve this issue. I removed the number I had put into the CallerID field.

    All is working well now.

    Thanks.

    Mike.
     

Share This Page