TIPS Incoming DID string not working

[goblin]

PIAF Installed Version = 2.0.6.5 under *HARDWARE*
FreePBX Version = 2.11.0.32
Running Asterisk Version = 1.8.26.1
Asterisk Source Version = 1.8.26.1

This PBX is using a sip trunk with a mexican carrier, i have several DID configured with the las 4 digits of the DID in my incoming route but all incoming calls are getting " The number you have dial is not in service please try again", here is the output of the CLI.

  -- Executing [2490;tgrp=tstl-em015693236;trunk-context=ims.enlacetpe.com@from-trunk:1] Set("SIP/iusacell-discovery-00000020", "__FROM_DID=2490;tgrp=tstl-em015693236;trunk-context=ims.enlacetpe.com") in new stack
    -- Executing [2490;tgrp=tstl-em015693236;trunk-context=ims.enlacetpe.com@from-trunk:2] NoOp("SIP/iusacell-discovery-00000020", "Received an unknown call with DID set to 2490;tgrp=tstl-em015693236;trunk-context=ims.enlacetpe.com") in new stack
    -- Executing [2490;tgrp=tstl-em015693236;trunk-context=ims.enlacetpe.com@from-trunk:3] Goto("SIP/iusacell-discovery-00000020", "s,a2") in new stack
    -- Goto (from-trunk,s,2)
    -- Executing [s@from-trunk:2] Answer("SIP/iusacell-discovery-00000020", "") in new stack
    -- Executing [s@from-trunk:3] Wait("SIP/iusacell-discovery-00000020", "2") in new stack
    -- Executing [s@from-trunk:4] Playback("SIP/iusacell-discovery-00000020", "ss-noservice") in new stack
    -- <SIP/iusacell-discovery-00000020> Playing 'ss-noservice.gsm' (language 'en')
    -- Executing [s@from-trunk:5] SayAlpha("SIP/iusacell-discovery-00000020", "2490;tgrp=tstl-em015693236;trunk-context=ims.enlacetpe.com") in new stack
    -- <SIP/iusacell-discovery-00000020> Playing 'digits/2.gsm' (language 'en')
    -- <SIP/iusacell-discovery-00000020> Playing 'digits/4.gsm' (language 'en')
    -- <SIP/iusacell-discovery-00000020> Playing 'digits/9.gsm' (language 'en')
    -- <SIP/iusacell-discovery-00000020> Playing 'digits/0.gsm' (language 'en')
    -- <SIP/iusacell-discovery-00000020> Playing 'letters/ascii59.gsm' (language 'en')
    -- <SIP/iusacell-discovery-00000020> Playing 'letters/t.gsm' (language 'en')
    -- <SIP/iusacell-discovery-00000020> Playing 'letters/g.gsm' (language 'en')
    -- <SIP/iusacell-discovery-00000020> Playing 'letters/r.gsm' (language 'en')
    -- <SIP/iusacell-discovery-00000020> Playing 'letters/p.gsm' (language 'en')
    -- <SIP/iusacell-discovery-00000020> Playing 'letters/equals.gsm' (language 'en')
    -- <SIP/iusacell-discovery-00000020> Playing 'letters/t.gsm' (language 'en')
    -- <SIP/iusacell-discovery-00000020> Playing 'letters/s.gsm' (language 'en')
    -- <SIP/iusacell-discovery-00000020> Playing 'letters/t.gsm' (language 'en')
    -- <SIP/iusacell-discovery-00000020> Playing 'letters/l.gsm' (language 'en')
    -- <SIP/iusacell-discovery-00000020> Playing 'letters/dash.gsm' (language 'en')

Any ideas?

 

[briankelly63]

a normal inbound route requires all the digits not just the last 4. In the U.S. people often end up with issues created by extra digits that they didn't include like using 2015555555 instead of what's being sent which might be 12015555555. Some carriers add a plus. There is lots of info about routes and DID route issues you can search. Jut to be clear we are talking about the string for DID not CID

 

[goblin]

Yes for DID, my carrier adviced to use 4 and 10 digits of the number but still im getting number not valid when dialing those numbers.

 

[briankelly63]

in the CLI you'll see what they are sending you and the inbound route needs to match that exactly