With the Encore release of CCM, you are now able to register with one remote gatekeeper for call routing. This seems to work fine, but I have noticed infrequently that the registration times out and no subsequent RRQ messages are sent over. At this time, the easy fix is just to go into CCM And reset the gk ( even though it really doesnt reset it, it just forces another RRQ). This does not scale in the practical world and I was wondering if anyone else has seen something like this before ( a possible workaround). I have played with the TTL etc but I was not sucessful.
Unfortunatley, this is not the case all the other endpoints remain registered with the Gatekeeper, just the CCM drops out. I have been meaning to open a case and will probably get to it soon, main problem is that this is a random problem, which means I can not get the exact log file that it occurs in etc.
It would be nice if the Cisco Gatekeepers has the ability to send a trap when a location times out of RRQ for does not re-register.
I had this issue with nine remote CM's homing to the gatekeeper at the host site via a Frame Relay WAN. They CM's (3.07) were losing connections to the GK (12.1T) periodically. I investigated and found that the Ethernet ports on all the Frame Relay router(s) were 10Mb but set to Full Duplex! The stats on the interface (all sites) had several thousand CRC's per one milliion packets. I had the customer clean each network and verify that all ports were set to auto negotiation. After this was done, the GK has not dropped since!
Another incident that this occured with one CM to a GK via a WAN and found that the cable from the WAN router was generating CRC's, replaced the cable and no more GK drops.
In both cases, nothing was wrong with the CallManager's or the Gatekeeper. It was all at Layer1!
As mentioned previously in my previous article and following the same idea of certificate pinning in Cisco Meeting Server, to demonstrate this concept added since version 3.0. I used two different CA to sign :1-The WebBridge certificate with CA's certific...
Certificate pinning is introduced on cisco meeting server starting in CMS 3.0 to help prevent man in the middle attack.But what is the Certificate Pinning?Traditionally, SSL Handshake consists on the validation of the server's certificate, let's say colla...
In a Clustering over the WAN deployment, securing the ICCS (Intra-Cluster Communication Signaling) traversing the WAN can be a requirement. The IPSEC VPN Policy between nodes can be configured to secure the ICCS Traffic.To quickly verify that the IPSEC is...
Attracted by the concept of dial plan and the passion of writing, I launched a challenge to write a workbook with practical scenarios covering in details this concept, the result is a workbook with 30 practice labs treating many components such route patt...