McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 43

↗ View in doc context
page
43
source
voice-quality/troubleshooting/cisco-ios-vs-iosxe/cisco-ios-vs-iosxe.md
chunk_id
voice-quality::troubleshooting::cisco-ios-vs-iosxe::cisco-ios-vs-iosxe::56

Order of Command Preference with Tenants Dial-peer command 1. Tenant command 2. Global command (voice service voip and sip-ua) 3. Multi-Tenant Configuration Example You have two tenants 777 and 999. You have configured them with slightly different configurations and applied them to the dial-peers. This means that calls using the different dial-peers have the dial-peer based configurations as well as the tenant specific configurations. The options listed are only a snippet of the power of voice class tenants. Refer to the documentation to see what can be configured on a tenant. It is recommend to employ strict matching mechanisms like voice class uri or tagging numbers with certain number strings to separate tenant dial-peer matching, or even configuring VRFs so that Tenant A never overlaps with Tenant B and accidentally matches a dial-peer they cannot.

! voice class tenant 999 asymmetric payload full bind control source-interface GigabitEthernet0/0/0.228 bind media source-interface GigabitEthernet0/0/0.228 g729 annexb-all ! voice class tenant 777 sip-server ipv4:192.168.1.2 bind control source-interface Loopback0 bind media source-interface Loopback0 pass-thru content sdp ! dial-peer voice 999 voip destination-pattern 8675309 session protocol sipv2 incoming called-number 8675309 voice-class sip tenant 999 ! dial-peer voice 777 voip destination-pattern 8675309 session protocol sipv2 session target sip-server voice-class sip tenant 777 !

Verification Currently, there are no individual commands to see voice class tenant configurations. This command can be sufficient for filtering the running config to just the tenant information.

show run | sec tenant