Howto talk:Not maintaining bindings for domain: Difference between revisions
Jump to navigation
Jump to search
(New page: This page only describes the problem, but the "howto" in the name is misunderstanding....there's no solution explained for getting things done. How can we create a bind for the domain (ex...) |
mNo edit summary |
||
| Line 5: | Line 5: | ||
Have you got to initiate a VPN connection to use only internal IP addresses or can you also put the public ip address of the PBX in a list (like ip routes or gatekeeper ID alias) that the PBX assumes to be in local network? | Have you got to initiate a VPN connection to use only internal IP addresses or can you also put the public ip address of the PBX in a list (like ip routes or gatekeeper ID alias) that the PBX assumes to be in local network? | ||
Thanks | Thanks | ||
''Howto:'' is just a '''Namespace''' within our Wiki, and does not belong to the Article Name ''Not maintaining bindings for domain'' in fact. | |||
The solution for your problem would be: | |||
#use DNS name instead of the IP address | |||
#confiugre this name ''as System Name'' in the PBX configuration | |||
Revision as of 16:36, 30 January 2012
This page only describes the problem, but the "howto" in the name is misunderstanding....there's no solution explained for getting things done.
How can we create a bind for the domain (external address of the PBX) in order to get external phones (softphone, sipphones, ip phones) rightly connect to the PBX?
Have you got to initiate a VPN connection to use only internal IP addresses or can you also put the public ip address of the PBX in a list (like ip routes or gatekeeper ID alias) that the PBX assumes to be in local network? Thanks
Howto: is just a Namespace within our Wiki, and does not belong to the Article Name Not maintaining bindings for domain in fact.
The solution for your problem would be:
- use DNS name instead of the IP address
- confiugre this name as System Name in the PBX configuration