[cisco-voip] CUCM SIP To PSTN

[Nick Matthews]

Technically you could have a router terminating DMVPN connections, a
full BGP routing table, running UCS express on a SRE with VMware,
doing IOS firewall, and doing CUBE at the same time.

For most folks it's about task isolation, or sometimes groups are
silo'd and want their own equipment. As long as the CPU/memory are
fine it's not a problem. Sometimes calculating the estimated CPU is an
art.  But it is very common to turn an existing gateway into CUBE, and
even keep some TDM on it.

-nick

On Fri, Jun 15, 2012 at 1:01 AM, Paul <asobihoudai at yahoo.com> wrote:
> I think primary factors for this would be the BHCA call volume (i.e., the maximum number of simultaneous SIP sessions expected), the maximum number of simultaneous SIP sessions required for the gateway to support (if it even can cover the customer requirements), and of course cost since those CUBE licenses are PRICEY!
>
> E.g., if you're going to max out a 3945E with 2500 simultaneous SIP sessions, it's probably not a wise idea to use it for much else...
>
>
> ----- Original Message -----
> From: Lelio Fulgenzi <lelio at uoguelph.ca>
> To: Nick Matthews <matthnick at gmail.com>
> Cc: "cisco-voip at puck.nether.net" <cisco-voip at puck.nether.net>
> Sent: Friday, June 15, 2012 12:39 AM
> Subject: Re: [cisco-voip] CUCM SIP To PSTN
>
> The question I've had is, what is the best practice for this? Should you use a separate router for the CUBE functionality? Or use an existing gateway? I'm sure the answer is 'it depends' ;), but if there are some scenarios where it makes sense not to, that would be good to know.
>
> Sent from my iPhone...
>
> "There's no place like 127.0.0.1"
>
> On Jun 14, 2012, at 7:17 PM, Nick Matthews <matthnick at gmail.com> wrote:
>
>> The scenario of:
>> CUCM--SIP--GW--SIP--Provider
>>
>> The gateway magically turns into a CUBE, and there's a whole bunch of
>> marketing and technical information on what happens when you do that.
>>
>> If you compare these two solutions:
>> -CUCM direct SIP trunk to provider
>> -Use MTP to keep media to a single IP
>> -Or use NAT to keep internal addressing safe
>> or
>> -Use CUBE
>>
>> There's a whole bunch of scalability and troubleshooting problems that
>> can arise from the first. Having a demarcation point at the GW (CUBE)
>> is extremely helpful. As well, it prevents you from needing to NAT SIP
>> which historically is a pretty terrible idea.  It also has some SIP
>> security and flexibility options, and is a good centralization point
>> for trunks.
>>
>> I haven't worked with anyone doing the direct trunk from CUCM to
>> provider. Many providers are going to make their own rules which will
>> include an SBC (industry term for CUBE).
>>
>> Short story - just use an SBC. There's about 3-4 compelling reasons.
>>
>> -nick
>>
>> On Thu, Jun 14, 2012 at 1:17 PM, Adel Abushaev <adel.abushaev at gmail.com> wrote:
>>> You can set up a SIP trunk to your SP, assuming that you are a SIP
>>> client of them.Otherwise, if you want to go over T1, then  you need to
>>> terminate SIP on the GW to translate between SIP and ISDN PRI or
>>> whatever other signalling you are using between you and telco.
>>>
>>> A.
>>>
>>> On Thu, Jun 14, 2012 at 5:44 AM,  <george.hendrix at l-3com.com> wrote:
>>>> Hi everyone,
>>>>
>>>>
>>>>
>>>>   I know with h.323 gateways in CUCM, you have to configure dial peers on
>>>> each gateway and for each CUCM.  Is it possible to create a SIP trunk
>>>> directly from CUCM to the Telco?  Without having to do any dial peers on the
>>>> gateway.  Or would it CUCM SIP <> SIP GW <> SIP PSTN, with SIP dial peers on
>>>> the SIP GW for both CUCM and the PSTN?
>>>>
>>>>
>>>>
>>>> Thanks,
>>>>
>>>>
>>>>
>>>> Bill Hendrix
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>
>> _______________________________________________
>> 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
>