- Joined
- Apr 19, 2010
- Messages
- 6
- Reaction score
- 0
I'm far for being a SIP expert, however, I can't find a functionallity that will add a lot of value and sense to 3CX.
We have a few remote locations, some overseas and local employee homes where we we want to deploy the 3102; not all have static ip internet connections. We need to dial out using the FXO port and to receive and place calls through the FXS port.
All the dual functions on the 3102, listed on 3CX as non supported, are working fine.
Thus far, setup the FXS port: OK (can place and receive local and PBX calls), router OK, local FXO port (ie use of <gw0>) OK, receive incomming PSTN calls, OK.
On the 3cx I can see the gateway registered, with a Virtual Extension Number, so the IP is known, however, the system requires a static IP in the configuration.
Is there any other method to connect to the FXO port without using the static IP? I the system can register a Virtual Extension for the FXO, why 3CX can't use the registration IP as the Gateway IP?
Thanks,
We have a few remote locations, some overseas and local employee homes where we we want to deploy the 3102; not all have static ip internet connections. We need to dial out using the FXO port and to receive and place calls through the FXS port.
All the dual functions on the 3102, listed on 3CX as non supported, are working fine.
Thus far, setup the FXS port: OK (can place and receive local and PBX calls), router OK, local FXO port (ie use of <gw0>) OK, receive incomming PSTN calls, OK.
On the 3cx I can see the gateway registered, with a Virtual Extension Number, so the IP is known, however, the system requires a static IP in the configuration.
Is there any other method to connect to the FXO port without using the static IP? I the system can register a Virtual Extension for the FXO, why 3CX can't use the registration IP as the Gateway IP?
Thanks,