FreePBX | Register | Issues | Wiki | Portal | Support

Mis Destination not working?


(Joseph Chrzempiec) #1

hello i try to adda mis destination with name and a number. I have IVR setup correctly when i go to that mis destination it says can not be completed. I searched around and I’m much for figuring things out so i got lost. Can someone please help me to figure out what is wrong or What am i doing wrong?

Joseph


(Dave Burgess) #2

Yes, we can, but you need to be specific and use logs and screenshots.


(Joseph Chrzempiec) #3

Hello can get i get the logs? never did that before?


(Joseph Chrzempiec) #4

I put in the correct number 267 area code followed by the number all together.

example: 2675555555


(Lorne Gaetz) #5

https://wiki.freepbx.org/display/SUP/Providing+Great+Debug#ProvidingGreatDebug-AsteriskLogs-PartII


(Joseph Chrzempiec) #6

Is there a way to getting the log from the web portal Not sure how to get the log from the console and put it on my pc?.


(Joseph Chrzempiec) #7
[2019-03-14 17:39:28] VERBOSE[10515][C-0006c28c] pbx.c: -- Executing [s@ivr-5:1] Set("DAHDI/4-1", "INVALID_LOOPCOUNT=0") in new stack
[2019-03-14 17:39:28] VERBOSE[10515][C-0006c28c] pbx.c: -- Executing [s@ivr-5:2] Set("DAHDI/4-1", "_IVR_CONTEXT_ivr-5=") in new stack
[2019-03-14 17:39:28] VERBOSE[10515][C-0006c28c] pbx.c: -- Executing [s@ivr-5:3] Set("DAHDI/4-1", "_IVR_CONTEXT=ivr-5") in new stack
[2019-03-14 17:39:28] VERBOSE[10515][C-0006c28c] pbx.c: -- Executing [s@ivr-5:4] Set("DAHDI/4-1", "__IVR_RETVM=") in new stack
[2019-03-14 17:39:28] VERBOSE[10515][C-0006c28c] pbx.c: -- Executing [s@ivr-5:5] GotoIf("DAHDI/4-1", "0?skip") in new stack
[2019-03-14 17:39:28] VERBOSE[10515][C-0006c28c] pbx.c: -- Executing [s@ivr-5:6] Answer("DAHDI/4-1", "") in new stack
[2019-03-14 17:39:28] VERBOSE[10515][C-0006c28c] pbx.c: -- Executing [s@ivr-5:7] Wait("DAHDI/4-1", "1") in new stack
[2019-03-14 17:39:28] VERBOSE[10510][C-0006c28b] pbx.c: == CDR updated on DAHDI/1-1
[2019-03-14 17:39:28] VERBOSE[10510][C-0006c28b] pbx.c: -- Executing [4@ivr-5:1] Goto("DAHDI/1-1", "ext-miscdests,3,1") in new stack
[2019-03-14 17:39:28] VERBOSE[10510][C-0006c28b] pbx.c: -- Goto (ext-miscdests,3,1)
[2019-03-14 17:39:28] VERBOSE[10510][C-0006c28b] pbx.c: -- Executing [3@ext-miscdests:1] NoOp("DAHDI/1-1", "MiscDest: GIGI1") in new stack
[2019-03-14 17:39:28] VERBOSE[10510][C-0006c28b] pbx.c: -- Executing [3@ext-miscdests:2] Goto("DAHDI/1-1", "from-internal,xxxxxxxxxx,1") in new stack
[2019-03-14 17:39:28] VERBOSE[10510][C-0006c28b] pbx.c: -- Goto (from-internal,xxxxxxxxxx,1)
[2019-03-14 17:39:28] VERBOSE[10510][C-0006c28b] pbx.c: -- Executing [xxxxxxxxxx@from-internal:1] Macro("DAHDI/1-1", "user-callerid,LIMIT,EXTERNAL,") in new stack
[2019-03-14 17:39:28] VERBOSE[10510][C-0006c28b] pbx.c: -- Executing [s@macro-user-callerid:1] Set("DAHDI/1-1", "TOUCH_MONITOR=1552599561.314719") in new stack
[2019-03-14 17:39:28] VERBOSE[10510][C-0006c28b] pbx.c: -- Executing [s@macro-user-callerid:2] Set("DAHDI/1-1", "AMPUSER=6097751699") in new stack
[2019-03-14 17:39:28] VERBOSE[10510][C-0006c28b] pbx.c: -- Executing [s@macro-user-callerid:3] GotoIf("DAHDI/1-1", "0?report") in new stack
[2019-03-14 17:39:28] VERBOSE[10510][C-0006c28b] pbx.c: -- Executing [s@macro-user-callerid:4] ExecIf("DAHDI/1-1", "1?Set(REALCALLERIDNUM=6097751699)") in new stack
[2019-03-14 17:39:28] VERBOSE[10510][C-0006c28b] pbx.c: -- Executing [s@macro-user-callerid:5] Set("DAHDI/1-1", "AMPUSER=") in new stack
[2019-03-14 17:39:28] VERBOSE[10510][C-0006c28b] pbx.c: -- Executing [s@macro-user-callerid:6] GotoIf("DAHDI/1-1", "0?limit") in new stack
[2019-03-14 17:39:28] VERBOSE[10510][C-0006c28b] pbx.c: -- Executing [s@macro-user-callerid:7] Set("DAHDI/1-1", "AMPUSERCIDNAME=") in new stack
[2019-03-14 17:39:28] VERBOSE[10510][C-0006c28b] pbx.c: -- Executing [s@macro-user-callerid:8] GotoIf("DAHDI/1-1", "1?report") in new stack
[2019-03-14 17:39:28] VERBOSE[10510][C-0006c28b] pbx.c: -- Goto (macro-user-callerid,s,16)
[2019-03-14 17:39:28] VERBOSE[10510][C-0006c28b] pbx.c: -- Executing [s@macro-user-callerid:16] GotoIf("DAHDI/1-1", "1?continue") in new stack
[2019-03-14 17:39:28] VERBOSE[10510][C-0006c28b] pbx.c: -- Goto (macro-user-callerid,s,30)
[2019-03-14 17:39:28] VERBOSE[10510][C-0006c28b] pbx.c: -- Executing [s@macro-user-callerid:30] Set("DAHDI/1-1", "CALLERID(number)=6097751699") in new stack
[2019-03-14 17:39:28] VERBOSE[10510][C-0006c28b] pbx.c: -- Executing [s@macro-user-callerid:31] Set("DAHDI/1-1", "CALLERID(name)=CHRZEMPIEC JOSE") in new stack
[2019-03-14 17:39:28] VERBOSE[10510][C-0006c28b] pbx.c: -- Executing [s@macro-user-callerid:32] Set("DAHDI/1-1", "CDR(cnum)=6097751699") in new stack
[2019-03-14 17:39:28] VERBOSE[10510][C-0006c28b] pbx.c: -- Executing [s@macro-user-callerid:33] Set("DAHDI/1-1", "CDR(cnam)=CHRZEMPIEC JOSE") in new stack
[2019-03-14 17:39:28] VERBOSE[10510][C-0006c28b] pbx.c: -- Executing [s@macro-user-callerid:34] Set("DAHDI/1-1", "CHANNEL(language)=en") in new stack
[2019-03-14 17:39:28] VERBOSE[10510][C-0006c28b] pbx.c: -- Executing [xxxxxxxxxx@from-internal:2] NoCDR("DAHDI/1-1", "") in new stack
[2019-03-14 17:39:28] VERBOSE[10510][C-0006c28b] pbx.c: -- Executing [xxxxxxxxxx@from-internal:3] Progress("DAHDI/1-1", "") in new stack
[2019-03-14 17:39:28] VERBOSE[10510][C-0006c28b] pbx.c: -- Executing [xxxxxxxxxx@from-internal:4] Wait("DAHDI/1-1", "1") in new stack
[2019-03-14 17:39:29] VERBOSE[10515][C-0006c28c] pbx.c: -- Executing [s@ivr-5:8] Set("DAHDI/4-1", "IVR_MSG=custom/welcome1") in new stack
[2019-03-14 17:39:29] VERBOSE[10515][C-0006c28c] pbx.c: -- Executing [s@ivr-5:9] Set("DAHDI/4-1", "TIMEOUT(digit)=3") in new stack
[2019-03-14 17:39:29] VERBOSE[10515][C-0006c28c] func_timeout.c: -- Digit timeout set to 3.000
[2019-03-14 17:39:29] VERBOSE[10515][C-0006c28c] pbx.c: -- Executing [s@ivr-5:10] ExecIf("DAHDI/4-1", "1?Background(custom/welcome1)") in new stack
[2019-03-14 17:39:29] VERBOSE[10515][C-0006c28c] file.c: -- <DAHDI/4-1> Playing 'custom/welcome1.slin' (language 'en')
[2019-03-14 17:39:29] VERBOSE[10510][C-0006c28b] pbx.c: -- Executing [xxxxxxxxxx@from-internal:5] Progress("DAHDI/1-1", "") in new stack
[2019-03-14 17:39:29] VERBOSE[10510][C-0006c28b] pbx.c: -- Executing [xxxxxxxxxx@from-internal:6] Playback("DAHDI/1-1", "silence/1&cannot-complete-as-dialed&check-number-dial-again,noanswer") in new stack
[2019-03-14 17:39:29] VERBOSE[10510][C-0006c28b] file.c: -- <DAHDI/1-1> Playing 'silence/1.ulaw' (language 'en')
[2019-03-14 17:39:30] VERBOSE[10510][C-0006c28b] file.c: -- <DAHDI/1-1> Playing 'cannot-complete-as-dialed.ulaw' (language 'en')

