Showing posts from April, 2015

4 Ways to Protect CUCM Meetme Conferences with PIN


RSVP Basics

In IP Telephony World, RSVP is a CAC mechanism that can reserve bandwidth for the length of the call. If any router along the path cannot reserve the requested bandwidth, the originating gateway, CUBE, or CallManager can reroute the call, send it with different marking, or drop it.
One drawback to RSVP is that the reservation process causes some delay in call setup. To minimize this, include RSVP control messages LLQ.
RSVP Signaling
Its Network control protocol (protocol number 0x2e and operates at L3) that allows internet applications to reserve QoS resources for their traffic. Note that RSVP will do the signaling for reservation but the actual reservation should be done by queuing mechanisms.
RSVP messages 1. Path Message It’s sent by the sender through the path provided by routing protocol towards the receiver. It will store flow info in each node and enables each node to realize the previous and next hop of the session. Those messages are sent periodically. They are used to form RSV…

Remarking Calls over Two CoS MPLS WAN

I had a scenario where the client bought two CoS L3 MPLS links for all his offices (HQs & BRs). 20% CoS1 is used for voice calls while 80% CoS3 for data.
As you know, MPLS providers will drop excess packets on CoS1. The excess packets from CoS1 won't be remarked. For other CoSes excess packets are remarked to default CoS.
Initially, we deployed E-LCAC for his network to make sure that once CoS1 is full calls are blocked. The client decided not to go for AAR.
The demand for On-Net calls increased and the users started getting "Not Enough Bandwidth" message very frequent.
Increasing E-LCAC location bandwidth wasn't an option as this will degrade overall calls performance due to packets getting dropped at CoS1 (remember excess packets at CoS1 are dropped).
The client didn't want to invest on upgrading CoS1 and wanted to pass excess calls over CoS3.
- Network devices won't be able to do this as they mark packets not calls. This means that packets …

LDAP Users Import Failed with Custom User Fields

When configuring "Custom User Fields To Be Synchronized", every time you add anything to the section at : System > LDAP > LDAP Directory > Custom User Fields To Be Synchronized, the synchronization process fails.
Checking CUCM traces for DirSync and found this exception:
2014-06-06 15:50:52,830 ERROR [DirSync-DBInterface] common.DSDBInterface ( - DSDBInterface.executeSQL Calling rollbackTransaction 2014-06-06 15:50:52,831 ERROR [DirSync-DBInterface] common.DSDBInterface ( - DSDBInterface.executeSQL Caught SQLException, Error code=-217 2014-06-06 15:50:52,831 ERROR [DirSync-DBInterface] common.DSDBInterface ( - DSDBInterface.updateUserInfo Error code=-217 2014-06-06 15:50:52,831 ERROR [DirSync-DBInterface] common.DSDBInterface ( - DSDBInterface.updateUserInfo java.sql.SQLException: Column (customfield1) not found in any table in the query (or SLV is undefined). MESSAGE Column…