Frequently Asked Questions - Revision history

Mdomer: /* Frequently Asked Questions (FAQ) */

2025-09-22T15:37:17Z

Frequently Asked Questions (FAQ)

Mike Lunn: Mike Lunn moved page Frequently asked questions to Frequently Asked Questions: Naming convention on page

2021-12-07T19:03:25Z

Mike Lunn moved page Frequently asked questions to Frequently Asked Questions: Naming convention on page

Mike Lunn at 18:47, 7 December 2021

2021-12-07T18:47:58Z

Mike Lunn at 18:21, 7 December 2021

2021-12-07T18:21:39Z

Mike Lunn at 17:28, 7 December 2021

2021-12-07T17:28:40Z

Mike Lunn at 17:22, 7 December 2021

2021-12-07T17:22:54Z

Mike Lunn at 17:16, 7 December 2021

2021-12-07T17:16:16Z

Mike Lunn at 16:54, 7 December 2021

2021-12-07T16:54:40Z

Mike Lunn: Created page with "== Frequently Asked Questions (FAQ) == This page aims to cover general frequently asked questions along with linking the answer to the relevant page on the topic. === How do..."

2021-12-07T16:20:12Z

Created page with "== Frequently Asked Questions (FAQ) == This page aims to cover general frequently asked questions along with linking the answer to the relevant page on the topic. === How do..."

New page

== Frequently Asked Questions (FAQ) ==
This page aims to cover general frequently asked questions along with linking the answer to the relevant page on the topic.

=== How do I provision a phone? ===

=== Why does my phone not register? ===

=== Why will Queue Manager not connect? ===

← Older revision		Revision as of 15:37, 22 September 2025
Line 22:		Line 22:
	=== What is a branch office? ===		=== What is a branch office? ===
	A branch office is a connection between two pbxs, that can be physical premise systems, cloud hosted systems, or a combination of both, that allows the pbxs to operate in tandem with each other. Extensions on one system can directly call extensions and destinations on another system over the branch office connection, calls can be transferred, and even routed across the branch. Branch office connections use the IAX2 protocol to establish two-way communication between the systems involved. This runs over port 4569, so port forwarding needs to be done on any router that's in front of a premise pbx attempting to use branch offices. A further expanded guide on branch offices can be found at [[IP_PBX_Manual_Branch_Offices\|Branch Offices]] and at [[Training:_Branch_Offices\|Branch Office Training]]		A branch office is a connection between two pbxs, that can be physical premise systems, cloud hosted systems, or a combination of both, that allows the pbxs to operate in tandem with each other. Extensions on one system can directly call extensions and destinations on another system over the branch office connection, calls can be transferred, and even routed across the branch. Branch office connections use the IAX2 protocol to establish two-way communication between the systems involved. This runs over port 4569, so port forwarding needs to be done on any router that's in front of a premise pbx attempting to use branch offices. A further expanded guide on branch offices can be found at [[IP_PBX_Manual_Branch_Offices\|Branch Offices]] and at [[Training:_Branch_Offices\|Branch Office Training]]
		+
		+	=== What IP addresses does IPitomy SIP service use? ===
		+	IPitomy SIP service has two signaling servers, SIP East and SIP West, as well as two media servers. In the near future we will be retiring our current media servers for two new media servers on the latest software.
		+
		+	====== These are the IP addresses associated with our SIP service and the ports you will need to forward: ======
		+	SIP East: 52.5.220.123 (5060 UDP)
		+
		+	SIP West: 54.200.2336.200 (5060 UDP)
		+
		+	Old Media East: 52.202.13.217 (10000-20000 UDP)
		+
		+	Old Media West: 44.236.207.157 (10000-20000 UDP)
		+
		+	New Media East: 54.80.52.224 (10000-20000 UDP)
		+
		+	New Media West: 54.187.72.69 (10000-20000 UDP)
		+
		+	When configuring port forwarding in your firewall you will need to configure port forwarding to allow traffic from our two SIP IP addresses on port 5060 UDP. With the IPitomy PBX you will also need to configure port forwarding to allow traffic from all of our media server IP addresses to ports 10000-20000 UDP. For 3rd party PBXs you will need to consult the administration manual to find out what RTP ports your specific PBX uses and forward those ports.
		+
		+	It's best to leave the RTP ports (10000-20000 UDP) open to all IPs. Since these are not signaling ports it's not possible to generate calls on these ports so they are not vulnerable to fraud. If they are open to all IP addresses then you will never need to update the IP addresses when new media servers are created or media IP addresses change.

