SIP Overview
Choose the SIP registration, inbound access, and outbound routing capabilities needed to connect GetVoiceBot with your telephony system.
GetVoiceBot supports SIP registration and direct inbound and outbound SIP calling. These capabilities solve
different parts of the call path and can be used separately or together.
Choose the required capability
| Capability | Use it when |
|---|---|
| SIP registration | A GetVoiceBot agent should register to your PBX or SIP service like a VoIP endpoint. |
| Inbound SIP access | Your approved carrier, PBX, or proxy will send SIP calls directly to GetVoiceBot. |
| Outbound SIP routing | GetVoiceBot should send matching outbound calls to your SIP domain, IP, or proxy. |
Registration is often the simplest PBX integration, but it does not replace inbound source controls
or direct outbound routes when your topology requires those capabilities.
Plan the call path
Before configuring anything, record:
- the Agent that should receive or originate the call
- SIP domain or IP and required port
- UDP or TCP transport
- any outbound proxy
- source IP addresses that may send inbound calls
- the caller identity format expected by each system
- transfer and extension behavior
Use E.164 phone numbers for public caller identity unless your approved SIP design explicitly uses a
different internal destination format.
Configure and test
- Configure the required registration, inbound access, or outbound route.
- Re-read the complete saved resource.
- Place a representative inbound call.
- Place an authorized outbound call.
- Test transfer behavior when used.
- Inspect GetVoiceBot logs and your telephony provider's SIP evidence.
Preserve unrelated inbound sources and outbound routes when making a change. Removing a registration,
source address, or route can interrupt production calling.
Continue with SIP registration, SIP to your Agent, or
SIP from your Agent.