Application Server configuration in CUCM

Answered Question
Dec 31st, 2009

Hi,

Could any one tell me the exact usage of Application Server configuration window in CUCM?

I recently integrated CUPS 7.0 and CUCM 7.0,

Adding CUPS server under application server in CUCM was one of the important steps.

After integration, i was able to register my CUPC and tested presence,IM and IPPM features. I then went to CUCM and removed the CUPS IP from the application server window and restarted both the servers. After reboot, I was able to use all the features on CUPC with out any issues and my CUPS server was able to reach CUCM and was in sync. I was not able to notice any difference in the CUPS behavior.

Thanks

Aravind

I have this problem too.
0 votes
Correct Answer by htluo about 6 years 11 months ago

This applies to *any* server in the cluster.  *any* means CUCM, CUPS, Unity Connection, etc.

The confusing part is: not *all* traffic relies on this.  ie. some traffic will work without this and some traffic will not.

To make things simpler, you should consider this as mandatory.

Michael

Correct Answer by htluo about 6 years 11 months ago

"won't accept any kind of communication from an unknown IP" is a little bit exaggerated.

CUCM will accept quite a lot traffic from "unknow IP", such as https, ssh, etc.

The entry in "server" and "application server" is used for IPSEC control.  Without it, IPSec communication between nodes won't established.  The most obvious symptom is "Change Notification" didn't take effect (push update).  However, pull update will still succeed.

For example, when you change the DN on CUCM, it won't populate to CUPS automatically.  But if you restart SyncAgent on CUPS, it'll pull the update over.

Michael

http://htluo.blogspot.com

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (3 ratings)
Loading.
htluo Thu, 12/31/2009 - 09:46

The "Server" and "Application Server" menu on CUCM is a kind of security measure to control which server can join the CUCM cluster (and share information).

Generally speaking, if you want to add a new server to an existing cluster, you should add the server to "Server" (if it's CUCM) or "Application Server" (if it's other server, such as Unity Connection, CUPS, etc.).

However, people keep forgetting this and open tickets with Cisco.  Thus some product team decide to make this process more intuitive.  For example, CUPS 7.x does not require you to add the server to "Application Server" menu (manually).  Instead, when you first logon to CUPS Admin page, it'll ask you for AXL credential (which is an application user on CUCM).  With the AXL credential, CUPS will have the power to add an entry to CUCM "Application Server" menu.

Michael

http://htluo.blogspot.com

Jaime Valencia Thu, 12/31/2009 - 12:16

Since CUCM is secured it won't accept any kind of communication from an unknown IP, until you configure the application servers it won't accept any connection from those server.

Similar to H323 GW config, if CUCM does not recognize the source IP it won't accept any H225/H245 negotiation.

HTH

java

If this helps, please rate

www.cisco.com/go/pdihelpdesk

Correct Answer
htluo Thu, 12/31/2009 - 12:23

"won't accept any kind of communication from an unknown IP" is a little bit exaggerated.

CUCM will accept quite a lot traffic from "unknow IP", such as https, ssh, etc.

The entry in "server" and "application server" is used for IPSEC control.  Without it, IPSec communication between nodes won't established.  The most obvious symptom is "Change Notification" didn't take effect (push update).  However, pull update will still succeed.

For example, when you change the DN on CUCM, it won't populate to CUPS automatically.  But if you restart SyncAgent on CUPS, it'll pull the update over.

Michael

http://htluo.blogspot.com

aravindhanelango Sun, 01/03/2010 - 21:38

Hi,

Does this apply to Presence traffic between CUCM and CUPS server aswell or it is restricted only to the database sync?

Thanks

Aravind

Correct Answer
htluo Sun, 01/03/2010 - 21:42

This applies to *any* server in the cluster.  *any* means CUCM, CUPS, Unity Connection, etc.

The confusing part is: not *all* traffic relies on this.  ie. some traffic will work without this and some traffic will not.

To make things simpler, you should consider this as mandatory.

Michael

Actions

This Discussion