We have a problem with a Fallback on BCM50 (R2 and R3).
Well, i'm not sure that be a problem, or a "philosophy of design".
I have a BCM50 with 2 Voip trunks, and a "BRI MBM". The routing and scheduling is configured correctly.
I have 1 emergency extention (emergency DN), and that should be the only one that can be use the Fallback (BRI MBM). The other extensions (normal DN) shouldn't use the BRI module (in theory).
If i have the 2 IP-trunks busy, and a normal extension (normal DN) tries to realize a call, it receive a message "No free lines". That's correct, and is that we are looking for.
If the "emergency DN" tries the same (with the 2 IP-trunks busy), the call will be realized through the BRI MBM. That is correct.
But if the IP-trunks are "down" (the cable LAN is out for example) the normal extention can realized call normally through the BRI MBM. That is a problem, the "normal DN" shouldn't use the Fallback, only the "emergency DN".
Somebody has an idea to restrict the second scenario?
Thanks in advance.
Well, i'm not sure that be a problem, or a "philosophy of design".
I have a BCM50 with 2 Voip trunks, and a "BRI MBM". The routing and scheduling is configured correctly.
I have 1 emergency extention (emergency DN), and that should be the only one that can be use the Fallback (BRI MBM). The other extensions (normal DN) shouldn't use the BRI module (in theory).
If i have the 2 IP-trunks busy, and a normal extension (normal DN) tries to realize a call, it receive a message "No free lines". That's correct, and is that we are looking for.
If the "emergency DN" tries the same (with the 2 IP-trunks busy), the call will be realized through the BRI MBM. That is correct.
But if the IP-trunks are "down" (the cable LAN is out for example) the normal extention can realized call normally through the BRI MBM. That is a problem, the "normal DN" shouldn't use the Fallback, only the "emergency DN".
Somebody has an idea to restrict the second scenario?
Thanks in advance.