[cisco-voip] SIP trunk vs. SCCP ports for CUCM v7 and UCxN v7 integration

[Jason Aarons (US)]

I’d like to know what the “known SIP issues” are ?  In general I still stick with SCCP out of habit but I’d like to have known what was on his/her mind.

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Sandy Lee
Sent: Wednesday, December 01, 2010 10:53 AM
To: Lelio Fulgenzi; voyp list
Subject: Re: [cisco-voip] SIP trunk vs. SCCP ports for CUCM v7 and UCxN v7 integration

Hi Lelio,

When I migrated from 4.1(3) to 7.1(3), I tried the SIP trunk, because I tought it would be simplier. I ran into a few issues and after discussing with my SE, he recommended the SCCP approach, as there are known issues with the SIP one. Nice to know “before”. Maybe it was because I also had another SIP trunk to my legacy PBX through TIMG. Will never know, but SCCP works fine for me.

Sandy.

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
Sent: Tuesday, November 30, 2010 4:36 PM
To: voyp list
Subject: [cisco-voip] SIP trunk vs. SCCP ports for CUCM v7 and UCxN v7 integration

I'm working on the migration from CUCM v4.1(3) to v7.1(x).

I think it would be much simpler if I am able to create a SIP trunk from CallManager v7 to Connection.

Has anyone seen any huge differences between an SCCP and a SIP integration? Do things generally continue to work the same?



---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
                              - LFJ (with apologies to Mr. Popeil)

-----------------------------------------
Disclaimer:

This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only.  If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful.  If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20101201/8a39d15f/attachment.html>