Hi, we’ve reached the limit of SIP URIs on our 8510 and I noticed the below in the admin guide, has anyone achieved this prefix based routing method and does it retain the presence of the MCU conferences?
Btw, in earlier versions the MCU/VCS supported more (at least h323 registered conferences).
We use authentication and these many registrations crashed the VCS. Maybe thats one of
the reasons why it is now limited.
>>-MCU still have 100 H323 and 50 SIP registration. This limit was set in earlier version as well.
always thought of adding an extra sip domain for the MCU, and use either the API of the VCS
or the MCU to get the concurrent calls out and then map these to an extra presence handler.
But hope dies last that this will be fixed in general and it was not critical for us.
>> Presence works on base of SUBSRCIBE- NOTIFY. When an UA(user agent) registers to REGISTRAR (VCS in this case), after that it sends SUBSCRIBE to subscribe for event 'presence'. Whenever the Status of the UA changes, it send PUBLISH to VCS, and VCS will send NOTIFY all the other UA's whose has subscribe to Presence event.
So without Registration,MCU will act as Gateway. Presence will not work for this scenario.
like you have the prefix 80 and the conference number 50 you would dial 8050 you will always
and up in a h323 call and the mcu registers the number 50, it would be much better if it could
register on sip 8050.
>> Lets say that you created a conference with Numeric ID 50 and MCU service prefix is 80. Now you have registered as both H323 and SIP. In this case you dont need 80. You can directly dial with H323 id 50 or SIP URI firstname.lastname@example.org
Now lets says that you have conference created but not registered, in that case for H323 you can dial 80(prefix) followed by conference ID. But in case of SIP what you can do is create a rule as follow
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.