SIP from Your Agent

Route approved outbound GetVoiceBot calls to a SIP domain, IP, or proxy.

Outbound SIP routes tell GetVoiceBot where matching calls should be sent. Review the complete route list
before changing it because overlapping destinations or route order can affect production delivery.

Route format

{domain-or-ip}:{port};transport={tcp-or-udp};proxyAddress={domain-or-ip}:{proxy-port}

• Domain or IP: Required destination used in the SIP request.
• Port: Optional signaling port; normally 5060 when omitted.
• Transport: Optional tcp or udp; normally udp when omitted.
• Proxy address: Optional network destination that receives the request on behalf of the SIP
  domain. It can include its own port.

Examples:

sip.example.com
sip.example.com:6000;transport=tcp
sip.example.com;proxyAddress=proxy.example.com
sip.example.com;transport=tcp;proxyAddress=proxy.example.com:6000

Add and verify a route

1. Read all current outbound routes.
2. Confirm the exact destination, port, transport, and proxy with the receiving provider.
3. Add the narrowest intended route without replacing unrelated entries.
4. Read the complete list again.
5. Place a representative outbound call.
6. Verify caller identity, destination, audio, and transfer behavior.
7. Inspect GetVoiceBot logs and the provider's SIP trace.

Removing a route can interrupt production calls. Confirm the replacement path and test the remaining
route set after deletion.

Manage routes with the generated operations to
list,
add, or
remove an outbound route.