we have 3 CCM 4.13sr2, Publisher and subscriber located at main building, another subscriber located at branch1. DS3 between buildings. All T1 PRI and FXO are configured as MGCP.
The phone load for 7940/7060: P00307020300 For 7970: TERM70.7-0-2SR1S
main (Pub, sub with 3 T1 PRI Trunk) <--> branch1 (sub with 8FXO for 911 and backup purpose) <--> branch2 (2 T1 PRI Trunk)
We had T1 PRI at branch1 before, but move to branch2 last Friday for saving money purpose. An the mean time, the old T1 PRI at branch2 also move to the new trunk group (new T1 PRI jack). Cut the the long story short, both T1 PRI are lcoated at Branch2, but they are plug into new T1 PRI jack.
Now, our main number at Branch1 get call through T1 PRI at Branch2, after transfer call, both parties get dead air (no audio).
Call comes in -->Branch2T1PRI --> Branch1(ext: 8000 rings)--> transfer to any extension (dead air).
I have to change to Region to G.711 between buildings, then the problem fixed, which will increase bandwidth useage.
If I call the main number at main building, I can transfer to anywhere.
I tested CCM last night for myself. I called the main number at branch1, which go to voice mail (unified messaging) after business hour, so I press my extension 6000, I got cut off. 9 of 10 are failed.
If I tested by calling main number at main building, I can transfer anywhere I want by pressing extension.
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...