Recently we deployed So8 with IPO 400 for an interesting application.
This is a multi-locational customer and use ERP and IT/IS systems on privately owned leased circuits network.
Backup is ISDN BRI lines.
If and when required, individual branches and depots come live on ISDN BRI remotely.
Multi-service router at head-end authenticates using incoming calls using CLI and other authentication mechanisms.
If authenticated, head-end router disconnects incoming. connection and initiates a callback to calling location and they are connected.
ISDN BRI at headend is terminated on router isdn interfaces or optionally ISDN interface cards on the servers.
IPO has 2 PRIs and spare capacity in usage.
We suggested,
1. New So8 module that we installed and configured a pool of MSNs which remote offices can dial into.
2. So8 ports are generated and shown as Lines under IPO Manager.
3. So we did normal short codes and programming of Incoming Call Routes.
4. So8 ports are connected to router ISDN interfaces (NT not required).
5. All other WAN configuration remains the same except that remote offices dial into a different no. - our given MSN rather than provider's no.
pluses (+) of above,
1. customer would be able to return all ISDN BRIs so there is very good saving on call costs as well as for fixed charges for those many lines.
2. reduces total no. of possible points of failure.
3. IT team is happy bcoz WAN side reconfiguiration was minimal.
4. Saves rack space and less equipments clutter.
minuses (-),
1. But for any reason if IPO needs to be power cycled then it hurts connectivity. i suppose thats a major factor...and not wanting to across many more..!
This is a multi-locational customer and use ERP and IT/IS systems on privately owned leased circuits network.
Backup is ISDN BRI lines.
If and when required, individual branches and depots come live on ISDN BRI remotely.
Multi-service router at head-end authenticates using incoming calls using CLI and other authentication mechanisms.
If authenticated, head-end router disconnects incoming. connection and initiates a callback to calling location and they are connected.
ISDN BRI at headend is terminated on router isdn interfaces or optionally ISDN interface cards on the servers.
IPO has 2 PRIs and spare capacity in usage.
We suggested,
1. New So8 module that we installed and configured a pool of MSNs which remote offices can dial into.
2. So8 ports are generated and shown as Lines under IPO Manager.
3. So we did normal short codes and programming of Incoming Call Routes.
4. So8 ports are connected to router ISDN interfaces (NT not required).
5. All other WAN configuration remains the same except that remote offices dial into a different no. - our given MSN rather than provider's no.
pluses (+) of above,
1. customer would be able to return all ISDN BRIs so there is very good saving on call costs as well as for fixed charges for those many lines.
2. reduces total no. of possible points of failure.
3. IT team is happy bcoz WAN side reconfiguiration was minimal.
4. Saves rack space and less equipments clutter.
minuses (-),
1. But for any reason if IPO needs to be power cycled then it hurts connectivity. i suppose thats a major factor...and not wanting to across many more..!