Wake Up Call specific outbound trunk

[stanhamil (Alan)]

I have several trunks set up on my installation and regularly use the Wake Up Call module with my family.

Outbound calls are via the default outbound route and trunk.

I want to select a different trunk to use for the outbound wake up calls.

In the settings for Wake Up Calls, I increased the “Max Destination Length” so that in the dialled number, I could include the prefix which I’ve defined within the dialling pattern for the particular outbound route which I want to use, but the call isn’t made as scheduled.

Has anyone come across this before? Does anyone know how I might specify a particular outbound route/trunk for calls made via the Wake Up Call module?

[peteravionsim (Peter Kulik)]

Is that specific outbound route above the default route under “Outbound Routes”?

Calls will start from the top and dial the first one that matches.

If I understand you correctly, you say you use a prefix that one of the outbound routes should ‘catch’, but you end up with the call not being made at all… this tells me the sytem tries to fire it off using another outbound route (and fails because it’s probably including (part of) the prefix), which means that the prefix also matches another route.

Try making a prefix with ** or ##… less risk of matching with other dialing rules

[stanhamil (Alan)]

The default outbound rule is right at the bottom of the list and there aren’t any outbound rules which conflict. I can successfully use my existing prefixes to dial from the relevant trunks via the telephones on my system.

I even tried using a *XX prefix with my outbound routes, as you suggested. This also didn’t work when I set up a wake up call to *XX-XXXXXXXXXXX (no call was made), but using a * as part of a prefix is a very useful feature and I wasn’t aware this would work, so thank you for that tip!

Right now, I still have no way to specify an outbound route when scheduled wake up calls are made.

[peteravionsim (Peter Kulik)]

Odd. I just tried it myself on FPBX14/Asterisk13 and my route is followed just fine, presenting the associated CID to my mobile.

At least that tells me that it is possible, so we should definitely try to find it in the routes in question.

In my case:
-using a route that is blocked for all extensions by Extension Routes, so that has no effect.
-route uses a 6 digit prefix (don’t ask), prefix is stripped, and then pushed onto the trunk listed in the route, which has the CID hardcoded (Force Trunk CID)
-the route is nr 6 in a seqeunce of 9, where 9 is the default with our main number. all others above and after route calls based on dialed number (different trunks for different countries etc).

Can you gather from the logs that it’s actually hitting the proper Outbound Route? if you search your logs for “@outbound-allroutes:” you should get a nice breakdown of all the steps it follows.

[2023-07-24 23:23:00] VERBOSE[59096][C-00001ac0] pbx.c: Executing [3311110626XXXXXXX@outbound-allroutes:2] Gosub(“Local/3311110626XXXXXXX@originate-skipvm-0000220e;2”, “sub-record-check,s,1(out,3311110626XXXXXXX,dontcare)”) in new stack
[2023-07-24 23:23:00] VERBOSE[59096][C-00001ac0] pbx.c: Executing [3311110626XXXXXXX@outbound-allroutes:3] ExecIf(“Local/3311110626XXXXXXX@originate-skipvm-0000220e;2”, “0 ?Set(CDR(accountcode)=)”) in new stack
[2023-07-24 23:23:00] VERBOSE[59096][C-00001ac0] pbx.c: Executing [3311110626XXXXXXX@outbound-allroutes:4] Set(“Local/3311110626XXXXXXX@originate-skipvm-0000220e;2”, “_ROUTEID=6”) in new stack
[2023-07-24 23:23:00] VERBOSE[59096][C-00001ac0] pbx.c: Executing [3311110626XXXXXXX@outbound-allroutes:5] Set(“Local/3311110626XXXXXXX@originate-skipvm-0000220e;2”, “_ROUTENAME=Sim Support”) in new stack
[2023-07-24 23:23:00] VERBOSE[59096][C-00001ac0] pbx.c: Executing [3311110626XXXXXXX@outbound-allroutes:6] Set(“Local/3311110626XXXXXXX@originate-skipvm-0000220e;2”, “MOHCLASS=default”) in new stack
[2023-07-24 23:23:00] VERBOSE[59096][C-00001ac0] pbx.c: Executing [3311110626XXXXXXX@outbound-allroutes:7] ExecIf(“Local/3311110626XXXXXXX@originate-skipvm-0000220e;2”, “1?Set(TRUNKCIDOVERRIDE=<320XXXXXX>)”) in new stack
[2023-07-24 23:23:00] VERBOSE[59096][C-00001ac0] pbx.c: Executing [3311110626XXXXXXX@outbound-allroutes:8] Set(“Local/3311110626XXXXXXX@originate-skipvm-0000220e;2”, “_CALLERIDNAMEINTERNAL=Wake Up Calls”) in new stack
[2023-07-24 23:23:00] VERBOSE[59096][C-00001ac0] pbx.c: Executing [3311110626XXXXXXX@outbound-allroutes:9] Set(“Local/3311110626XXXXXXX@originate-skipvm-0000220e;2”, “_CALLERIDNUMINTERNAL=*68”) in new stack
[2023-07-24 23:23:00] VERBOSE[59096][C-00001ac0] pbx.c: Executing [3311110626XXXXXXX@outbound-allroutes:10] Set(“Local/3311110626XXXXXXX@originate-skipvm-0000220e;2”, “_EMAILNOTIFICATION=FALSE”) in new stack
[2023-07-24 23:23:00] VERBOSE[59096][C-00001ac0] pbx.c: Executing [3311110626XXXXXXX@outbound-allroutes:11] Set(“Local/3311110626XXXXXXX@originate-skipvm-0000220e;2”, “_NODEST=”) in new stack
[2023-07-24 23:23:00] VERBOSE[59096][C-00001ac0] pbx.c: Executing [3311110626XXXXXXX@outbound-allroutes:12] Macro(“Local/3311110626XXXXXXX@originate-skipvm-0000220e;2”, “dialout-trunk,3,0626XXXXXXX,on”) in new stack

Last line shows it dials out on trunk 3 (literally position 3 in the Trunks view). Line 7 is where the CID is forced. Line 5 shows the route that’s used.

(I’ve masked the nrs, 0626XXXXXX is my mobile, <320XXXXXX> is the 9-digit CID without leading 0. Your situation is probably different wrt number formatting, but you get the picture)

(You may want to copy my logs and paste them in text editor so you get full lines. Easier to read.)

[dicko]

You might yourself want to use pastebin to replace your long inchoate copy/paste efforts

[stanhamil (Alan)]

I’ve finally managed to get it working!

Previously, I’d added a relevant prefix to the number a wake up call had to be made to, but when this was added, the call was never made.

I tried your suggestion of *XX which is great in general for defining which outbound route to use, but the Wake Up Call module dropped the *, so this didn’t work.

After previously deleting existing prefixes and replacing them with cleaner *XX prefixes, I then had to think of other numerical-only prefixes which I could use. As you can imagine, choosing these is a delicate task because I don’t want them interfering with regular calls.

However, I’ve created some prefixes with 00 in front of them, as well as the new *XX prefixes.

When entering the destination number with the relevant 00XX prefixes, wake up calls are now made through the relevant trunk/outbound rule.

I have no idea why this wasn’t working before.

[peteravionsim (Peter Kulik)]

Fair point. I’m new to using these kind of forums