Handle Multiple Early Dialog Messages

In a VoIP/SIP network, services such as call forward trigger multiple early dialog creation on Cisco UBE. SIP forking proxy will fork the SIP invite request to multiple endpoints and send out multiple forked invite responses to Cisco UBE. The Handle Multiple Early Dialog Messages feature enables Cisco UBE to respond to the forked invite responses.


Note

A SIP forking proxy is a proxy sever that routes messages to more than one destination.

Finding Feature Information

Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table.

Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/​go/​cfn. An account on Cisco.com is not required.

Restrictions for Handle Multiple Early Dialog Messages

This feature does not support the following calls:

  • SIP-H323

  • Media Anti-trombone

  • Session Description Protocol (SDP) Passthrough

  • SRTP-RTP interworking and SRTP passthrough

  • RSVP and RSVP interworking

  • TCL and VXML application

Information About Handle Early Dialog Messages

Multiple Early Dialog Support

The Handle Multiple Early Dialog Messages feature is enabled on Cisco UBE by default. When a service such as call forward triggers multiple early dialog creation on Cisco UBE, the SIP forking proxy will fork the SIP invite request to multiple endpoints and multiple invite responses are sent out to Cisco UBE. Cisco UBE handles the forked invite responses on the outbound call-leg and updates the peer (inbound) call-leg with an early dialog UPDATE message. This message renegotiates the media information, and Cisco UBE maps the appropriate dialog and responds to the forked responses.


Note

UPDATE and PRACK (rel1xx) support is a prerequisite for this feature.

Verifying the Handle Multiple Early Dialog Messages Feature

Perform this task to verify the multiple early dialog messages support on Cisco UBE. The show commands can be entered in any order.

SUMMARY STEPS

    1.    enable

    2.    show call active voice compact

    3.    show call active voice brief

    4.    show voip rtp connections


DETAILED STEPS
    Step 1   enable


    Example:
    Router> enable

    Enables privileged EXEC mode.

    Step 2   show call active voice compact


    Example:
    Router# show call active voice compact

<callID> A/O FAX T<sec> Codec type Peer Address IP R<ip>:<udp>
Total call-legs: 2
42 ANS T9 g711ulaw VOIP P1000 10.0.1.10:20796
43 ORG T9 g711ulaw VOIP P2000 10.0.2.20:21252

    Displays a compact version of the voice calls in progress.

    Step 3   show call active voice brief


    Example:
    Router#  show voice active voice brief | inc tx

dur hh:mm:ss tx:<packets>/<bytes> rx:<packets>/<bytes> dscp:<packets violation> media:<packets violation>
Tele <int> (callID) [channel_id] tx:<tot>/<v>/<fax>ms <codec> noise:<l> acom:<l> i/o:<l>/<l> dBm
speeds(bps): local <rx>/<tx> remote <rx>/<tx>
tx: <audio pkts>/<audio bytes>,<video pkts>/<video bytes>,<t120 pkts>/<t120 bytes>
dur 00:00:10 tx:507/81120 rx:510/81600 dscp:0 media:0
dur 00:00:10 tx:510/81600 rx:507/81120 dscp:0 media:0

    Displays a truncated version of the active voice or video call information.

    Step 4   show voip rtp connections


    Example:
    Router# show voip rtp connections

VoIP RTP active connections :
No. CallId dstCallId LocalRTP RmtRTP LocalIP 			RemoteIP
1 		42 				43 							18440 			20796 	9.44.44.44 9.44.46.21
2 		43 				42 							22668 			21252 	9.44.44.44 9.44.46.25
Found 2 active RTP connections

    Displays RTP-named event packets.

    Troubleshooting Tips

    The following commands can help troubleshoot the Handle Multiple Early Dialog Messages feature:

    • debug ccsip all

    • debug voip ccapi inout

    Feature Information for Handle Multiple Early Dialog Messages

    The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.

    Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/​go/​cfn. An account on Cisco.com is not required.
    Table 1 Feature Information for Handle Multiple Early Dialog Messages

    Feature Name

    Releases

    Feature Information

    Handle Multiple Early Dialog Messages

    15.2(2)T

    In a VoIP/SIP network, services such as call forward trigger multiple early dialog creation on Cisco UBE. SIP forking proxy will fork the SIP invite request to multiple endpoints and send out multiple forked invite responses to Cisco UBE. The Handle Multiple Early Dialog Messages feature enables Cisco UBE to respond to the forked invite responses.

    No commands were introduced or modified by this feature.