Example dial-peer for a trunk with TLS and SRTP:
dial-peer voice 100 voip
description Five9 VCC Atlanta Data Center SBC
translation-profile incoming FIVE9-INCOMING
translation-profile outgoing FIVE9-OUTGOING
media monitoring
no modem passthrough
session protocol sipv2
session target ipv4:[REDACTED]:5061
session transport tcp tls
destination e164-pattern-map 100
incoming uri via 100
voice-class sip early-offer forced
voice-class sip options-keepalive profile 100
voice-class sip bind control source-interface GigabitEthernet0/0/?
voice-class sip bind media source-interface GigabitEthernet0/0/?
dtmf-relay rtp-nte
srtp
codec g711ulaw bytes 160 fixed-bytes
fax rate disable
ip qos dscp cs3 signaling
no vad
Two things to be aware of:
- ANI and DNIS formatting will depend how the customer’s VCC tenant was built: NANP or E.164. You will likely need voice translations to align with what they expect. They do not support internal PBX extensions either; everything must be formatted as a real TN. Their typical approach is to prefix nines to pad extensions it out, despite the possibility that could someday be a real phone number. For example, a four digit internal extensions on the PBX would be dialed as 999999XXXX from VCC if the tenant was built for NANP.
- They expect G.711 u-law with a fixed 20ms sample size ONLY. You will have audio quality problems if using another sample size (learned that the hard way)! Ensure CUBE has transcoding/transrating resources in place if anything in the customer’s environment, including upstream ITSP, does not support that SDP.