(Joseph Chrzempiec) #8

I put xxxxxxxxxx to hide the mumber it is going to sorry.


(Lorne Gaetz) #9

Looks like there is no outbound route with a pattern matching your dial string.


(Joseph Chrzempiec) #10

Normally outgoing calls goes only from extensions 700 to 740 and in the pattern. So i added a NXXXXXX and a second one NXXNXXXXX with no caller ID in the pattern and that let me dial to the Mis Destination. But it said you must dial a 1 with the number. So i went to the Mis destination put a 1 in there then i tried again and gotten and gotten the same message your number can not be completed.

screenshot below of the pattern

pattern


(Joseph Chrzempiec) #11

Just a update if i put in a local 609 area code that works find but if i put in a 267 area code i get that message you must dial a 1 before the area code. So i added a 1 in then the area code like this 1267XXXXXXX and i get that other message your call can not be completed please check the number and try again?


(Joseph Chrzempiec) #12

I have tried everything i can think of and no luck I’m more then stuck. I need help.


(Dave Burgess) #13

Since you are calling out on a DAHDI connection, your outbound TRUNK should be doing some of the work. You know, for example, that local calls are seven digits, and anything that isn’t a local call requires 1 and an area code.

You can split the necessary work for the outbound calls so that “whatever” form the call is sent to the trunk it is processed correctly.

