Upgrade to 2.8 breaks outbound calling

i upgraded to 2.8 yesterday and it completely broke my outbound calling …

i went into the trunks config, and updated each one of them, supplying the requested caller-id value (not previously present for me in 2.7) and i verified that the dialed number manipulation rules matched what was expected for north-america.

then i went to the outbound routes (i have 3) and verified that everything was correct there.

hit apply to update freepbx, but no change. i get a fast-busy whenever i try to make any kind of outbound call.

what is more perplexing is that going to a shell and running asterisk -rvvv will show inbound calls perfectly, but outbound calls do not even register??? it’s almost like my sip-phones are not speaking properly with asterisk. i was hoping for some insights from the log files, but there’s nothing.

any ideas?

cheers,
-e

thanks for the quick response! i appreciate that.

did as you suggested … from-internal works like a champ. switched it back to say from-route1, made a call, and it failed again.

next, i removed the _ from the trunk name (from the error log as a notice, but just figured it couldn’t hurt to change that) and then went back into the outbound route and hit save again, just in case. applied all the settings, made a call, and failed again.

questions:

  1. should the name of the outbound route be ‘from-route1’ or simply ‘route1’? i have it as the latter.
  2. similarly, should the context of the extension read ‘route1’ or ‘from-route1’? pretty sure it’s the latter, which is what i have.
  3. when i click on Tools in FreePBX, there are menu options for Custom Extensions and Custom Destinations. i do not have anything filled in for those. could this be a problem? and if so, can you point me to an example of how these are used to tie everything together?

let me know if there’s any additional info i can provide. and thanks again for your help. i really appreciate it.

as far as the trunk or trunk name being an issue, it would never create the problem you are having.

It sounds very much like you are simply mis-configuring the Custom-Contexts.

I would suggest opening a new thread with a title that reflects you are having problems getting Custom Context to work as you think it should, and provide some reasonably specific information of what you have setup and what you are expecting and see if someone more familiar with Custom Context can come to your aid.

