Solved: carrier sip service

rvincent · ‎09-06-2008

Customer is getting callmanager business edition. Their carrier [Paetec] is providing a 3meg sip trunk to provide internet and voice. It will terminate into a 2851 router.

I've yet to configured sip service, and could use some help.

What is the sip handoff - ethernet?T1?

Do phones need to be sip or can they be sccp?

Is there a good doc showing the ios config?

Any info would be appreciated.

thanks

Rob

Marwan ALshawi · ‎09-07-2008

as u know the well know signaling protocall n gateways is h323 aslo the new and most growing one now is sip

with sip u can use hotsname to send and recieve calls and numbers as well

anyway

for ur case u will use ur voice equipment normally, like sccp,h323, and callmanager

only on the gateqay u need to creat dial-peer use sip point to the service provider

the following document relate to callmanager expres but the dial-peers for pstn and sip will be similer and the technology is the same

http://www.cisco.com/en/US/products/sw/voicesw/ps4625/products_configuration_example09186a00808f9666.shtml

good luck

if helpful Rate

View solution in original post

Michael Owuor · ‎09-07-2008

Hi Rob and Marwan (+5 for your good input),

Here's additional information on how some service providers such as Paetec and AT&T are connecting their customers. SIP trunks are increasingly being used in conjunction with a Session Border Controller such as the Cisco Unified Border Element (CUBE) as an alternative to traditional PSTN connections. In your case the 2851 could provide the CUBE functionality. Phones could use whicherver protocol is desired. It shouldn't matter. The CallManager will route the calls out a SIP Trunk.

The CUBE provides a network-to-network interface point for:

* Signaling Interworking (H.323, SIP)

* Media Interworking (DTMF, Fax, Modem and Codec Transcoding)

* Address and Port translations (Privacy and Topology Hiding)

* Billing and CDR Normalization

* QoS and Bandwidth Management (QoS marking using TOS, DSCP and bandwidth enforcement using RSVP and codec filtering)

Here are some sample configurations

Unified Border Element (CUBE) with Cisco Unified Communications Manager (CUCM) Configuration Example

http://www.cisco.com/en/US/products/sw/voicesw/ps5640/products_configuration_example09186a00808ead0f.shtml

AT&T IP Toll-Free: Connecting Cisco Unified Communications Manager 6.1(1a) via the Cisco Unified Border Element using SIP

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/pbx/interop/notes/668298.pdf

AT&T IP FlexReach: Connecting Cisco Unified Communications Manager 6.1(1a) via the Cisco Unified Border Element using SIP

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/pbx/interop/notes/685803.pdf

Note that phones can still be SCCP.

Hope this helps.

Regards,

Michael.

View solution in original post

Marwan ALshawi · ‎09-07-2008

as u know the well know signaling protocall n gateways is h323 aslo the new and most growing one now is sip

with sip u can use hotsname to send and recieve calls and numbers as well

anyway

for ur case u will use ur voice equipment normally, like sccp,h323, and callmanager

only on the gateqay u need to creat dial-peer use sip point to the service provider

the following document relate to callmanager expres but the dial-peers for pstn and sip will be similer and the technology is the same

http://www.cisco.com/en/US/products/sw/voicesw/ps4625/products_configuration_example09186a00808f9666.shtml

good luck

if helpful Rate

Michael Owuor · ‎09-07-2008

Hi Rob and Marwan (+5 for your good input),

Here's additional information on how some service providers such as Paetec and AT&T are connecting their customers. SIP trunks are increasingly being used in conjunction with a Session Border Controller such as the Cisco Unified Border Element (CUBE) as an alternative to traditional PSTN connections. In your case the 2851 could provide the CUBE functionality. Phones could use whicherver protocol is desired. It shouldn't matter. The CallManager will route the calls out a SIP Trunk.

The CUBE provides a network-to-network interface point for:

* Signaling Interworking (H.323, SIP)

* Media Interworking (DTMF, Fax, Modem and Codec Transcoding)

* Address and Port translations (Privacy and Topology Hiding)

* Billing and CDR Normalization

* QoS and Bandwidth Management (QoS marking using TOS, DSCP and bandwidth enforcement using RSVP and codec filtering)

Here are some sample configurations

Unified Border Element (CUBE) with Cisco Unified Communications Manager (CUCM) Configuration Example

http://www.cisco.com/en/US/products/sw/voicesw/ps5640/products_configuration_example09186a00808ead0f.shtml

AT&T IP Toll-Free: Connecting Cisco Unified Communications Manager 6.1(1a) via the Cisco Unified Border Element using SIP

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/pbx/interop/notes/668298.pdf

AT&T IP FlexReach: Connecting Cisco Unified Communications Manager 6.1(1a) via the Cisco Unified Border Element using SIP

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/pbx/interop/notes/685803.pdf

Note that phones can still be SCCP.

Hope this helps.

Regards,

Michael.

Marwan ALshawi · ‎09-07-2008

hi Michael

first thanks for rating

and this is 5+ without doubt for ur nice add :)

rvincent · ‎09-09-2008

marwan

Michael

I'd like to thank you both for providing the information you did. It will be most helpful when I start digging into this next week

thanks again

Rob

tcekada · ‎09-09-2008

Michael,

Is CUBE necessary/Mandatory to integrate and configure the SIP provider trunk into Call Manager?? Could you shed any light on when you need CUBE and when you don't??

Thanks,

Tony

Michael Owuor · ‎09-09-2008

Hi Tony,

Using CUBE is not mandatory, but it is indeed strongly recommended. A SIP trunk fronted by CUBE offers a number of advantages over using a direct SIP trunk to CallManager.

Some of these advantages include:

1. CUCM does not support SIP Register or sending outbound options for keepalive.

2. With CUCM, the demarcation point is not clearly defined, so troubleshooting issues might be a little difficult.

3. CUBE provides number normalization which CUCM 4.x, 5.x or 6.x does not provide. I think this is available in CUCM 7.x.

4. CUBE can provide Call Admission Control.

5. CUBE can also provide MTP and gateway functionality such as TDM interfaces and SRST.

6. CUBE provides capabilities around H.323-SIP interworking.

7. With CUBE, you don't need direct network connectivity between the CUCM and the Service Provider network.

8. The CUBE router may leverage the IOS Firewall features to provide added security to the enterprise network.

So when in doubt, you certainly want to go CUBE.

Hope this helps, Tony.

Regards,

Michael.

febinattingal · ‎11-10-2008

Can you Explain how cucm 6.x and pbx integration .My connectivity between cucm and pbx through vpn.