IPitomy SIP Trunk Configuration - Revision history

Tyler: /* Billing Portal */

2023-06-20T18:37:33Z

Billing Portal

Mike Lunn at 15:20, 3 July 2019

2019-07-03T15:20:33Z

Mike Lunn at 15:14, 3 July 2019

2019-07-03T15:14:38Z

Mike Lunn at 15:12, 3 July 2019

2019-07-03T15:12:24Z

Mike Lunn at 15:11, 3 July 2019

2019-07-03T15:11:43Z

Mike Lunn at 14:26, 3 July 2019

2019-07-03T14:26:25Z

Mike Lunn: /* E911 */

2019-07-03T14:16:04Z

E911

Mike Lunn: /* Digium Gateway G100/G200/G400/G800 (IPitomy SIP Trunks to PRI) */

2018-02-08T21:53:30Z

Digium Gateway G100/G200/G400/G800 (IPitomy SIP Trunks to PRI)

Mike Lunn: /* Important Notes */

2016-05-18T13:54:11Z

Important Notes

Mike Lunn at 13:51, 18 May 2016

2016-05-18T13:51:16Z

← Older revision		Revision as of 18:37, 20 June 2023
Line 2:		Line 2:


−	~~== Billing Portal ==~~

−	When you you applied for your account, you provided an email address for invoicing and billing. When you first get your IPitomy Billing Account activated, an email is generated to your billing email that provides a link to set your password. once you enter in a password, your account is active and accessible from [https://portal-ipitomy.smartbilling.ca https://portal-ipitomy.smartbilling.ca]	+	E911
−
−	~~See the following guide for information on how to use the billing portal:~~
−
−	~~[[File:Billing portal guideUpdated.pdf\|File:Billing portal guideUpdated.pdf]]~~
−
−	~~== Testing International<br/> ==~~
−
−	~~If you have Intl Rate Plan 1 you can call Mexico, Canada, and Puerto Rico. Here is a number to a hotel in Mexico to test: 011 52 664 633 3900~~
−
−	If you have Intl Rate Plan 2, you have access to many more countries, including Australia. (See your order form for a complete list). The following is a number to the automated date/time service in Australia you can use to test: 011-613-966-94916
−
−
−
−	== E911 ==

	By default, when you get an IPitomy SIP Trunk it supports one CID and one Address. To ensure that E911 is getting the correct CID, make sure the SIP Provider has the correct Outbound CID set, and ensure that under your Emergency and Emergency Test routes (Call Routing=>Outgoing) have Disable EXT CID set to Yes. If you need to have more than one CID and Address due to multiple locations, you'll need to specify this when you are ordering the trunks.		By default, when you get an IPitomy SIP Trunk it supports one CID and one Address. To ensure that E911 is getting the correct CID, make sure the SIP Provider has the correct Outbound CID set, and ensure that under your Emergency and Emergency Test routes (Call Routing=>Outgoing) have Disable EXT CID set to Yes. If you need to have more than one CID and Address due to multiple locations, you'll need to specify this when you are ordering the trunks.

← Older revision		Revision as of 15:20, 3 July 2019
Line 29:		Line 29:

	<span style="font-size:medium;">It is of ''vital'' importance that you successfully test and verify the E911 service. Successful testing is <u>required</u> to begin the porting process.</span>		<span style="font-size:medium;">It is of ''vital'' importance that you successfully test and verify the E911 service. Successful testing is <u>required</u> to begin the porting process.</span>
		+
		+	<span style="font-size:medium;"><span style="font-size:small;">Here are screen shots of both the Emergency 911 route and the Emergency Test 933 route. Please note that if there are phones at multiple physical locations, that </span></span><span style="font-size: small;">you would need to create additional Emergency routes for each location that requires E911 service.  A Class of Service can be created and assigned to specific extensions to </span>segregate each location.

	[[File:E911 routes.jpg]]		[[File:E911 routes.jpg]]

@@ Line 28: / Line 28: @@
 <font size="4">'''<u>TESTING WITH 933</u>'''</font>
-<span style="font-size:medium;">It is of vital importance that you successfully test and verify the E911 service, and is <u>required</u> to begin the porting process.</span>
+<span style="font-size:medium;">It is of ''vital'' importance that you successfully test and verify the E911 service. Successful testing is <u>required</u> to begin the porting process.</span>
 [[File:E911 routes.jpg]]

@@ Line 28: / Line 28: @@
 <font size="4">'''<u>TESTING WITH 933</u>'''</font>
-It is of vital importance that you successfully test and verify the E911 service, and is <u>required</u> to begin the porting process.
+<span style="font-size:medium;">It is of vital importance that you successfully test and verify the E911 service, and is <u>required</u> to begin the porting process.</span>
 [[File:E911 routes.jpg]]

← Older revision		Revision as of 15:11, 3 July 2019
Line 29:		Line 29:

	It is of vital importance that you successfully test and verify the E911 service, and is <u>required</u> to begin the porting process.		It is of vital importance that you successfully test and verify the E911 service, and is <u>required</u> to begin the porting process.
		+
		+	[[File:E911 routes.jpg]]

	== Migration ==		== Migration ==

← Older revision		Revision as of 14:26, 3 July 2019
Line 27:		Line 27:

	<font size="4">'''<u>TESTING WITH 933</u>'''</font>		<font size="4">'''<u>TESTING WITH 933</u>'''</font>
		+
		+	It is of vital importance that you successfully test and verify the E911 service, and is <u>required</u> to begin the porting process.

	== Migration ==		== Migration ==

← Older revision		Revision as of 14:16, 3 July 2019
Line 23:		Line 23:

	[[File:EmergencyCIDOverrideDisabled.jpg\|File:EmergencyCIDOverrideDisabled.jpg]]		[[File:EmergencyCIDOverrideDisabled.jpg\|File:EmergencyCIDOverrideDisabled.jpg]]
		+
		+
		+
		+	<font size="4">'''<u>TESTING WITH 933</u>'''</font>

	== Migration ==		== Migration ==

← Older revision		Revision as of 21:53, 8 February 2018
Line 151:		Line 151:

	[[File:Digium g100 4.PNG\|File:Digium g100 4.PNG]]		[[File:Digium g100 4.PNG\|File:Digium g100 4.PNG]]
		+	NOTE: Under Advanced Signalling, ensure "Enable Caller ID" is set to YES, or caller ID will not be passed properly.

@@ Line 37: / Line 37: @@
 *When naming the SIP trunk, do not use any spaces, hyphens, underscores, or special characters.
-*When configuring the SIP ACL to allow IPitomy trunks to communicate to the PBX be sure to add the following: 8.38.53.40/30 so it includes 8.38.53.41 and 8.38.53.42 (for our Legacy server); also add in 52.5.220.123/32 and 54.200.236.200/32 (for our new regional redundant server, East and West respectively).
+*When configuring the SIP ACL to allow IPitomy trunks to communicate to the PBX be sure to add the following: 52.5.220.123/32 and 54.200.236.200/32 for our regional redundant servers, East and West respectively.
 *Moving forward, we will be building accounts only on the new regional redundant servers. Whether using IP Bound or Registration method, you'll need to add TWO SIP Providers, one for east and one for west. If using Registration method, you'll use the same Username and Password, but will need to change the HOST field in the registration string to reflect the correct server (sip-e1.ipitomy.com for East, sip-w1.ipitomy.com for West).
@@ Line 44: / Line 44: @@
 *When building Providers in the PBX for our SIP Trunks, we have one for East and one for West.  Your DIDs should only be entered under one, and we recommend for that to be East since its the primary.  If a call happens to come inbound over West, they will route to the correct location that is programmed for that DID under East, because in the background there is only one big table of DIDs.
 == IP Bound Method ==

@@ Line 1: / Line 1: @@
 __TOC__
@@ Line 41: / Line 29: @@
 [[File:IPitomy SIP Trunk Migration.doc|File:IPitomy SIP Trunk Migration.doc]]
 == IP Bound Method ==