SIP Trunking User Manual
Contents
- 1 Introduction
- 2 Connection to Phone Power
- 3 Technical Contacts
- 4 Product guidelines
- 5 Technical guidelines
- 6 Suggested interoperability testing
- 6.1 Outbound Calls
- 6.1.1 Test Case 1.1.1: Normal Call, Ring Back From PSTN End, With Answer, Hang-up from PSTN
- 6.1.2 Test Case 1.1.2: Normal Call, Ring Back From PSTN End, With Answer, Hang-up from Customer
- 6.1.3 Test Case 1.2.1: Ring No Answer, Hangup During Ring back, SIP Resp Cancel & SIP Resp 487
- 6.1.4 Test Case 1.2.2: Ring No Answer, Timeout
- 6.1.5 Test Case 1.2.3: User Busy, SIP Resp 486
- 6.1.6 Test Case 1.3.1: 1 Hour hold time & SIP Session Timers
- 6.1.7 Test Case 1.4.1: Single choice, g711 20ms
- 6.1.8 Test Case 1.4.2: InBand DTMF, g711 20ms
- 6.1.9 Test Case 1.4.3: DTMF RFC2833 named events, g711 20ms
- 6.1.10 Test Case 1.4.4: Fax InBand, g711 20ms
- 6.1.11 Test Case 1.4.5: Fax Re-Invite to T.38, g711 20ms
- 6.1.12 Test Case 1.4.6: Single choice, g729 20ms, DTMF RFC2833
- 6.1.13 Test Case 1.5.1: Normal Call with no FROM number
- 6.1.14 Test Case 1.5.2: Normal Call to toll free
- 6.1.15 Test Case 1.5.3: International Call (011 + CC + XXXXXXXXXX)
- 6.1.16 Test Case 1.5.4: Service Call (311)
- 6.1.17 Test Case 1.5.5: Emergency (911)
- 6.2 Inbound Calls
- 6.2.1 Test Case 2.1.1: Normal Call, Ring Back From Customer End, With Answer, Hang-up from PSTN
- 6.2.2 Test Case 2.1.2: Normal Call, Ring Back From Customer End, With Answer, Hang-up from Customer
- 6.2.3 Test Case 2.2.1: Ring No Answer, Hangup During Ring back, SIP Resp Cancel & SIP Resp 487
- 6.2.4 Test Case 2.2.2: Ring No Answer, Timeout
- 6.2.5 Test Case 2.2.3: User Busy, SIP Resp 486
- 6.2.6 Test Case 2.3.1: 1 Hour hold time & SIP Session Timers
- 6.2.7 Test Case 2.4.1: Single choice, g711 20ms
- 6.2.8 Test Case 2.4.2: InBand DTMF, g711 20ms
- 6.2.9 Test Case 2.4.3: DTMF RFC2833 named events, g711 20ms
- 6.2.10 Test Case 2.4.4: Fax InBand, g711 20ms
- 6.2.11 Test Case 2.4.5: Fax Re-Invite to T.38, g711 20ms
- 6.2.12 Test Case 2.5.1: Normal Call with no FROM number
- 6.2.13 Test Case 2.5.2: Call to Toll Free number
- 6.1 Outbound Calls
Introduction
Congratulations on your new Phone Power SIP trunk connection. This manual will cover the basic setup and call flows as well as provide some useful information on your connection going forward.
Connection to Phone Power
All SIP trunk connections to Phone Power are done over the public internet. Phone Power does not currently offer any dedicated circuit connections or BGP peering.
Connection Details
Peering IP |
208.64.8.13 |
Protocol |
SIP |
Port |
5060 |
Protocol |
UDP |
Codecs |
G711u, G729a |
FAX |
T.38, G711u pass through |
DTMF |
RFC2833, G711u in-band |
Technical Contacts
Technical Support hours :
6:00 am - 5:30 pm PST (Monday - Friday)
Emergency support 24/7
Email : [email protected]
Phone : (866) 431-1626
Live Chat via Phone Power
Product guidelines
A SIP trunk is a session between one or more SIP endpoints on your network and Phone Powers border elements. Trunks may be Termination only or Bi-directional (Origination and Termination).
Trunk ID
When the trunk is configured you will be assigned a trunk ID. The trunk ID must be a new 10 digit domestic phone number and can not be a number that was ported it. This 10 digit TN cannot be canceled as long as this trunk is active, and should be referenced whenever contacting support.
Lines
A SIP Trunk can have multiple public IP's associated with it. Each public IP address defined as eligible to send/receive traffic on this trunk will need to have port capacity associated to it. Calls will be sent to the first available IP that has not reached capacity, and will not roll over to subsequent IP's until all capacity has been used. Any IP defined as a member of the trunk is eligible to send an outbound call.
Ports
All SIP trunks are assigned a specific number of available ports. Every concurrent outgoing or incoming call will use one port. Most customers will have only one IP endpoint and all ports will be assigned to that endpoint, however it is possible to configure multiple endpoints and assign ports across them to facilitate load balancing and fail-over. Each product will include a specific number of ports, and additional ports can be provisioned at an additional charge.
DID's
All SIP trunks can have a virtually unlimited number of DID's associated with them. Calls to these DID's use ports but do not incur any additional charges. DID's are available anywhere within the Phone Power footprint and can be ported in from other carriers. DID's each have a monthly recurring charge associated with them to maintain the number. Each DID provisioned will come with the following:
• LIDB registration
• CNAM
• E911 Service
Toll Free
All SIP trunks can have a virtually unlimited number of toll free numbers associated with them. Calls to toll free numbers will use ports on your trunk as well as be billed at the rate defined in your service plan. Toll Free numbers each have a monthly recurring charge associated with them to maintain the number.
Origination
All calls originated via a SIP trunk will have:
• Calling Number (when not marked private)
• Calling Name (CNAM) when available
Termination
SIP trunks include a volume of minutes per month to be used for termination within the lower 48 states and Canada. All calls within this footprint are not charged up to the included minute amount.
• All minutes beyond this are charged at the blended domestic rate specified in the service plan.
• Calls to Alaska, Hawaii, Caribbean islands, and international destinations are billed at the current price indicated on our international rates page: http://www.phonepower.com/services/voip/international.aspx
• Directory assistance calls are billed at $0.99 per call and $0.10 per minute after 2 minutes if call completion is requested.
• Operator service calls are billed at $3.00 per call
All these rates are subject to change. Please refer to our terms of service page for details. http://www.phonepower.com/services/terms/voiptos.aspx
Technical guidelines
Below are the guidelines for what call flows are and are not supported with Phone Power SIP Trunking. Please review these completely.
Signaling requirements and behavior
In order to ensure complete interoperability and experience the best possible results with Phone Power SIP trunking please ensure the following behavior in your switch signaling:
- Invites are sent using 10D format as described below
- Domestic Calls: 1 + area code + number
- OR Domestic Calls: area code + number
- OR Domestic Calls: 7D number IF within the same area code as destination
- International Calls: 011 + country code + number
- Canada: 1 + area code + number
- Caribbean islands: 1 + area code + number
- 211 – Calls to 211 United Way / Human services are supported based on the calling number sent at no charge
- 311 – Non emergency city services are supported based on the calling number sent at no charge
- 411 – Information / Directory assistance calls are supported with an additional charge per call
- 511 – Traffic information calls are supported based on the calling number as no charge
- 611 – This will go to phone power support
- 711 – TTY service for the hearing impaired are supported at no charge
- 811 – Dig alert calls are supported based on the calling number sent at no charge
- 911 can be supported if inbound numbers are provisioned. If a 911 call is sent from a non-provisioned number it will be answered but a charge of $75 will be applied.
- All signaling traffic contains public IP's in all headers described below:
- From
- To
- Contact
- Topmost VIA
- SDP
- Privacy
- P-Asserted-Identitiy or Remote-party-ID are used to convey all privacy. It is recommended that a PAI header be inserted on all Invites but is not required.
- Calls sent with privacy MUST have a PAI header inserted.
- Inbound calls with privacy enabled will NOT have a PAI header describing the original caller
- Wholesale customers will receive PAI headers on inbound calls that have privacy enabled.
- Calls sent with an anonymous from header should include a valid RPID or PAI header describing the true calling party for services that do not respect anonymity. If this header is not included the Trunk ID will be used.
- Caller ID:
Valid options to set for the from number in traffic are:
- Any 10 digit number provisioned on your trunk.
- In conjunction with the "Truth in Caller ID Act of 2010" all calls sent with a caller ID other than one of the numbers on your trunk will have their caller ID changed to the trunk ID.
- Customers may set any CNAM value desired, however delivery is left to the discretion of the terminating telco, and as such is best effort.
- Wholesale customers may set any 10 digit North American number.
- SIP Options keep-alives:
- To ensure reliable service Phone Power will send SIP Options messages to all configured customer endpoints to determine their availability. Any 2xx or 4xx class response to these messages will confirm that your equipment is up and ready to take calls. Failure to respond to these keep-alives will result in that endpoint not being offered calls until a keep-alive is successfully responded to.
- Voice Codec
- Phone Power supports only G711 and G729
- Silence suppression is not supported
- DTMF
- Phone Power supports both DTMF via RFC 2833 and InBand. SIP INFO is not supported.
- Session Timers
- Phone Power will use a re-invite to detect orphaned calls every 15 minutes. If the re-invite is not responded we will assume the call leg is orphaned and tear it down.
- Phone Power supports a maximum call length of 4 hours.
- Bandwidth and connectivity
- The customer is responsible for managing their own bandwidth and connectivity.
- A typical G711uLaw call will consume 84kbps of bandwidth. Please provision ports appropriately
- Quality monitoring
- Phone Power provides RTP statistics in its CDR's between the customer endpoint and its border elements purely for customer diagnostic purposes.
Supported Call Flows
• Call established from Customer endpoint to PSTN
• Call established from PSTN to Customer endpoint
• Call established from PSTN to Customer endpoint, Customer endpoint plays ring back
• Call established from Customer endpoint to PSTN, Phone Power plays ring back
• RE-INVITE changing media preferences after call is established
• UPDATE changing media preferences during ring back but before 200OK
• Call established from Customer endpoint to PSTN with privacy
• Call established from PSTN to Customer endpoint with privacy
• SIP options health checks
Unsupported Call Flows
• Call transfer bridged in the phone power network
• Call hold via RFC 2543
Billing behavior
• Billing on all outgoing calls commences at the 200OK
• Billing on all Toll-free calls commences at the 200OK
• Phone Power is aware that some international destinations MAY send a 200ok while they are still playing ring-back. This call will be considered answered and billable.
• Once the customer has acknowledged their trunk is in production, they will be held responsible for all calls originating from their configured IP address.
Suggested interoperability testing
It is recommended that customers perform the following sample call flows to ensure complete functionality of their Phone Power SIP Trunk prior to going into production, since improper behavior in any of these flows may result in improper billing treatment or impaired service.
It is encouraged that customers perform packet captures from their IP PBX and submit them to their interop engineer at Phone Power to validate the correct behavior, however if this is not an option, customers can work with their interop engineers to lookup the call flows in our cache and validate the correct behavior for any of the tests they wish to perform.
Outbound Calls
Test Case 1.1.1: Normal Call, Ring Back From PSTN End, With Answer, Hang-up from PSTN
Test Case 1.1.2: Normal Call, Ring Back From PSTN End, With Answer, Hang-up from Customer
Test Case 1.2.1: Ring No Answer, Hangup During Ring back, SIP Resp Cancel & SIP Resp 487
Test Case 1.2.2: Ring No Answer, Timeout
Test Case 1.2.3: User Busy, SIP Resp 486
Test Case 1.3.1: 1 Hour hold time & SIP Session Timers
Test Case 1.4.1: Single choice, g711 20ms
Test Case 1.4.2: InBand DTMF, g711 20ms
Test Case 1.4.3: DTMF RFC2833 named events, g711 20ms
Test Case 1.4.4: Fax InBand, g711 20ms
Test Case 1.4.5: Fax Re-Invite to T.38, g711 20ms
Test Case 1.4.6: Single choice, g729 20ms, DTMF RFC2833
Test Case 1.5.1: Normal Call with no FROM number
Please ensure you set privacy using either a P-Asserted-Identitiy header or a Remote-Party-ID header to denote the actual calling party for billing and compliance purposes.
Test Case 1.5.2: Normal Call to toll free
Test Case 1.5.3: International Call (011 + CC + XXXXXXXXXX)
Hong Kong weather -011-852-187-8200 Speaking Clock (UK) – 011-44-871-789-3642
Test Case 1.5.4: Service Call (311)
Test Case 1.5.5: Emergency (911)
When placing this call indicate to the PSAP that you are placing a test call and ask to confirm the service address. This will NOT result in a 911 dispatch to your location. DO NOT HANG UP UNTIL YOU SPEAK WITH THE OPERATOR.
Inbound Calls
Test Case 2.1.1: Normal Call, Ring Back From Customer End, With Answer, Hang-up from PSTN
Test Case 2.1.2: Normal Call, Ring Back From Customer End, With Answer, Hang-up from Customer
Test Case 2.2.1: Ring No Answer, Hangup During Ring back, SIP Resp Cancel & SIP Resp 487
Test Case 2.2.2: Ring No Answer, Timeout
Test Case 2.2.3: User Busy, SIP Resp 486
Test Case 2.3.1: 1 Hour hold time & SIP Session Timers
Test Case 2.4.1: Single choice, g711 20ms
Test Case 2.4.2: InBand DTMF, g711 20ms
Test Case 2.4.3: DTMF RFC2833 named events, g711 20ms
Test Case 2.4.4: Fax InBand, g711 20ms
Test Case 2.4.5: Fax Re-Invite to T.38, g711 20ms
Test Case 2.5.1: Normal Call with no FROM number