[cisco-voip] CUCM Trunk timer

[Anthony Holloway]

Which is fine for things like CUBE and CUC, but for SME to Leaf Clusters,
one might use multiple destinations per trunk, to limit the numbers of
trunks you need to create/manage.

E.g., SME is only really needed when you have more than 3 clusters being
tied together, so let's a assume 4 clusters of 8 subs each.  The difference
would be 4 SIP trunks or 32 SIP trunks.

On Wed, Dec 6, 2017 at 1:25 AM Erick Bergquist <erickbee at gmail.com> wrote:

> It’s 0 days and the same hours and minutes right?
>
> It’s been like that for awhile as far as I recall next to the trunk
> destination. Likely a cosmetic item.
>
> I usually have only one destination per trunk and use route groups to
> order how they are used.
>
> Erick
>
>
> On Tue, Dec 5, 2017 at 12:56 PM Jason Aarons (Americas) <
> jason.aarons at dimensiondata.com> wrote:
>
>>
>>
>> On a CUCM trunk, you have the status showing the duration it’s been in
>> service, then under SIP information there is another timer for the
>> individual links.
>>
>>
>>
>> CUCM is showing a difference in the timers.  Do you know why that is?
>>
>>
>>
>>
>>
>>
>>
>> Jason Aarons, CCIEx2 No. 38564
>>
>> Advanced Technology Consultant
>>
>> Dimension Data
>>
>> 904-338-3245 <(904)%20338-3245>
>>
>>
>>
>>
>> This email and all contents are subject to the following disclaimer:
>> "http://www.dimensiondata.com/emaildisclaimer"
>> <http://www.dimensiondata.com/Global/Policies/Pages/Email-Disclaimer.aspx>
>> _______________________________________________
>> 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/20171206/4bbe4975/attachment.html>