[cisco-voip] SIP trunk CUCM 7

[Wes Sisk]

CM supports a native SIP trunk. However, that trunk does not offer any 
means of providing authentication to the provider. That and the need to 
focus all ip traffic through a single address (Border Element) are 
reasons most people put a CUBE between CM and the SIP provider.

/wes

On Monday, December 01, 2008 5:30:59 PM, Dane Newman 
<dane.newman at gmail.com> wrote:
> Please correct me if I am wrong but I thought cucm had the ability to 
> support sip trunks native in 7?
>
> Sent from my iPhone
>
> On Dec 1, 2008, at 2:44 PM, "Mark Holloway" <mh at markholloway.com 
> <mailto:mh at markholloway.com>> wrote:
>
>> I haven’t had a chance to explore CUCM 7 yet, but I think you will 
>> need a back to back user agent like CUBE or Ingate’s SIPerator.
>>
>>  
>>
>> *From:* cisco-voip-bounces at puck.nether.net 
>> <mailto:cisco-voip-bounces at puck.nether.net> 
>> [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf Of *Dane Newman
>> *Sent:* Monday, December 01, 2008 10:58 AM
>> *To:* cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
>> *Subject:* [cisco-voip] SIP trunk CUCM 7
>>
>>  
>>
>> I just purchased a sip trunk from ipcomms.net <http://ipcomms.net> 
>> does anyone have instructions how to configure it to work with CUCM 7?
>>
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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/20081201/998d55f2/attachment.html>