Support / Voice / SIP Trunking / IP termination using an account prefix
IP termination using an account prefix.
VoiceTel supports IP-authenticated outbound SIP termination using an account-prefix dialing format. The account username is placed in the dialed destination, and VoiceTel uses the prefix to associate the call with the correct account and approved IP address list.
Network endpoints
Use one of the following VoiceTel termination endpoints:
geo.voicetel.com
bgp.voicetel.comTest the endpoint that works best for the PBX, SBC, firewall, and network path in use.
Dialing format
Use the following format for outbound calls:
ACCOUNT_NUMBER#10_DIGIT_DESTINATION_NUMBER@geo.voicetel.comThe account number identifies the VoiceTel account. The 10-digit destination number identifies the number being called.
Example
To call VoiceTel support at (917) 580-3000 from account number 1234567890, send the call as:
1234567890#9175803000@geo.voicetel.comHow the prefix is used
VoiceTel uses the account prefix to identify the correct account and apply the proper IP-authenticated outbound calling behavior.
The PBX, SBC, or application must format the outbound destination correctly. If the prefix is missing or malformed, VoiceTel may not be able to associate the outbound call with the correct account.
Add approved IP addresses
To use IP authentication, add the customer source IP addresses to the approved IP address list.
- Log in to the VoiceTel portal.
- Go to Settings.
- Open Authentication.
- Click + IP.
- Add the public source IP address that VoiceTel will see when the PBX, SBC, or firewall sends SIP traffic.
- Save the change.
- Select the authentication type that matches the customer configuration.
Authentication type
Available authentication types:
| Authentication type | Behavior |
|---|---|
| Digest | Allows outbound calls using SIP Digest authentication. |
| Lax (Digest | IP) | Allows traffic that matches either valid Digest authentication or the approved source IP address list. |
| IP | Allows traffic only when the source IP address matches the approved IP address list. |
| Strict (Digest + IP) | Requires both valid Digest authentication and a matching approved source IP address. |
The customer selects the authentication type that matches their PBX, SBC, firewall, and network configuration. See Authentication types and DID routing for how authentication interacts with inbound DID delivery.
Changing authentication type can affect inbound DID behavior. Digest-based routing and IP-authenticated routing are configured differently. Confirm DID routing after changing authentication type, approved IP addresses, or outbound call formatting.