[cisco-voip] Weird trunk issue

Erick Wellnitz ewellnitzvoip at gmail.com
Wed Nov 28 11:52:46 EST 2012


I got this one resolved but not with the MTP.  I used intercluster trunk
only going to one CM on each side.  Works great now.

I have another issue I'm working involving a SIP integration with
Connection.

On Wed, Nov 28, 2012 at 10:49 AM, Erick Wellnitz <ewellnitzvoip at gmail.com>wrote:

> Really weird but I unchecked the "Media Termination Point Required" box
> and now it works.  Is this going to get me into trouble down the road?
>
> On Wed, Nov 28, 2012 at 10:41 AM, abbas Wali <abbaseo at gmail.com> wrote:
>
>> I had some issues when i created my first SIP trunk between CUCM 8.5 and
>> CUCM 6. after some testing I found out that
>>
>> the Route list for that particular Route pattern must be registered with
>> the CM who is participating in the SIP signalling for the trunk on the
>> remote CM.
>>
>>
>> hope that helps.
>>
>>
>> On 28 November 2012 02:06, Erick Wellnitz <ewellnitzvoip at gmail.com>wrote:
>>
>>> Reading the SRND for both 6 and 8 I think I misconfigured the
>>> intercluster trunk.  I'm going to simplify my configuration and use a
>>> single CUCM on each side to begin with.  It is a temporary setup so I'm not
>>> concerned with redundancy.
>>>
>>>
>>>
>>> On Tuesday, November 27, 2012, Peter Slow wrote:
>>>
>>>> the thing that's happening to you is not a reliability problem, calls
>>>> aren't ever supposed to drop - they drop when they're really "dropping"
>>>> because of network outages, usually.
>>>>
>>>> what devices are you calling from and to? where are THEY? (physically
>>>> and logically)
>>>>
>>>> Pick one call flow, the simplest one you can that still exhibits your
>>>> problem, then troubleshoot that specifically. (and tell us what it is
>>>> please =)
>>>>
>>>> Until _both_ of your sides are on 7-or-8-dot-somethign my personal
>>>> recommendation is to use h.323.
>>>>
>>>> let us know what you decide to do, and more about the call flow
>>>> (devices on either side, proximity of the CUCMs to each other and # of CMs
>>>> in the cluster etc). It's difficult to provide more than smart-assery
>>>> without those things ;)
>>>>
>>>> -Peter
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Tue, Nov 27, 2012 at 8:46 PM, Erick Wellnitz <
>>>> ewellnitzvoip at gmail.com> wrote:
>>>>
>>>>> No firewall.  I wish it was that simple.
>>>>>
>>>>>
>>>>> On Tuesday, November 27, 2012, Peter Slow wrote:
>>>>>
>>>>>> remove the firewall that's in between your two clusters?
>>>>>>
>>>>>> On Tue, Nov 27, 2012 at 8:16 PM, Erick <ewellnitzvoip at gmail.com>wrote:
>>>>>>
>>>>>>> I'm migrating sites from a 6.1 cucm cluster to an 8.6 cluster.
>>>>>>>
>>>>>>> I have set up both SIP and an intercluster trunk with similar
>>>>>>> results.  After a random period of time you get a fast busy calling between
>>>>>>> the clusters.
>>>>>>>
>>>>>>> Anyone have any tips for settinv this up to be reliable?
>>>>>>>
>>>>>>> Thanks!
>>>>>>> _______________________________________________
>>>>>>> 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
>>>
>>>
>>
>>
>> --
>> @bbas..
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20121128/3064aefe/attachment.html>


More information about the cisco-voip mailing list