I am having a very wierd issue configuring intercoms on a new installation. We use extensions in the 100 range, so I create an intercom as *100, *101,*101 and so on. I have done this many times before and it works like a charm. The issue that I am having is when I hit *1, I get a secondary dial tone. If I create an intercom that is *200. It works fine. The funny thing is that if I dial *1, then *100 the intercom works fine. I have searched the configuration for a dial peer that might be overlapping but I cannot find one. Thank you for your assistance in this matter.
You can use the following sql command to find out which DN / pattern starting with *1 has secondary dial tone checked - I am not sure how the outsidedialtone field is represented (as true or 1), so one of the following two commands should result in a valid output :
run sql select pkid, dnorpattern from numplan where ((dnorpattern like '*1%') and (outsidedialtone='1'))
run sql select pkid, dnorpattern from numplan where ((dnorpattern like '*1%') and (outsidedialtone='t'))
If using Windows version :
Remote Desktop to Pub > Start > Programs > Microsoft SQL > SQL Query Analyzer > select latest CCM<> database on the top >
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...
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 discusses the bas...