← Older revision		Revision as of 18:47, 7 December 2021
Line 19:		Line 19:
	Both protocols are used for the autoprovisioning process by phones. HTTP is generally recommended (and required on cloud) for REMOTE phone autoprovisioning, while TFTP is ONLY recommended for either local phone provisioning, or if remote, you use an access control list with it, because TFTP has no inherent security or authentication. Both protocols are used by the phone to send a request to the pbx for its configuration files. HTTP will work over default port 80, or if you've remapped an external port, such as 8080, it will work over that as well, but needs to be specified. You can put it into the URL like this: http://example.com:8080/ippbx/phonecfg		Both protocols are used for the autoprovisioning process by phones. HTTP is generally recommended (and required on cloud) for REMOTE phone autoprovisioning, while TFTP is ONLY recommended for either local phone provisioning, or if remote, you use an access control list with it, because TFTP has no inherent security or authentication. Both protocols are used by the phone to send a request to the pbx for its configuration files. HTTP will work over default port 80, or if you've remapped an external port, such as 8080, it will work over that as well, but needs to be specified. You can put it into the URL like this: http://example.com:8080/ippbx/phonecfg
	TFTP runs over port 69, and you ONLY use the base address (ip address or domain name). You do not add the /ippbx/phonecfg when using TFTP.		TFTP runs over port 69, and you ONLY use the base address (ip address or domain name). You do not add the /ippbx/phonecfg when using TFTP.
		+
		+	=== What is a branch office? ===
		+	A branch office is a connection between two pbxs, that can be physical premise systems, cloud hosted systems, or a combination of both, that allows the pbxs to operate in tandem with each other. Extensions on one system can directly call extensions and destinations on another system over the branch office connection, calls can be transferred, and even routed across the branch. Branch office connections use the IAX2 protocol to establish two-way communication between the systems involved. This runs over port 4569, so port forwarding needs to be done on any router that's in front of a premise pbx attempting to use branch offices. A further expanded guide on branch offices can be found at [[IP_PBX_Manual_Branch_Offices\|Branch Offices]] and at [[Training:_Branch_Offices\|Branch Office Training]]

← Older revision		Revision as of 18:21, 7 December 2021
Line 15:		Line 15:
	=== Why will Queue Manager not connect? ===		=== Why will Queue Manager not connect? ===
	The primary cause for a single queue manager client to fail to connect to the pbx is the computer's time setting. The PC running queue manager must have the exact same time as the pbx or else the authentication will be rejected. The PBX time can be found on pbx setup->general, and has a spot to configure a network time server for synchronizing. In windows, it is advised to set the exact same network time server so that it is always in sync with the pbx. We recommend pool.ntp.org as the server to be used, but you may use another of your preference. See [[Q_Manager]] for our main page on this application.		The primary cause for a single queue manager client to fail to connect to the pbx is the computer's time setting. The PC running queue manager must have the exact same time as the pbx or else the authentication will be rejected. The PBX time can be found on pbx setup->general, and has a spot to configure a network time server for synchronizing. In windows, it is advised to set the exact same network time server so that it is always in sync with the pbx. We recommend pool.ntp.org as the server to be used, but you may use another of your preference. See [[Q_Manager]] for our main page on this application.
		+
		+	=== What is the difference between HTTP and TFTP? ===
		+	Both protocols are used for the autoprovisioning process by phones. HTTP is generally recommended (and required on cloud) for REMOTE phone autoprovisioning, while TFTP is ONLY recommended for either local phone provisioning, or if remote, you use an access control list with it, because TFTP has no inherent security or authentication. Both protocols are used by the phone to send a request to the pbx for its configuration files. HTTP will work over default port 80, or if you've remapped an external port, such as 8080, it will work over that as well, but needs to be specified. You can put it into the URL like this: http://example.com:8080/ippbx/phonecfg
		+	TFTP runs over port 69, and you ONLY use the base address (ip address or domain name). You do not add the /ippbx/phonecfg when using TFTP.

