Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here




When using AADS I have the setting to configure the SIP_CONTROLLER_LIST with the list I want the client to use. This is marked in the global setting of AADS.

When going to https://servername.domain.com/acs/resources/config... the controller list appears to be what PPM is sending out. The output from the url is
SET SIP_CONTROLLER_LIST ";transport=TLS,;transport=TCP,;transport=UDP,;transport=TLS,;transport=TCP,;transport=UDP"

The problem - When my client registers it picks the first 2 listed, which is really the same SM, just using different ports. I have defined in AADS:

This way the client registers to each SM.

I guess I have two questions - is there a way to force what I put in AADS to override PPM?
I have tried adding the Setting - ENABLE_PPM_SOURCED_SIPPROXYSRVR with a value of 0 in AADS with no luck.
Or how do I fix PPM to only offer the 2 options?

Thanks in advance.


So this took an Avaya case and a really long time to figure out. It turns out that AADS cannot set the SIP CONTROLLER LIST, as it will get overwrote with values from SM. The process is the following to clear up the SIP CONTROLLER List.
In SMGR, drill to routing then entities.
Find SM
Click on SM and make sure the end point at the bottom of the page is checked for what protocols you want to offer.
Do this on both SMs
The controller list will match after replication.

Things to check -
Make sure both SMs are in a DataCenter
Also make sure 1 SM is tied to AADS.

We noticed if we changed the secondary SM (one tied to AADS) its settings did not get replicated. it wasn't till we made a change on the Primary SM that the settings were replicated. Avaya said this is functioning as designed, but I don't see how... O well. In the end, my problem is solved. Onto the next challenge.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close