Did an upgrade last night - even though github has 1.9.7 as the last update, I am now on 1.9.9. Didn't poke around yet but see things like Dynamic routing and ai agent. I assume that you are just running behind in updating github and docs and that I didn't accidentally end up on a version that is not meant to be out yet?
New features I see :-)
- Thread starter Voipy
- Start date
rather than this one. But thank you - will try that!You guys have clearly not been sitting still. Will upgrade to 2.0 today.
I also see the comments on the version upgrades not but I am lost on Dynamic routing. Dynamic routing as I know it, routes inbound calls based on the caller ID of the caller - if no match, it takes the normal route. That, from the explanation does not seem to be what it means here but I don't quite get what it does. If it is based on the original dialled number, so the DID, how is it different from just normal call routing? I am clearly missing something?
I also see the comments on the version upgrades not but I am lost on Dynamic routing. Dynamic routing as I know it, routes inbound calls based on the caller ID of the caller - if no match, it takes the normal route. That, from the explanation does not seem to be what it means here but I don't quite get what it does. If it is based on the original dialled number, so the DID, how is it different from just normal call routing? I am clearly missing something?
Here is a possible use case and how it works. You have 50 DIDs for a client. All of them need to check business hours first and then route to their own destination.
Old configuration (without dynamic routes module):
You will have to create 50 Business hours sets and adjust the individual route inside each set. Then point those 50 DIDs to individual Business hours.
Problem: now you need to change the business hours for the entire company or add a holiday override. You have to do it 50 times.
New configuration with dynamic routes:
Create one business hours set and point it to dynamic routes. Point all of your DIDs to it. Done. If you only need to make any holiday or hours changes, you only need to do it once.
Once business hours are verified, the dynamic routes determine the routing for each DID, based on the initial number dialed.
DID1 -> Ring group A
DID2 -> Ring Group B
DID3 -> Ext 100
...
DID50 -> IVR 500
This feature is designed specifically for migrating from FreePBX or PBXact to FS PBX. Since their old PBX included this feature, its absence makes client migrations challenging. We've seen a surge in interest from FreePBX users in FS PBX, especially as Sangoma's recent actions have not been well received by the community.
Old configuration (without dynamic routes module):
You will have to create 50 Business hours sets and adjust the individual route inside each set. Then point those 50 DIDs to individual Business hours.
Problem: now you need to change the business hours for the entire company or add a holiday override. You have to do it 50 times.
New configuration with dynamic routes:
Create one business hours set and point it to dynamic routes. Point all of your DIDs to it. Done. If you only need to make any holiday or hours changes, you only need to do it once.
Once business hours are verified, the dynamic routes determine the routing for each DID, based on the initial number dialed.
DID1 -> Ring group A
DID2 -> Ring Group B
DID3 -> Ext 100
...
DID50 -> IVR 500
This feature is designed specifically for migrating from FreePBX or PBXact to FS PBX. Since their old PBX included this feature, its absence makes client migrations challenging. We've seen a surge in interest from FreePBX users in FS PBX, especially as Sangoma's recent actions have not been well received by the community.
