- Joined
- Nov 14, 2013
- Messages
- 516
- Reaction score
- 346
Currently each phone must have the IP address of a chosen SBC manually entered. Please add a list of Session Border Controllers so that these systems can be manually entered (or even automatically populated when an SBC checks in). Ideally, the SBC would have an internal identifier and would pass the LAN IP to the PBX. This HOSTNAME of the SBC could be used.
It should also be included in email alerts when there is a registration change event.
This will have two benefits:
1 - Provisioning will be faster an less prone to mistakes
2 - An SBC IP address change only needs to be done once, and the affects all phones using that SBC.
3 - If the SBC Hostname can be used, and passed to the phones for provisioning, then an SBC IP address change is not an issue.
This will allow us to configure an SBC for DCHP and configure the extensions, ship to the client and when the SBC checks in we can manually update the SBC LAN IP in the PBX (if it does not auto populate or use the HOSTNAME) and then when the phones start RPS will pull the correct settings.
It should also be included in email alerts when there is a registration change event.
This will have two benefits:
1 - Provisioning will be faster an less prone to mistakes
2 - An SBC IP address change only needs to be done once, and the affects all phones using that SBC.
3 - If the SBC Hostname can be used, and passed to the phones for provisioning, then an SBC IP address change is not an issue.
This will allow us to configure an SBC for DCHP and configure the extensions, ship to the client and when the SBC checks in we can manually update the SBC LAN IP in the PBX (if it does not auto populate or use the HOSTNAME) and then when the phones start RPS will pull the correct settings.
Last edited:
Upvote
15