@@ Line 11: / Line 11: @@
 === Why does my phone not register? ===
-If the phone is local, first check to see that the extension actually exists, by looking at Reports->Monitoring, and looking for the extension in this list.  If you've created the extension, saved it, applied changes, and it is NOT in this list, chances are you lack a license for that extension type.  If it does appear in the monitoring list, the phone is failing to authenticate to the pbx for some reason.  If it's a local phone, either the phone is not provisioned properly, or it is unable to talk to the pbx.  If it's remote, in addition to the same problems the local phone has, you also need to ensure port 5060 is forwarded to the pbx through the router, and that if the pbx has a SIP Access Control List, that it allows the IP address where the remote phone is located.
+If the phone is local, first check to see that the extension actually exists, by looking at Reports->Monitoring, and looking for the extension in this list.  If you've created the extension, saved it, applied changes, and it is NOT in this list, chances are you lack a license for that extension type.  If it does appear in the monitoring list, the phone is failing to authenticate to the pbx for some reason.  If it's a local phone, either the phone is not provisioned properly, or it is unable to talk to the pbx.  If it's remote, in addition to the same problems the local phone has, you also need to ensure port 5060 is forwarded to the pbx through the router, and that if the pbx has a SIP Access Control List, that it allows the IP address where the remote phone is located.  [[Troubleshooting_Remote_SIP]] contains a lot of useful information to help with troubleshooting remote phones.
 === Why will Queue Manager not connect? ===
-The primary cause for a single queue manager client to fail to connect to the pbx is the computer's time setting.  The PC running queue manager must have the exact same time as the pbx or else the authentication will be rejected.  The PBX time can be found on pbx setup->general, and has a spot to configure a network time server for synchronizing.  In windows, it is advised to set the exact same network time server so that it is always in sync with the pbx.  We recommend pool.ntp.org as the server to be used, but you may use another of your preference.
+The primary cause for a single queue manager client to fail to connect to the pbx is the computer's time setting.  The PC running queue manager must have the exact same time as the pbx or else the authentication will be rejected.  The PBX time can be found on pbx setup->general, and has a spot to configure a network time server for synchronizing.  In windows, it is advised to set the exact same network time server so that it is always in sync with the pbx.  We recommend pool.ntp.org as the server to be used, but you may use another of your preference. See [[Q_Manager]] for our main page on this application.

@@ Line 4: / Line 4: @@
 === How do I provision a phone? ===
 This is going to depend on the phone and where the phone is in relation to the pbx (local or remote).
-For an IPitomy branded phone, [[http://wiki.ipitomy.com/wiki/HD_Phones#Phone_Configuration Configuring an IPitomy Phone]], if the phone is local, follow the autoprovisioning steps.  If it is remote, follow the remote phones steps.  Both are on the linked page.
+For an IPitomy branded phone, [[HD_Phones#Phone_Configuration|Configuring an IPitomy Phone]], if the phone is local, follow the autoprovisioning steps.  If it is remote, follow the remote phones steps.  Both are on the linked page.
 === Why does my phone not register? ===

← Older revision	Revision as of 19:03, 7 December 2021
(No difference)