 Feedback
|
Table Of Contents
Support of SIP SUBSCRIBE/NOTIFY Methods
Related Features and Technologies
Supported Standards, MIBs, and RFCs
Provisioning SUBSCRIBE/NOTIFY Methods
Enabling SUBSCRIBE/NOTIFY Methods
Disabling SUBSCRIBE/NOTIFY Methods
Provisioning Unsolicited Notifications
Enabling Unsolicited Notifications
Disabling Unsolicited Notifications
Provisioning Subscription Duration
Provisioning Minimum Subscription Duration for Telephony Event
Provisioning Maximum Duration for SUBSCRIBE
Obtaining Documentation and Submitting a Service Request
Support of SIP SUBSCRIBE/NOTIFY Methods
Document Release History
Feature History
9.4(1)
This feature was introduced on the Cisco Media Gateway Controller (MGC) software.
The Support of Session Initiated Protocol (SIP) SUBSCRIBE/NOTIFY Methods feature is described in the following sections:
•
Supported Standards, MIBs, and RFCs
•
Feature Overview
The Support of SIP SUBSCRIBE/NOTIFY Methods feature enables the Cisco MGC to act as a Notifier in a SIP network. This feature provides the Cisco MGC the ability to receive SUBSCRIBE messages from a SIP user agent and to return NOTIFY messages to that SIP user agent.
If this feature is enabled, and a SUBSCRIBE message is received, the MGC sends an MGCP NOTIFY message requesting the Dual-Tone Multi-Frequency (DTMF) data to the associated Media Gateway Controller Protocol (MGCP) media gateway. If the MGCP media gateway receives DTMF, it sends the DTMF digits to the MGC. The MGC returns these DTMF digits to the subscribing SIP user agent in out-of-band NOTIFY messages (these NOTIFY messages do not use the RTP stream). This is useful for a variety of applications that monitor calls for a specific event and perform an action based upon the received event.
If the Cisco MGC receives an unsolicited SIP NOTIFY message with DTMF, the MGC uses MGCP commands to cause the connected MGCP media gateway to send the specified DTMF tone(s) to the PSTN.
Benefits
This feature has the following benefits:
Support for SIP-Based ITS
This feature enables DTMF to be passed from Skinny phones connected to an ITS over SIP to the Cisco MGC, and then out to the PSTN.
Support of Pre-Paid Card Services
This feature enables the Cisco MGC to support pre-paid card services. Detection of the long pound sign (a DTMF digit) enables some pre-paid card services and IP Centrex.
Mid-Call DTMF Access Support
This feature provides SIP Back-to-Back User Agents (B2BUAs) access to mid-call DTMF to enable support of follow-on card services (long pound sign detection), and feature invocation (for example, changing a call forwarding number).
Support for IP Private Branch Exchanges (PBXs)
Some IP PBXs require access to DTMF to invoke feature commands. This feature enables an increase in efficiency in networks, as these IP PBXs will no longer require an additional piece of hardware in the network to access DTMF.
Restrictions
This feature can only be used in conjunction with SIP user agents that support the standard SIP SUBSCRIBE/NOTIFY methods.
Related Features and Technologies
This feature is related to the following Cisco IOS software features:
•
•
Related Documents
This document contains information that is related strictly to this feature. The documents that contain additional information related to the Cisco Media Gateway Controller (MGC) are listed below:
•
•
•
•
•
•
•
•
•
•
•
•
•
Supported Platforms
The hardware platforms supported for the Cisco MGC software are described in the Release Notes for Cisco Media Gateway Controller Software Release 9.4(1).
Supported Standards, MIBs, and RFCs
This feature supports the following standards, MIBs, and RFCs.
Standards
No new standards are supported by this feature.MIBs
No new or modified MIBs are supported by this feature. For more information on the MIBs used in the Cisco MGC software, refer to the Cisco Media Gateway Controller Release 9 MIB Guide.RFCs
This feature supports the following RFCs•
•
This feature has the following limitations in support of the above RFCs:
•
•
•
Note
•
Prerequisites
You must have Cisco MGC software Release 9.4(1). Prerequisites for this release can be found in the Release Notes for the Cisco Media Gateway Controller Software Release 9.4(1).
Information on the prerequisites for the implementation of the related features in Cisco IOS software for the MGCP media gateways can be found in the Support for SIP SUBSCRIBE/NOTIFY Methods and the SIP-SRST and ITS/SRST SIP Enhancements feature module.
Provisioning Tasks
This section provides provisioning information for this feature. Additional examples of provisioning for the Cisco MGC software can be found in the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
The provisioning information appears in the following sections:
•
•
•
Planning for Provisioning
Before you provision this feature, determine the minimum and maximum duration for which a SIP device can subscribe to an event.
For more information on planning the provisioning for the rest of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Provisioning Procedures
This section contains the procedures necessary for provisioning this feature. This section covers the following topics:
•
•
•
Provisioning Basics
You can use the four procedures in this section to start a provisioning session, save provisioning data, end a provisioning session, and retrieve current provisioning data. For more detailed information about provisioning your Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Starting a Provisioning Session
You might need to start a provisioning session as part of your system operations. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
mml>prov-sta::srcver="curr_ver",dstver="mod_ver"Where:
•
Note
–
–
Note
•
For example, to use a configuration version called ver1 as the basis for a version to be called ver2, you would enter the following command:
mml>prov-sta::srcver="ver1",dstver="ver2"Once a provisioning session is underway, you can use the prov-add, prov-ed, and prov-dlt MML commands to add, modify, and delete components on your system. This document describes how to add, modify, and delete components for this feature. For more information on provisioning other components on your Cisco PGW 2200, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
There are two ways to close your provisioning session:
•
•
Saving and Activating Your Provisioning Changes
When you have completed making provisioning changes in your session, you must enter a command to save and activate your changes. There are two different provisioning MML commands that do this: prov-cpy and prov-dply.
Caution
The prov-cpy MML command is used to save and activate your changes on the active Cisco MGC. This command is typically used to save and activate changes on a Cisco MGC in a simplex configuration. However, you can use the prov-cpy MML command on Cisco MGCs in high-availability or continuous-service configurations, to save and activate your changes on the active Cisco MGC. If you choose to do this, you should enter the prov-sync MML command immediately afterwards, to have your changes saved and activated on the standby Cisco MGC.
Note
Caution
Note
The prov-dply MML command is used to save and activate your changes on the active and standby
Cisco MGCs. This command is typically used to save and activate changes on Cisco MGCs in high-availability or continuous-service configurations. This command should not be used on a Cisco MGC in a simplex configuration.
Note
Ending a Provisioning Session Without Activating your Changes
You may find that you want to end a provisioning session without saving and activating the changes you have entered during your session. To do so, you can enter the prov-stp MML command. This command ends your current provisioning session and your changes are not entered.
Retrieving Provisioning Data
You can use the prov-rtrv MML command to retrieve information about your current provisioning settings. The ways in which you can use this command to retrieve provisioning data are described in the following sections:
•
•
•
•
•
Retrieving Data for an Individual Component
You can retrieve provisioning data on any individual component on your system. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
mml>prov-rtrv:component:name=MML_nameWhere:
•
•
For example, to view the provisioning data for an IUA signaling service called iua1, you would enter the following command:
mml>prov-rtrv:sigsvcprop:name="iua1"Retrieving Data for Select Components
You can retrieve data on select components provisioned on your system. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
mml>prov-rtrv:all
Note
Retrieving Data for All Components of a Particular Type
You can retrieve provisioning data on all components of a particular type on your system. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
mml>prov-rtrv:component:"all"Where: component is the MML component type associated with the desired component group. You can find a complete list of MML component types in the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Note
mml>prov-rtrv:propComp:name="compName" | name="ss7famName"
Where:
propComp—MML component name appropriate to the property type you want to retrieve, as listed below:
sigsvcprop—Provides maintenance access to the properties of signaling services
trnkgrpprop—Provides maintenance access to the properties of trunk groups
lnksetprop—Provides maintenance access to the properties of linksets
compName—MML name of a previously provisioned signaling service or trunk group
ss7famName—MML name of the SS7 family associated with the desired linksetFor example, to view the provisioning data for all signaling services, enter the following command:
mml>prov-rtrv:naspath:"all"Retrieving Data on the Current Provisioning Session
You can retrieve provisioning data on the current provisioning session. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
mml>prov-rtrv:sessionThe system returns a response similar to the following:
MGC-02 - Media Gateway Controller 2003-01-13 13:39:19M RTRV"session=jtest:session"/*Session ID = mml1SRCVER = activeDSTVER = jtest*/Retrieving Data on Supported Signaling Protocols
You can retrieve protocol data for the current provisioning session. To do this, log in to the active
Cisco MGC, start an MML session, and enter the following command:mml>prov-rtrv:variantsProvisioning SUBSCRIBE/NOTIFY Methods
The procedures for provisioning the SUBSCRIBE/NOTIFY methods are in the following sections:
•
•
Enabling SUBSCRIBE/NOTIFY Methods
Use the following steps to enable the SUBSCRIBE/NOTIFY methods:
Step 1
Step 2
mml> prov-ed:trnkgrpprop:name="trnkgrpnum", custgrpid="grpid", SubscribeNotifySupport=1Where:
•
•
For example, to enable the SUBSCRIBE/NOTIFY methods on a SIP trunk group called 3333, you would enter the following command:
mml> prov-ed:trnkgrpprop:name="3333", custgrpid="1111", SubscribeNotifySupport=1Step 3
Disabling SUBSCRIBE/NOTIFY Methods
Use the following steps to disable the SUBSCRIBE/NOTIFY methods:
Step 1
Step 2
mml> prov-ed:trnkgrpprop:name="trnkgrpnum", custgrpid="grpid", SubscribeNotifySupport=0Where:
•
•
For example, to disable the SUBSCRIBE/NOTIFY methods on a SIP trunk group called 3333, you would enter the following command:
mml> prov-ed:trnkgrpprop:name="3333",custgrpid="1111", SubscribeNotifySupport=0Step 3
Provisioning Unsolicited Notifications
The procedures for provisioning unsolicited notifications are in the following sections:
•
•
Enabling Unsolicited Notifications
Use the following steps to enable the Unsolicited NOTIFY method for SIP DTMF digits by the Cisco MGC:
Step 1
Step 2
mml> prov-ed:trnkgrpprop:name="trnkgrpnum", custgrpid="grpid", UnsolicitedNotifyMethod=1Where:
•
•
For example, to enable unsolicited notifications on a SIP trunk group called 3333, you would enter the following command:
mml> prov-ed:trnkgrpprop:name="3333",custgrpid="1111", UnsolicitedNotifyMethod=1Step 3
Disabling Unsolicited Notifications
Use the following steps to disable the Unsolicited NOTIFY method for SIP DTMF digits by the Cisco MGC:
Step 1
Step 2
mml> prov-ed:trnkgrpprop:name="trnkgrpnum", custgrpid="grpid", UnsolicitedNotifyMethod=0Where:
•
•
For example, to disable unsolicited notifications on a SIP trunk group called 3333, you would enter the following command:
mml> prov-ed:trnkgrpprop:name="3333",custgrpid="1111", UnsolicitedNotifyMethod=0Step 3
Provisioning Subscription Duration
The procedures for provisioning the duration data for subscriptions are in the following sections:
•
•
Provisioning Minimum Subscription Duration for Telephony Event
Use the following steps to define the minimum duration for which a telephony event can exist before it can be re-subscribed:
Step 1
Step 2
mml> prov-ed:trnkgrpprop:name="trnkgrpnum", custgrpid="grpid", MinEventSubscribeDuration=minsubWhere:
•
•
•
For example, to provision a telephony event to last a minimum of 200 ms on a SIP trunk group called 3333, you would enter the following command:
mml> prov-ed:trnkgrpprop:name="3333",custgrpid="1111", MinEventSubscribeDuration=200Step 3
Provisioning Maximum Duration for SUBSCRIBE
Use the following steps to define the maximum duration for which the subscription can exist before it needs a re-subscription:
Step 1
Step 2
mml> prov-ed:trnkgrpprop:name="trnkgrpnum", custgrpid="grpid", MaxSubscriptionDuration=maxsubWhere:
•
•
•
For example, to provision a subscription to last a maximum of 3600 seconds on a SIP trunk group called 3333, you would enter the following command:
mml> prov-ed:trnkgrpprop:name="3333",custgrpid="1111", MaxSubscriptionDuration=3600Step 3
Reference Information
The "Properties" section contains reference material related to this feature.
Properties
The properties in this section are modified for this feature. For information on other properties for the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
The parent objects for the properties involved in this feature are found in Table 8.
Table 8 Software Properties Related to this Feature
The properties modified for this feature are described in Table 9.
Glossary
Table 10 contains definitions of acronyms and technical terms used in this feature module.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
CCDE, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0812R)
