Re: SIP/2.0 503 Service Unavailable - In incoming calls when usi
I solved the problem.
This is the summary of what I have found:
- The site1-GW1 = site1-trunk1 has associated a Device Pool(DP) which has associated a CCM Group called 'Default'. This CCM group consists of CCM1 and CCM2, which are the CCMs in site1, it has not associated any CCM of site2.
In our tests when a call incoming through site1-GW1 that negociates SIP against CCM3 and CCM4 receives error 503 and isn't established. These gateways don't belong to the CCM-group used by the trunk.
We changed this, we included CCM3 in the CCM-Group and we forced the GW to negociate SIP with CCM1, CCM2 and CCM3 ( a CCM-Group can contain up to 3 CCMs).
And it works. No error 503 now.
- The site2-GW1 = site2-trunk1 has associated a Device Pool(DP) which has a CCM Group called 'CCM-G3'. This CCM group consists of CCM3, CCM4 and CCM2, which are the CCMs in site1 and in site2.
In our tests when a call incoming through site2-GW1 that negociates SIP against CCM1 receives error 503 and isn't established. This gateway doesn't belong to the CCM-group used by the trunk.
Now we have changed this and the gateways negociates SIP against CCM2 and it works.
When a device registers, it attempts to connect to the primary (first) Cisco Unified Communications Manager in the group that is assigned to its device pool. If the primary Cisco Unified Communications Manager is not available, the device tries to connect to the next Cisco Unified Communications Manager that is listed in the group, and so on.
I asked TAC about the sense of the CCM group for a SIP trunk, since they don't register themselves. This was the answer:
For INCOMING calls, the CCM group in the sip trunks to determin through which cucm Server the call will be routed/proccessed first (determining the cucm servers priority to proccess the call)
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.