Hi, I appreciate there are several discussion along this line already, however I have a H323 configured gateway on a CUCM for PSTN access, with an FXS Card used by Fax Machines which is controlled by MGCP.
Reading the exiting posts I believe they describe fallback for when the PSTN access is also MGCP, I hope the below will explain my problem.
Below is an extract of the config at present.
application global service alternate Default ! ccm-manager fallback-mgcp ccm-manager redundant-host 10.79.0.11 ccm-manager mgcp no ccm-manager fax protocol cisco ccm-manager music-on-hold ccm-manager config server 10.79.16.18 10.79.16.10 ccm-manager config ! mgcp mgcp call-agent 10.79.16.11 2427 service-type mgcp version 0.1 mgcp modem passthrough voip mode nse mgcp package-capability rtp-package mgcp package-capability sst-package mgcp package-capability pre-package mgcp default-package mt-package no mgcp timer receive-rtcp mgcp sdp simple mgcp fax t38 inhibit ! mgcp profile default ! dial-peer voice 999010 pots service mgcpapp port 0/1/0 ! dial-peer voice 999011 pots service mgcpapp port 0/1/1 ! dial-peer voice 1 pots description *** DEFAULT INCOMING - PSTN *** incoming called-number . direct-inward-dial port 0/0/0:15 ! dial-peer voice 2 voip description *** DEFAULT INCOMING - VOIP *** voice-class codec 1 voice-class h323 1 incoming called-number . ! dial-peer voice 10 pots destination-pattern 9T progress_ind setup enable 3 progress_ind alert enable 8 progress_ind progress enable 8 progress_ind connect enable 8 direct-inward-dial port 0/0/0:15 ! dial-peer voice 100 voip description *** CUCM - PRIMARY *** preference 1 destination-pattern 513.... voice-class codec 1 voice-class h323 1 session target ipv4:10.79.0.11 dtmf-relay h245-alphanumeric fax rate disable ip qos dscp cs5 media no vad ! dial-peer voice 101 voip description *** CUCM - SECONDARY *** preference 2 destination-pattern 513.... voice-class codec 1 voice-class h323 1 session target ipv4:10.79.16.11 dtmf-relay h245-alphanumeric fax rate disable ip qos dscp cs5 media no vad !
To enable the FXS (extension 513100) to recieve calls in SRST I believe I need a new dial-peer along the lines of:
dial-peer voice 201 pots description *** FXS 0/1/0 for SRST *** incoming called-number 513100 port 0/1/0
However, if I add this configuration all inbound calls to 513100 even when not in SRST will match dial-peer 201 rather than 100 or 101, will I need to configure 3 new dial-peers? 1st pref IP of CUCM Primary, 2nd pref IP of CUCM Secondary and 3rd pref Port 0/1/0, this will then route the call to the CUCM Subscribers under normal operation but send straight to the FXS port when in SRST?
Thanks for confirming my thoughts, I have configured with the additional dial-peers but have also found I an alternative would have been to make use of the "dial-peer hunt" command which could change the hunting order of dial-peers to give the preference command the prioirty rather than the longest match. Then give the pots DP for the FXS port a preference of 3 and keep the existing generic CUCM dial-peers.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...