[cisco-voip] Intercluster Trunk H323 or SIP ?

[Justin Steinberg]

SIP is required if you want intercluster presence.  Although if you really
wanted to you could create a special CSS for Subscribe that used the SIP
trunks and actual calls/media could use h323.

On Mon, May 18, 2009 at 10:01 PM, Tanner Ezell <tanner.ezell at gmail.com>wrote:

> I've had the same experience, and feelings towards sip. H323 > SIP (imo)
>
>
> On Mon, May 18, 2009 at 6:57 PM, Jason Burns <burns.jason at gmail.com>wrote:
>
>> I'd stick with H.323 between CCM clusters over SIP. I find it easier to
>> troubleshoot and understand (but that's just personal preference I suppose),
>> and everything usually "just works" with the H.323 setup.
>>
>> - Jason
>>
>>
>> On Fri, May 15, 2009 at 10:32 AM, Matthew Linsemier <
>> mlinsemier at apassurance.com> wrote:
>>
>>>  If you use Unity you may want to verify that features such as MWI and
>>> voice profiles work across the a SIP link.  There was a reason we went with
>>> H.323 during our CCM 4 to UCM 7 migration, and I think this was one of them.
>>>
>>> Matt
>>>
>>>
>>>
>>> On 5/15/09 3:13 AM, "Nick" <csvoip at googlemail.com> wrote:
>>>
>>> Hi All
>>>
>>> I'm looking setting up an ICT to another CUCM cluster, just wondering if
>>> using SIP instead of H323 is now a better option?
>>>
>>> Any thoughts on this?
>>>
>>>
>>>
>>> ------------------------------
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>  ------------------------------
>>>
>>> CONFIDENTIALITY STATEMENT
>>> This communication and any attachments are CONFIDENTIAL and may be
>>> protected by one or more legal privileges. It is intended solely for the use
>>> of the addressee identified above. If you are not the intended recipient,
>>> any use, disclosure, copying or distribution of this communication is
>>> UNAUTHORIZED. Neither this information block, the typed name of the sender,
>>> nor anything else in this message is intended to constitute an electronic
>>> signature unless a specific statement to the contrary is included in this
>>> message. If you have received this communication in error, please
>>> immediately contact me and delete this communication from your computer.
>>> Thank you.
>>>
>>> ------------------------------
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090518/408f499a/attachment.html>