/mcp!
If an administrator does not want CUCM to configure the gateway, simply remove the ccm-manager commands. The dial-peer configuration is included to drive home the point about how the concept works. With ccm-manager configurations present, CUCM creates these dial-peers based on the port configuration in CUCM so there is no need to actually define the dial-peer. The CUCM created dial-peers usually start with 999 and are then three more digits. SIP DSAPP with Dial-Peers SIP DSAPP was added in Cisco IOS XE 16.12.1+ and CUCM 12.5.1SU+ With this feature, analog voice ports such as FXS can be registered and managed by CUCM. Call routing with DSAPP is slightly different than MGCP or SCCP as the dial-peers are still matched normally. That is, the gateway can collect digits from the FXS port and do a dial-peer lookup on the VOIP dial-peers. After a match is found, the INVITE is sent to CUCM enblock for CUCM to perform further digit analysis. Sample SIP DSAPP Configuration [with CUCM Auto-Configuration*] | Cisco IOS-XE 16.12.1+ and CUCM 12.5.1SU+
! dsapp line ! voice service voip sip bind control source-interface GigabitEthernet0/0/0 bind media source-interface GigabitEthernet0/0/0 session transport tcp ! application service dsapp param dialpeer 777 ! global service default dsapp ! ccm-manager config server 10.10.10.10 ccm-manager sipana auto-config local GigabitEthernet0/0/0 ! dial-peer voice 777 voip destination-pattern 9T session protocol sipv2 session target ipv4:10.10.10.10 session transport tcp incoming called-number . voice-class sip extension gw-ana voice-class sip bind control source-interface GigabitEthernet0/0/0 dtmf-relay rtp-nte codec g711ulaw ! dial-peer voice 19990100 pots service dsapp destination-pattern 7776 voice-class sip extension gw-ana port 0/1/0 !