In this thread, they may not be looking at it at all. (Of course the other option if you are time constrained would be to purchase some support and get someone to have a look at your system and get it configured as you need.

Lastly, you may want to determine if you need the Custom Context module at all to do what you are trying to do. You can create Outbound Routes which include “CID” in the routing. The CID is basically the extension. So you can make a route that will only be used by a specific extension or group of extensions.

thanks … as suggested, here is the new thread:
http://www.freepbx.org/forum/freepbx/installation/custom-context-help-needed

first step, change the context for the extension in question to ‘from-internal’ and test it. Does it work then? If yes, then change it back to your custom-context and double check that there is a route in your custom context that matches the proper pattern, and test again.

If the first works, then something does not appear to be properly configured with your custom contexts.

back at this again today … need some help, please.

here is some additional info:

amportal.conf has this for bad-number:
AMPBADNUMBER=true

outbound routes:
i have 3 outbound routes (call them route1, route2, route3) which are configured as permanent routes with no CID or password. each route has the standard US dial patterns suggested by the UI. each route is associated with one trunk (call them trunk_1, trunk_2, trunk_3).

question:
the trunk names do have a _ in them – could this be a problem?

extensions:
you are correct in that i am using a custom context for each extension, to associate it with the appropriate route for the particular business unit. so extension 101, for example lists from-route1 as its context. extension 401 lists from-route3 for its context. both of these are sip extensions which are configured on my polycom 601 phone. i also have extension 201 which is an old analog phone that comes thru a pap2 device which has from-route2 specified for its context.

current status/symptoms:

  • incoming calls work fine, come thru IVR with no issues
  • outgoing calls do not work

debug/log info after firing “reload” in the asterisk cli (which i realize is deprecated – should i call “asterisk reload” instead?):
[Sep 29 08:45:09] NOTICE[14221] cdr.c: CDR simple logging enabled.
[Sep 29 08:45:09] DEBUG[14221] http.c: Nothing changed in http
[Sep 29 08:45:09] WARNING[14221] pbx_config.c: The use of ‘_.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘X.’ instead at line 1085
[Sep 29 08:45:09] WARNING[14221] pbx_config.c: The use of '
.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘X.’ instead at line 1086
[Sep 29 08:45:09] WARNING[14221] pbx_config.c: The use of '
.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘X.’ instead at line 1549
[Sep 29 08:45:09] WARNING[14221] pbx_config.c: The use of '
.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘X.’ instead at line 1550
[Sep 29 08:45:09] WARNING[14221] pbx_config.c: The use of '
.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘X.’ instead at line 1757
[Sep 29 08:45:09] WARNING[14221] pbx_config.c: The use of '
.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘X.’ instead at line 1758
[Sep 29 08:45:09] WARNING[14221] pbx_config.c: The use of '
.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘X.’ instead at line 1789
[Sep 29 08:45:09] WARNING[14221] pbx_config.c: The use of '
.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘X.’ instead at line 1790
[Sep 29 08:45:09] WARNING[14221] pbx_config.c: The use of '
.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘X.’ instead at line 1797
[Sep 29 08:45:09] WARNING[14221] pbx_config.c: The use of '
.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘X.’ instead at line 1798
[Sep 29 08:45:09] WARNING[14221] pbx.c: Unable to register extension ‘h’, priority 1 in ‘from-route1’, already in use
[Sep 29 08:45:09] WARNING[14221] pbx.c: Unable to register extension ‘h’, priority 1 in ‘from-route2’, already in use
[Sep 29 08:45:09] WARNING[14221] pbx.c: Unable to register extension ‘h’, priority 1 in ‘from-route3’, already in use
[Sep 29 08:45:09] WARNING[14221] pbx_config.c: The use of '
.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘X.’ instead at line 118
[Sep 29 08:45:09] WARNING[14221] pbx_config.c: The use of '
.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘X.’ instead at line 437
[Sep 29 08:45:09] WARNING[14221] pbx_config.c: The use of '
.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘X.’ instead at line 438
[Sep 29 08:45:09] WARNING[14221] pbx_config.c: The use of '
.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘_X.’ instead at line 439
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘from-internal-xfer’ tries to include nonexistent context ‘from-internal-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘from-did-direct’ tries to include nonexistent context ‘ext-findmefollow’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘from-pstn’ tries to include nonexistent context ‘from-pstn-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘from-route3’ tries to include nonexistent context ‘ext-fax’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘from-route2’ tries to include nonexistent context ‘ext-fax’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘from-route1’ tries to include nonexistent context ‘ext-fax’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘from-internal-additional’ tries to include nonexistent context ‘from-internal-additional-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘macro-hangupcall’ tries to include nonexistent context ‘macro-hangupcall-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘macro-simple-dial’ tries to include nonexistent context ‘macro-simple-dial-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘macro-exten-vm’ tries to include nonexistent context ‘macro-exten-vm-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘macro-vm’ tries to include nonexistent context ‘macro-vm-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘vm-callme’ tries to include nonexistent context ‘vm-callme-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘from-dahdi’ tries to include nonexistent context ‘from-dahdi-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘from-zaptel’ tries to include nonexistent context ‘from-zaptel-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘macro-outbound-callerid’ tries to include nonexistent context ‘macro-outbound-callerid-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘macro-dialout-enum’ tries to include nonexistent context ‘macro-dialout-enum-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘macro-user-callerid’ tries to include nonexistent context ‘macro-user-callerid-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘macro-dialout-dundi’ tries to include nonexistent context ‘macro-dialout-dundi-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘macro-dialout-trunk’ tries to include nonexistent context ‘macro-dialout-trunk-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘sub-pincheck’ tries to include nonexistent context ‘sub-pincheck-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘macro-auto-blkvm’ tries to include nonexistent context ‘macro-auto-blkvm-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘macro-auto-confirm’ tries to include nonexistent context ‘macro-auto-confirm-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘macro-confirm’ tries to include nonexistent context ‘macro-confirm-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘bad-number’ tries to include nonexistent context ‘bad-number-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-blackhole’ tries to include nonexistent context ‘app-blackhole-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘outrt-3’ tries to include nonexistent context ‘outrt-3-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘outrt-2’ tries to include nonexistent context ‘outrt-2-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘outrt-4’ tries to include nonexistent context ‘outrt-4-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘outbound-allroutes’ tries to include nonexistent context ‘outbound-allroutes-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘macro-record-enable’ tries to include nonexistent context ‘macro-record-enable-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘sub-flp-3’ tries to include nonexistent context ‘sub-flp-3-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘sub-flp-2’ tries to include nonexistent context ‘sub-flp-2-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘sub-flp-1’ tries to include nonexistent context ‘sub-flp-1-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘from-trunk-sip-trunk_3’ tries to include nonexistent context ‘from-trunk-sip-trunk_3-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘from-trunk-sip-trunk_1’ tries to include nonexistent context ‘from-trunk-sip-trunk_1-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘ext-trunk’ tries to include nonexistent context ‘ext-trunk-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘from-trunk-sip-trunk_2’ tries to include nonexistent context ‘from-trunk-sip-trunk_2-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘from-did-direct-ivr’ tries to include nonexistent context ‘from-did-direct-ivr-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘ext-local’ tries to include nonexistent context ‘ext-local-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘ext-did-0002’ tries to include nonexistent context ‘ext-did-0002-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘ext-did-catchall’ tries to include nonexistent context ‘ext-did-catchall-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘ext-did-0001’ tries to include nonexistent context ‘ext-did-0001-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘ext-did’ tries to include nonexistent context ‘ext-did-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘ext-test’ tries to include nonexistent context ‘ext-test-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-chanspy’ tries to include nonexistent context ‘app-chanspy-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-zapbarge’ tries to include nonexistent context ‘app-zapbarge-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-pickup’ tries to include nonexistent context ‘app-pickup-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-userlogonoff’ tries to include nonexistent context ‘app-userlogonoff-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘sub-rgsetcid’ tries to include nonexistent context ‘sub-rgsetcid-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘ext-group’ tries to include nonexistent context ‘ext-group-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘timeconditions’ tries to include nonexistent context ‘timeconditions-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘macro-agent-del’ tries to include nonexistent context ‘macro-agent-del-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘macro-agent-add’ tries to include nonexistent context ‘macro-agent-add-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘from-queue-exten-only’ tries to include nonexistent context ‘from-queue-exten-only-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘from-queue-exten-internal’ tries to include nonexistent context ‘from-queue-exten-internal-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘from-queue’ tries to include nonexistent context ‘from-queue-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘ext-queues’ tries to include nonexistent context ‘ext-queues-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘macro-toggle-add-agent’ tries to include nonexistent context ‘macro-toggle-add-agent-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘macro-toggle-del-agent’ tries to include nonexistent context ‘macro-toggle-del-agent-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-queue-toggle’ tries to include nonexistent context ‘app-queue-toggle-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘ext-miscdests’ tries to include nonexistent context ‘ext-miscdests-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-vmmain’ tries to include nonexistent context ‘app-vmmain-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-dialvm’ tries to include nonexistent context ‘app-dialvm-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-cf-toggle’ tries to include nonexistent context ‘app-cf-toggle-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-cf-unavailable-on’ tries to include nonexistent context ‘app-cf-unavailable-on-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-cf-unavailable-off’ tries to include nonexistent context ‘app-cf-unavailable-off-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-cf-on’ tries to include nonexistent context ‘app-cf-on-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-cf-off-any’ tries to include nonexistent context ‘app-cf-off-any-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-cf-off’ tries to include nonexistent context ‘app-cf-off-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-cf-busy-on’ tries to include nonexistent context ‘app-cf-busy-on-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-cf-busy-off-any’ tries to include nonexistent context ‘app-cf-busy-off-any-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-cf-busy-off’ tries to include nonexistent context ‘app-cf-busy-off-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-dnd-toggle’ tries to include nonexistent context ‘app-dnd-toggle-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-dnd-on’ tries to include nonexistent context ‘app-dnd-on-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-dnd-off’ tries to include nonexistent context ‘app-dnd-off-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-announcement-2’ tries to include nonexistent context ‘app-announcement-2-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-announcement-3’ tries to include nonexistent context ‘app-announcement-3-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-announcement-1’ tries to include nonexistent context ‘app-announcement-1-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-callwaiting-cwon’ tries to include nonexistent context ‘app-callwaiting-cwon-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-callwaiting-cwoff’ tries to include nonexistent context ‘app-callwaiting-cwoff-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘macro-systemrecording’ tries to include nonexistent context ‘macro-systemrecording-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-recordings’ tries to include nonexistent context ‘app-recordings-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘disa-dial’ tries to include nonexistent context ‘disa-dial-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘disa’ tries to include nonexistent context ‘disa-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-speakingclock’ tries to include nonexistent context ‘app-speakingclock-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-speakextennum’ tries to include nonexistent context ‘app-speakextennum-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-echo-test’ tries to include nonexistent context ‘app-echo-test-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-directory’ tries to include nonexistent context ‘app-directory-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-calltrace-perform’ tries to include nonexistent context ‘app-calltrace-perform-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘app-calltrace’ tries to include nonexistent context ‘app-calltrace-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘ivr-8’ tries to include nonexistent context ‘ivr-8-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘ivr-7’ tries to include nonexistent context ‘ivr-7-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘ivr-4’ tries to include nonexistent context ‘ivr-4-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘ivr-5’ tries to include nonexistent context ‘ivr-5-custom’
[Sep 29 08:45:09] WARNING[14221] pbx.c: Context ‘ivr-2’ tries to include nonexistent context ‘ivr-2-custom’
[Sep 29 08:45:09] NOTICE[14221] indications.c: Removed default indication country ‘us’
[Sep 29 08:45:09] NOTICE[14221] iax2-provision.c: No IAX provisioning configuration found, IAX provisioning disabled.
[Sep 29 08:45:09] WARNING[30372] acl.c: is not a valid IP
[Sep 29 08:45:09] WARNING[30372] acl.c: is not a valid IP
[Sep 29 08:45:09] WARNING[30372] acl.c: is not a valid IP
[Sep 29 08:45:09] WARNING[30372] acl.c: is not a valid IP
[Sep 29 08:45:09] ERROR[14221] chan_dahdi.c: Unable to load chan_dahdi.conf
[Sep 29 08:45:09] NOTICE[30375] chan_mgcp.c: Unable to load config mgcp.conf, MGCP disabled
[Sep 29 08:45:09] WARNING[14221] config.c: No ‘=’ (equal sign) in line 7 of /etc/asterisk/vm_general.inc

debug/log after making failed outbound call attempt:
[Sep 29 08:49:07] NOTICE[30372] chan_sip.c: Call from ‘201’ to extension ‘14095551212’ rejected because extension not found.

let me know what additional info i can provide and what next steps should be taken to get the outbound routes working properly.

thanks in advance!
-e

aha–just found some debug info …
[Sep 15 09:40:25] NOTICE[18042] chan_sip.c: Call from ‘101’ to extension ‘14095551212’ rejected because extension not found.

will search for “extension not found” and then post reference if/when i can resolve this.

just to clarify my issue … after migrating to 2.8 …

here is what works:

  • incoming sip calls
  • extension-to-extension dialing
  • *98 to access vmx

here is what does not work:

  • outbound dialing (get the error “extension not found”)

any ideas?
-e

blah…screw 2.8

i reverted back to 2.7 … think i’m just going to wait for 3.x to come out and get stable.

cheers,
-e

sorry you are having problems.

There is very little information in your posts to diagnose what is going on. If it is not seeing ‘the extension’ you are dialing then it looks like either your outbound routes were not generated, maybe you were using custom contexts and didn’t upgrade, or something else similar.

There thousands of 2.8 installs up and running, so something is just not right for some reason. You may want to see if you can provide a bit more information, have a look to see if the routes are not being generated, or other similar as I’m sure what ever is wrong with your setup is solvable.

Of course if there is nothing in 2.8 that you need or want, then I’m sure you can go on perfectly fine with 2.7 until you are ready to try and give it another shot.

hi philippe – thanks for the reply. i’m not down on freepbx – still love the product and have been doing my best to help/contribute.

but when my 2.7 works flawlessly, utilizing 3 sip trunks, 3 outbound routes, numerous sip and virtual extensions, 3 ivr’s (each tied to a separate sip trunk), a handful of queues and ring groups to get it all working … and then an upgrade to 2.8 breaks a very basic bit of functionality (outbound dialing), it’s rather frustrating.

i’m not sure i agree with you that i didn’t provide enough info. unlike some threads where people dump tons of conf files and output logs, i took the time to test a variety of scenarios, did some rather extensive google searches for the error message i was getting (which wasn’t an error, but a notice – see a few posts back for that) … and i posted my narrowed-down findings within the thread, both to assist in resolution and in case others were experiencing something similar.

my motivation for going to 2.8 was not about the feature set, per se, but more motivated by the desire to not be running archaic builds which are increasingly more difficult to troubleshoot. i’m not sure if there is a 2.9 planned, or if the current thinking is to encourage migration to 3.0. i may try again to upgrade to 2.8, but when you’re having a conversation with yourself in a thread asking for help, at some point you have to say ‘screw it’ :slight_smile:

thanks for taking the time to read my reply and thank you very much for all the excellent work you and the whole team continue to bring forth.

cheers,
-e

coroin,

I didn’t get the impression you were down on FreePBX.

I also could see that you spend time trying to look through the logs to see what was wrong. However sometimes, despite how ugly it can be, more of the log file (or other information) is helpful then not.

In your case, the bottom line, you did pull out some obviously helpful information, that Asterisk “can’t find the extension” which does tell me a couple things. The outbound-routes are not there at all. You are using a custom context for your extension which again doesn’t have any outbound routes installed. And in all cases, you do not have the bad-number context present (probably disabled in amportal.conf, and if not, then more signs that some dialplan is not being generated - but obviously some is.

So … unfortunately something is not going right for you:( And chances are, you will run into the same thing when you try and upgrade again whether to 2.8, or 2.9 (which yes a 2.9 is coming) and at that point 2.7 will go off support life. (And in any event, very few bugs are typically ‘fixed’ in the older of the two supported versions, which are currently 2.7 and 2.8.

So … I understand the frustration and of course 2.7 is still a very strong platform until you are ready to fight your battle again.

awesome – thanks for the hints on where to look for the disconnect. will investigate further and post back when resolved.

as always – appreciate you guys and all you do!

cheers,
-e