! To identify the inbound dial-peer - dtmf-relay rtp-nte dial-peer voice 2001 voip preference 1 destination-pattern [2-9] . . [2-9] session protocol sipv2 session target ipv4: <secondary CUCM IP Add> incoming called-number - 9T dtmf - relay rtp-nte We need to configure a few more dial-peers SO that the branch can work during the Survivable Remote Site Telephony (SRST) fallback mode. It is important to match the des- tination patterns defined here to the dial-peers configured for sending the call to the SP. Example 12-14 shows the configured dial-peers that will be used during the SRST fall- back mode. Example 12-14 Configuring SRST Mode dial-peer voice 200 pots incoming called-number direct-inward-dial port 0/2/0 dial-peer voice 91120 pots preference 1 destination-pattern 911 port 0/2/0 forward-digits all dial-peer voice 991120 pots preference 1 destination-pattern 9911 port 0/2/0 forward - digits 3 Chapter 12: Case Studies 295 dial-peer voice 100 pots description Local - 1FB preference 1 destination-pattern 9[2-9] port 0/2/0 forward-digits 7 dial-peer voice 101 pots description LD-1FB preference 1 destination-pattern 91 [2-9] port 0/2/0 forward-digits - 11 call-manager-fallback secondary-dialtone 9 max-conferences 16 gain -6 transfer-system full-consult timeouts interdigit 5 ip source-address 10.255.126.36 port 2000 max k-ephones 42 max-dn 144 dialplan-pattern 1 402715 extension-length - 4 ! Should represent the SP expected DIDs default-destination 59981 moh All_in_the_Mind.ULAW.wav multicast moh 239.1.1.1 port 16392 route 10.255.126.36 10.125.250.1 Summary In this chapter, we tried to provide a case study from a real-life deployment of a SIP trunk. We tried to capture as much information as possible without violating the confi- dentiality of the customers and their network. If you notice the problems and their solu- tions carefully, you should get an idea of the challenges and depth of the SIP trunk deployment. This page intentionally left blank Chapter 13 Future of Unified Communications This chapter covers th