In the TRUNK, using the form (prefix)+prepend|match/callerID, you could set up your trunk to do the following:
(609)+ |NXXXXXX/ # This strips the 609 area code off your local numbers
(1609)+ |NXXXXXX/ # This strips 1+609 off the local numbers
()+1|NXXNXXXXXX/ # This will add a to any 10-digit number that shows up.
()+ |1NXXNXXXXXX/ # This will match a properly formatted long distance number.

You can do the same thing in your outbound routes, but the point is that the number has to be in the right format for the Trunk to process it. If you don’t specify any outbound trunk rules, then any number that hits the trunk will be sent, even if it isn’t formatted correctly.

The point of this extra work is that not all trunks are created equally. I use a few different outbound providers:

  1. Local Loop (7- or 10-digit dialing is supported for all calls, 1 is required for long distance)
  2. VOIP Provider 1 (1+10 digit dialing is required)
  3. VOIP Provider 2 (10 digit dial is required for all calls, no country codes).

Rather than mess around with setting up my outbound routes to process calls, I just let the ROUTE set up the call with 10-digit dialing and let the outbound TRUNK fix the call so it works for the carrier.


#14

Presumably you live in New Jersey, which allows
both nxxxxxx and 709nxxxxx for in-state calls but you need 1nxxnxxxxx for any out of state calls

Check with your carrier for how it handles 732 856 and other in state area codes


(Joseph Chrzempiec) #15

Hello Dicko so i have to put for each area code i want to call like 609NXXXXXX and 856NXXXXXX for each one correct?So i have to put any prefix or prepend in there?


(Joseph Chrzempiec) #16

A little lost so i need to add a +1 follow by the area code of 609 then the NXXXXXX like this +1609NXXXXXX like that for each area code i would like to dial?


(Dave Burgess) #17

There are four fields on the Outbound Routes and Trunk Configurations.

The format is:
(prepend)
+ prefix
| match
\ extension

where “+”, “|”., and “\” are the field delimiters.

So, in this example, if this is in your TRUNK definition, the ‘number’ is “1NXXNXXXXXX” when the process starts (the output of your Outbound Route). There is no “prepend” (we don’t add anything to the number). We will strip the prefix ‘1’ off (since it’s delimited by the “+” and the “|”), and pass the number to the TRUNK Provider (DAHDI in your case).

The “(…)”,"+","|", or “\” are just the field delimiters in the example, you don’t actually add any of them, since they are all already on the screen.


(Joseph Chrzempiec) #18

So i need to add +1|NXXNXXXXXX Do i add the () quotes in the beginning and the / forward slash at the end?


(Dave Burgess) #19

No.

None of that.

There are two places that you can do outbound number manipulation. One is on the Outbound Route, one is on the trunk.

Look at the screenshot you supplied. In the box, you will see the delimiters. Go ahead - I’ll wait.

The first line in your screenshot, when “converted” to text (since I’m not going to mess with my outbound routes so I can give you a screenshot) is:

(prepend) + prefix | [411 / 7[01234]X]

See it?

The third line of your screenshot (in text) is

(prepend) + prefix | [NXXNXXXXXX / CallerID ]

The point of the exercise is to tell you that YOU need to know what your provider needs. I’m not going to call them and ask “Do one of your random customers need a ‘1’ on their outbound calls?” If you do, prepend a ‘1’ on the ones that need one. You can do that on the outbound route or on the trunk, but it’s ultimately going to be you that decides.

The requirements of your trunk provider will decide what you need and when you need it. There is no blanket rule.


(Joseph Chrzempiec) #20

Hello my fault there. I didn’t understand. I did add a 1 in there and I’m still getting the same error your call can not be completed.