Thirdlane.com logo

Incoming calls not working

Posted by shanecaznet on Tue, 02/28/2017
Forums
Thirdlane platform General Questions

Hi All

We're just testing TL here. We've setup a trunk, tenant, assigned a bunch of DIDs and are able to make outbound calls without any issues.

Inbound calls dont work. They don't go anywhere and no trace of them in the CDR.

Looking at the output of asterisk, we see this:

-- Executing [0884706850@from-outside:1] Wait("SIP/caznet-00000012", "1") in new stack
-- Executing [0884706850@from-outside:2] Set("SIP/caznet-00000012", "CDR(did)=0884706850") in new stack
-- Executing [0884706850@from-outside:3] ExecIf("SIP/caznet-00000012", "0?Gosub(from-outside-fixinbound,0884706850,1)") in new stack
-- Executing [0884706850@from-outside:4] Set("SIP/caznet-00000012", "__INCOMINGCLI=0404847356") in new stack
-- Executing [0884706850@from-outside:5] Goto("SIP/caznet-00000012", "from-outside-redir,0884706850,1") in new stack
-- Goto (from-outside-redir,0884706850,1)
[2017-03-01 16:34:05] WARNING[19246][C-00000010]: pbx.c:6863 __ast_pbx_run: Channel 'SIP/caznet-00000012' sent to invalid extension but no invalid handler: context,exten,priority=from-outside-redir,0884706850,1

0884706850 is configured as a DID, assigned to my tenant and to the extension.

There is an inbound rule for this DID under the tenant.

Any ideas what might be going on?

Submitted by eeman on Wed, 03/01/2017 Permalink

just guessing as no US number ever starts with a zero, but it could be possible that your DID got rewritten as 884706850. Sometimes programming languages treat these as integers and integers will simplify themselves to an absolute value.

from CLI can you do 'dialplan show from-outside-redir' and see what the extension got written as?

Submitted by thirdlane on Wed, 03/01/2017 Permalink

If you add one DID with a number starting with 0 - like 0800 it seems to be stored correctly, but if you add a range - 0800 through 0810 - only the first number will keep the leading 0, and the rest will be created without it.

We will fix this in the future, in the meantime try a workaround - you can enter ranges of numbers starting with 0 by entering numbers without leading 0 - 800 through 810 and specifying 0 in the "prepend" field. Please confirm if the workaround works - if not we will look further.

Submitted by awoodman on Sat, 03/04/2017 Permalink

Yep, i had this exact same issue... In Australia, most numbers begin with a "0", so importing a range, i just did as you said and prepended 0...

Submitted by shanecaznet on Tue, 03/07/2017 Permalink

It was indeed that the 0 had been stripped using the bulk DID tool. I didn't realise, because it doesn't happen to the first one.

Leaving off the leading 0 and using the prepend feature is a work around.