Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

Partner Central

IP Trunking

Cisco Powered Managed Services

A Cisco Powered managed IP trunking service is a Session Initiation Protocol (SIP)-based trunk from the service provider to an IP PBX or key system, delivering voice, multimedia, and data traffic.

The service provider provides basic connectivity, emergency services, dial plan management and operator services. Local and long distance call connections are completed by the service provider. A managed IP trunking service includes the IP termination service and features a PBX with a gateway, an IAD or an IP PBX.

The service provides comprehensive SLAs covering the overall performance of the service, and online access to real-time and historical service-performance reports.

To view a complete list of requirements for this service, please visit the Managed Services: Portfolio Requirements

To view the full Bills of Material for this service, please visit the MSCP Portfolio: Bills of Material



Architecture and Technical Attributes


Requirement Auditor Instructions (What to Look for)
IP Trunking Service must be in compliance with RFC 3261 Partner must demonstrate that the service offers Internet connectivity across the MPLS backbone to eliminate the need to carry Internet bound traffic back to a customers regional HQ site and then on to the external Internet connection
IP Trunking Architecture must support Emergency Calls As an example, E911 or country-specific regulatory specification
IP Trunking Architecture must be in compliance with RFC3264 “An Offer/Answer Model with Session Description Protocol (SDP)” Part of the Marketing Service Description (MSD) or Partner must be able to demonstrate network design option available to customer
IP Trunking Service support for Managed Dial Plan Service: unified dial plan across multiple locations (N-digit/private dial plan w/ overlap between enterprises) Part of the MSD or Partner must be able to demonstrate network design option available to customer in documentation
The Service Elements of IP Trunking Architecture must be hardened against DOS attacks and secured appropriately to counter unauthorized access Conformance to NFP best practices for securing service elements using the same methods described for the MPLS VPN and other connectivity services
IP Trunking Architecture must be in compliance with RFC 2833 (DTMF Relay) Part of the Marketing Service Description (MSD) or Partner must be able to demonstrate network design option available to customer
IP Trunking Service must support the codecs G.711 u-law and/or a-law Part of the Marketing Service Description (MSD) or Partner must be able to demonstrate network design option available to customer
IP Trunking Architecture must provide demarcation between service provider network and customer network in order to grant the correct operational independence and security level for both networks Part of the Marketing Service Description (MSD) or service diagram demonstrating compliance with Cisco IP-to-IP gateway

Architecture and Technical Attributes


Requirement Auditor Instructions (What to Look for)
IP Trunking Service must be in compliance with RFC 3261 Partner must demonstrate that the service offers Internet connectivity across the MPLS backbone to eliminate the need to carry Internet bound traffic back to a customers regional HQ site and then on to the external Internet connection
IP Trunking Architecture must support Emergency Calls As an example, E911 or country-specific regulatory specification
IP Trunking Architecture must be in compliance with RFC 2833 (DTMF Relay) Part of the Marketing Service Description (MSD) or Partner must be able to demonstrate network design option available to customer
IP Trunking Service must support the codecs G.711 u-law and/or a-law Part of the Marketing Service Description (MSD) or Partner must be able to demonstrate network design option available to customer
IP Trunking Architecture must provide demarcation between service provider network and customer network in order to grant the correct operational independence and security level for both networks Part of the Marketing Service Description (MSD) or service diagram demonstrating compliance with Cisco IP-to-IP gateway

There are no services being offered at the Legacy level.

Related Tools