[cisco-voip] SIP trunk CUCM 7

Mark Holloway mh at markholloway.com
Tue Dec 2 13:24:45 EST 2008


There are three ways a provider can potentially offer a SIP Trunk.

 

1)      The ITSP peers with your static public IP and they do not require any registration or authentication from you.  This is the most vulnerable for fraud unless they have some specific access control on a session border controller.

2)      The SIP Endpoint registers every 3600 seconds (60 seconds with NAT traversal) with a provider so the provider learns what IP to communicate with.  No authentication is required.  This is still vulnerable to fraud.

3)      The SIP Endpoint registers and authenticates (MD5-Hash) every 3600 seconds (60 seconds with NAT traversal).  This is the safest method.

 

Some providers are offering TLS but this is still relatively new to the ITSP industry to be mainstream.

 

 

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Wes Sisk
Sent: Tuesday, December 02, 2008 11:05 AM
To: Dane Newman
Cc: <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] SIP trunk CUCM 7

 

A list troll kindly clarified for me:
CM will do authentication on a SIP trunk if configured with the appropriate profile.  CM sends a message, receives a challange in response, and upon matching the realm will provide authentication.   However CM will not send REGISTER message to register a SIP trunk.  Most providers require registration.

HTH,
Wes

On Monday, December 01, 2008 5:34:03 PM, Wes Sisk  <mailto:wsisk at cisco.com> <wsisk at cisco.com> wrote:



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  <mailto:dane.newman at gmail.com> <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> 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] On Behalf Of Dane Newman
Sent: Monday, December 01, 2008 10:58 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] SIP trunk CUCM 7

 

I just purchased a sip trunk from 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
  





 



  _____  



 
_______________________________________________
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/20081202/e3a1f311/attachment.html>


More information about the cisco-voip mailing list