Setup inbound call routing with FreePBX 13
-
@JaredBusch I still think of this as a "new thing" whereas pre bandwidth.com owning schmooze there was no mysql.
Somewhere maybe around 2008, before or after.
-
@bigbear said in Setup inbound call routing with FreePBX 13:
@JaredBusch So the conf files are still getting written to, but editing the conf files does no good as the database overwrites them?
Not related, but Unifi stuff on the controller works the same way. Editing the files directly on the devices is over written the next time the controller talks to it.
-
@bigbear said in Setup inbound call routing with FreePBX 13:
@JaredBusch I still think of this as a "new thing" whereas pre bandwidth.com owning schmooze there was no mysql.
Somewhere maybe around 2008, before or after.
The FreePBX GUI has always been designed around a database to store the settings and then writing to the conf files all at once. It was never designed to read raw conf files and write back to them immediately.
-
-
@JaredBusch over on FreePBX forums you references a cfg file to edit, I am about to load up FPBX 14 and was curious where that file is. TFTBOOT directory somewhere?
The only way to get the Yealink T5 android apps installed is apparently to add the pkg path to a provisioning file. This weekend I am determined to figure out how to hard provision with FreePBX.
-
@bigbear said in Setup inbound call routing with FreePBX 13:
@JaredBusch over on FreePBX forums you references a cfg file to edit, I am about to load up FPBX 14 and was curious where that file is. TFTBOOT directory somewhere?
The only way to get the Yealink T5 android apps installed is apparently to add the pkg path to a provisioning file. This weekend I am determined to figure out how to hard provision with FreePBX.
Are you using the FreePBX Endpoint Manager to config your phones? If so, the basefile edit is an option there. If not, then you have to make it by hand and put it in the
/tftpbootdirectory yourself.For the record I almost always do the config files by hand because once you learn it, it only takes minutes to replicate for bunches of extensions.
-
@JaredBusch said in Setup inbound call routing with FreePBX 13:
@bigbear said in Setup inbound call routing with FreePBX 13:
@JaredBusch over on FreePBX forums you references a cfg file to edit, I am about to load up FPBX 14 and was curious where that file is. TFTBOOT directory somewhere?
The only way to get the Yealink T5 android apps installed is apparently to add the pkg path to a provisioning file. This weekend I am determined to figure out how to hard provision with FreePBX.
Are you using the FreePBX Endpoint Manager to config your phones? If so, the basefile edit is an option there. If not, then you have to make it by hand and put it in the
/tftpbootdirectory yourself.For the record I almost always do the config files by hand because once you learn it, it only takes minutes to replicate for bunches of extensions.
If there was anything at all that I wish had better documentation or example files for it would be this. And I would agree that hard setting everything would seem to be easier once you have it figure out.
I tried to build a file using the Yealink tool but it didnt work out. Again this weekend would be my first true effort.
Is it such that you create a file for each mac address, and there are files that would mass-apply to a model. For example could I put the line mentioned in FreePBX forums to fix "ghost return calls" in that file alone and see that setting applied to all yealink phones?
I imagine if I use EPM it will create said files and from there I could draw my conclusions and get the needed example files.
-
@bigbear said in Setup inbound call routing with FreePBX 13:
@JaredBusch said in Setup inbound call routing with FreePBX 13:
@bigbear said in Setup inbound call routing with FreePBX 13:
@JaredBusch over on FreePBX forums you references a cfg file to edit, I am about to load up FPBX 14 and was curious where that file is. TFTBOOT directory somewhere?
The only way to get the Yealink T5 android apps installed is apparently to add the pkg path to a provisioning file. This weekend I am determined to figure out how to hard provision with FreePBX.
Are you using the FreePBX Endpoint Manager to config your phones? If so, the basefile edit is an option there. If not, then you have to make it by hand and put it in the
/tftpbootdirectory yourself.For the record I almost always do the config files by hand because once you learn it, it only takes minutes to replicate for bunches of extensions.
If there was anything at all that I wish had better documentation or example files for it would be this. And I would agree that hard setting everything would seem to be easier once you have it figure out.
I tried to build a file using the Yealink tool but it didnt work out. Again this weekend would be my first true effort.
Is it such that you create a file for each mac address, and there are files that would mass-apply to a model. For example could I put the line mentioned in FreePBX forums to fix "ghost return calls" in that file alone and see that setting applied to all yealink phones?
I imagine if I use EPM it will create said files and from there I could draw my conclusions and get the needed example files.
i can upload one later tonight or tomorrow.
-
@bigbear said in Setup inbound call routing with FreePBX 13:
@EddieJennings said in Setup inbound call routing with FreePBX 13:
From what you said it looks like there are other PBX systems where that intelligence isn't built in, I would have to write specific routes for how to handle those calls.
Hmmm, I may not have explained that well. On an asterisk level you have dial plans. This can even be alphanumeric. You can create an extension or even a name like EDDIE and tell the call where to go.
In FreePBX (which is a system controlling Asterisk) you have an Extensions application and Outbound Routes which are manipulating your dial plans in asterisk.
What other routes are you looking to configure?
I'm not looking to configure anything wacky. I was curious as to how the PBX knows that a SIP invite that's sent to XXX@pbx is to go to a particular extension, rather than be compared against the dialling patterns for outbound routes.
-
@EddieJennings said in Setup inbound call routing with FreePBX 13:
@bigbear said in Setup inbound call routing with FreePBX 13:
@EddieJennings said in Setup inbound call routing with FreePBX 13:
From what you said it looks like there are other PBX systems where that intelligence isn't built in, I would have to write specific routes for how to handle those calls.
Hmmm, I may not have explained that well. On an asterisk level you have dial plans. This can even be alphanumeric. You can create an extension or even a name like EDDIE and tell the call where to go.
In FreePBX (which is a system controlling Asterisk) you have an Extensions application and Outbound Routes which are manipulating your dial plans in asterisk.
What other routes are you looking to configure?
I'm not looking to configure anything wacky. I was curious as to how the PBX knows that a SIP invite that's sent to XXX@pbx is to go to a particular extension, rather than be compared against the dialling patterns for outbound routes.
You were answered. It is in extensions.conf.
This is super under the hood Asterisk knowledge. This has nothing to do with FreePBX. Pick your fight here.
-
@JaredBusch I see that now. I'm not making plans to make any kind of changes with Asterisk's behavior. I was simply geeking out on the questions of why and how.
