Mid-call Re-INVITE/UPDATE Consumption · Table 1: Feature Information for Mid-call Re-INVITE Consumption Feature Name Releases Feature Information TheCiscoUBEMid-call signallinghelpstodisables

Mid-call Re-INVITE/UPDATE Consumption

The Mid-call Re-INVITE/UPDATE consumption feature helps consume unwanted mid-callRe-INVITEs/UPDATEs locally avoiding interoperability issues that may arise due to these Re-INVITES.

• Feature Information for Mid-call Re-INVITE Consumption, page 1

• Prerequisites, page 2

• Restrictions, page 2

• Information About CUBE Mid-call Re-INVITE/UPDATE Consumption, page 3

• How to Configure Cisco UBE Mid-call Re-INVITE Consumption, page 3

• Verifying and Troubleshooting Cisco UBE Mid-call Re-INVITE/UPDATE Consumption, page 7

• Mid Call Codec Preservation, page 10

Feature Information for Mid-call Re-INVITE ConsumptionThe following table provides release information about the feature or features described in this module. Thistable lists only the software release that introduced support for a given feature in a given software releasetrain. 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.

Cisco Unified Border Element (Enterprise) SIP Support Configuration Guide, Cisco IOS XE Release 3S 1

http://www.cisco.com/go/cfn

Table 1: Feature Information for Mid-call Re-INVITE Consumption

Feature InformationReleasesFeature Name

The Cisco UBE Mid-callsignalling helps to disablescodec negotiation in themiddle of a call and preservesthe codec negotiated beforethe call.

The following keyword wasintroduced or modified:preserve-codec.

15.3(2)S, 15.3TCisco UBE Mid-callSignalling

The Mid-call Re-INVITEconsumption featureconsumes mid-callRe-INVITEs fromCUBE andhelps to avoid interoperabilityissues because of thesere-invites

The following commandswere introduced or modified:midcall-signaling.

15.2(1)T

Cisco IOS XE Release 3.6S

Cisco UBE Mid-callRe-INVITE/UPDATEConsumption

Prerequisites• Enable CUBE application on a device

Restrictions• SIP-H.323 calls are not supported.

• TDM Gateways are not supported.

• Session Description Protocol (SDP) -passthrough is not supported

•When codec T is configured, the offer from CUBE has only audio codecs, and so the video codecs arenot consumed.

• Re-invites are not consumed if media flow-around is configured.

• Re-invites are not consumed if media anti-tromboning is configured.

• Video transcoding is not supported.

• Secure Real-time Protocol - Real-time Protocol (SRTP-RTP) supplementary services are not supported.

• Multicast Music On Hold (MMOH) is not supported.

Cisco Unified Border Element (Enterprise) SIP Support Configuration Guide, Cisco IOS XE Release 3S2

Mid-call Re-INVITE/UPDATE ConsumptionPrerequisites

http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube/configuration/cube-book/voi-cube-overview.html#task_BDEFEEAC4E2F49CDAF08B6E0C72FB01F

•When themidcall-signaling passthrumedia-change command is configured and high-density transcoderis enabled, there might be some impact on Digital Signal Processing (DSP) resources as the transcodermight be used for all the calls.

• Session timer is handled leg by leg whenever this feature is configured.

Information About CUBE Mid-call Re-INVITE/UPDATEConsumption

The purpose of Mid-call Re-INVITE Consumption is to ensure smooth interoperability of supplementaryservices (like audio hold, resume and call transfer) by consuming unnecessary re-invites (mid-call signaling)locally.

This can be done in three different ways:

• Converting a delayed offer to an early offer—

• Passthrough of mid-call signaling regarding media change—Mid-call signaling is passed through onlywhen bidirectional media like T.38 or video is added.

• Blocking all mid-call signaling for a specific SIP trunk.

This feature should be used as a last resort only when there is no other option in CUBE. This is becauseconfiguring this feature can break video-related features. For Delay-offer Re-INVITE, the configuredcodec will be passed as an offer in 200 message to change the codec, the transcoder is added in the answer.

Note

How to Configure Cisco UBE Mid-call Re-INVITE Consumption

Configuring Passthrough of Mid-call SignallingPerform this task to configure passthrough of mid-call signaling (as Re-invites) only when bidirectional mediais added.

SUMMARY STEPS

1. enable2. configure terminal3. Configure passthrough of mid-call signalling changes only when bidirectional media is added.

• midcall-signaling passthru media-change in Global VoIP configuration mode.

• voice-class sip mid-call signaling passthru media-change in dial-peer configuration mode.

4. end


Mid-call Re-INVITE/UPDATE ConsumptionInformation About CUBE Mid-call Re-INVITE/UPDATE Consumption

DETAILED STEPS

PurposeCommand or Action

Enables privileged EXEC mode.enableStep 1

Example:Device> enable

• Enter your password if prompted.

Enters global configuration mode.configure terminal

Example:Device# configure terminal

Step 2

Re-Invites are passed through only whenbidirectional media is added.

Configure passthrough of mid-call signalling changes only whenbidirectional media is added.

Step 3

• midcall-signaling passthru media-change in Global VoIPconfiguration mode.

• voice-class sip mid-call signaling passthru media-change indial-peer configuration mode.

Example:In Global VoIP configuration mode:Device(config)# voice service voipDevice(conf-voi-serv)# sipDevice(conf-serv-sip)# midcall-signaling passthru media-change

Example:In Dial-peer configuration mode:Device(config)# dial-peer voice 2 voipDevice(config-dial-peer)# voice-class sip mid-call signalingpassthru media-change

Exits to privileged EXEC mode.endStep 4

Blocking All Mid-Call SignalingPerform this task to block all mid-call signaling:


Mid-call Re-INVITE/UPDATE ConsumptionBlocking All Mid-Call Signaling

SUMMARY STEPS

1. enable2. configure terminal3. Configure blocking of all mid-call signaling changes:

• midcall-signaling block in Global VoIP configuration mode.

• voice-class sip mid-call signaling block in dial-peer configuration mode.

4. end

DETAILED STEPS







Step 2

Mid-call signaling is always blocked.Configure blocking of all mid-call signaling changes:Step 3

• midcall-signaling block in Global VoIP configuration mode.

• voice-class sip mid-call signaling block in dial-peer configurationmode.

Example:In Global VoIP configuration mode:Device(config)# voice service voipDevice(conf-voi-serv)# sipDevice(conf-serv-sip)# midcall-signaling block

Example:In Dial-peer configuration mode:Device(config)# dial-peer voice 2 voipDevice(config-dial-peer)# voice-class sip mid-call signalingblock



Mid-call Re-INVITE/UPDATE ConsumptionBlocking All Mid-Call Signaling

Configuring Delayed Offer to Early Offer

SUMMARY STEPS

1. enable2. configure terminal3. Configure conversion of a delayed offer to an early offer:

• voice-class sip early-offer forced in dial-peer configuration mode

• early-offer forced in global VoIP configuration mode

4. end

DETAILED STEPS


Enables privileged EXECmode. Enteryour password if prompted.

enable

Example:

Device> enable

Step 1


Example:

Device# configure terminal

Step 2

Configure conversion of a delayed offer to an early offer:Step 3

• voice-class sip early-offer forced in dial-peer configuration mode

• early-offer forced in global VoIP configuration mode

Example:In dial-peer configuration mode:

Device (config) dial-peer voice 10 voipDevice (config-dial-peer) voice-class sip early-offer forcedDevice (config-dial-peer) end

Example:In global VoIP SIP mode:

Device(config)# voice service voipDevice (config-voi-serv) sipDevice (config-voi-sip) early-offer forcedDevice (config-voi-sip) end


Mid-call Re-INVITE/UPDATE ConsumptionConfiguring Delayed Offer to Early Offer



Verifying and Troubleshooting Cisco UBE Mid-callRe-INVITE/UPDATE Consumption

Perform this task to verify mid-call Re-INVITE/UPDATE routing support on Cisco UBE

SUMMARY STEPS

1. enable2. debug ccsip all3. debug voip ccapi inout

DETAILED STEPS

Step 1 enableEnables privileged EXEC mode.


Step 2 debug ccsip allUse this command to enable SIP related debugging.

Example:Device# debug ccsip allReceived:INVITE sip:5555555555@[2208:1:1:1:1:1:1:1118]:5060 SIP/2.0Via: SIP/2.0/UDP [2208:1:1:1:1:1:1:1115]:5060;branch=z9hG4bK83AE3Remote-Party-ID: <sip:2222222222@[2208:1:1:1:1:1:1:1115]>;party=calling;screen=no;privacy=offFrom: <sip:2222222222@[2208:1:1:1:1:1:1:1115]>;tag=627460F0-1259To: <sip:5555555555@[2208:1:1:1:1:1:1:1118]>Date: Tue, 01 Mar 2011 08:49:48 GMTCall-ID: B30FCDEB-431711E0-8EDECB51-E9F6B1F1@2208:1:1:1:1:1:1:1115Supported: 100rel,timer,resource-priority,replacesRequire: sdp-anatMin-SE: 1800Cisco-Guid: 2948477781-1125585376-2396638033-3925258737User-Agent: Cisco-SIPGateway/IOS-15.1(3.14.2)PIA16Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTERCSeq: 101 INVITEMax-Forwards: 70Timestamp: 1298969388Contact: <sip:2222222222@[2208:1:1:1:1:1:1:1115]:5060>Expires: 180Allow-Events: telephone-eventContent-Type: application/sdpContent-Disposition: session;handling=required


Mid-call Re-INVITE/UPDATE ConsumptionVerifying and Troubleshooting Cisco UBE Mid-call Re-INVITE/UPDATE Consumption

Content-Length: 495v=0o=CiscoSystemsSIP-GW-UserAgent 7880 7375 IN IP6 2208:1:1:1:1:1:1:1115s=SIP Callc=IN IP6 2208:1:1:1:1:1:1:1115t=0 0a=group:ANAT 1 2m=audio 17836 RTP/AVP 0 101 19c=IN IP6 2208:1:1:1:1:1:1:1115a=mid:1a=rtpmap:0 PCMU/8000a=rtpmap:101 telephone-event/8000a=fmtp:101 0-16a=rtpmap:19 CN/8000a=ptime:20m=audio 18938 RTP/AVP 0 101 19c=IN IP4 9.45.36.111a=mid:2a=rtpmap:0 PCMU/8000a=rtpmap:101 telephone-event/8000a=fmtp:101 0-16a=rtpmap:19 CN/8000a=ptime:20“Received:INVITE sip:2222222222@[2208:1:1:1:1:1:1:1117]:5060 SIP/2.0Via: SIP/2.0/UDP [2208:1:1:1:1:1:1:1116]:5060;branch=z9hG4bK38ACERemote-Party-ID: <sip:5555555555@[2208:1:1:1:1:1:1:1116]>;party=calling;screen=no;privacy=offFrom: <sip:5555555555@[2208:1:1:1:1:1:1:1116]>;tag=4FE8C9C-1630To: <sip:2222222222@[2208:1:1:1:1:1:1:1117]>;tag=1001045C-992Date: Thu, 10 Feb 2011 12:15:08 GMTCall-ID: 5DEDB77E-ADC11208-808BE770-8FCACF34@2208:1:1:1:1:1:1:1117Supported: 100rel,timer,resource-priority,replaces,sdp-anatMin-SE: 1800Cisco-Guid: 1432849350-0876876256-2424621905-3925258737User-Agent: Cisco-SIPGateway/IOS-15.1(3.14.2)PIA16Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTERCSeq: 101 INVITEMax-Forwards: 70Timestamp: 1297340108Contact: <sip:5555555555@[2208:1:1:1:1:1:1:1116]:5060>Expires: 180Allow-Events: telephone-eventContent-Type: application/sdpContent-Length: 424v=0o=CiscoSystemsSIP-GW-UserAgent 8002 7261 IN IP6 2208:1:1:1:1:1:1:1116s=SIP Callc=IN IP6 2208:1:1:1:1:1:1:1116t=0 0m=image 17278 udptl t38c=IN IP6 2208:1:1:1:1:1:1:1116a=T38FaxVersion:0a=T38MaxBitRate:14400a=T38FaxFillBitRemoval:0a=T38FaxTranscodingMMR:0a=T38FaxTranscodingJBIG:0a=T38FaxRateManagement:transferredTCFa=T38FaxMaxBuffer:200a=T38FaxMaxDatagram:320a=T38FaxUdpEC:t38UDPRedundancy

Step 3 debug voip ccapi inout

Example:The voice gateway sets up negotiating capability with the terminating VoIP leg.*Mar 1 15:36:05.028: //45/xxxxxxxxxxxx/CCAPI/cc_api_caps_ind: (dstVdbPtr=0x637EC1E0, dstCallId=0x2C, srcCallId=0x2D,

caps={codec=0x4, fax_rate=0x2, vad=0x2, modem=0x0codec_bytes=20, signal_type=2})



*Mar 1 15:36:05.028: //45/xxxxxxxxxxxx/CCAPI/cc_api_caps_ind:(Playout: mode 0,initial 60,min 40, max 300)

The capabilities are acknowledged for both call legs.

Example:

*Mar 1 15:36:05.028: //45/xxxxxxxxxxxx/CCAPI/cc_api_caps_ack: (dstVdbPtr=0x637EC1E0, dstCallId=0x2C, srcCallId=0x2D,

caps={codec=0x4, fax_rate=0x2, vad=0x2, modem=0x0codec_bytes=20, signal_type=2, seq_num_start=2944})

*Mar 1 15:36:05.028: //44/xxxxxxxxxxxx/CCAPI/cc_api_caps_ack: (dstVdbPtr=0x62EC61A4, dstCallId=0x2D, srcCallId=0x2C,

caps={codec=0x4, fax_rate=0x2, vad=0x2, modem=0x0codec_bytes=20, signal_type=2, seq_num_start=2944})

*Mar 1 15:36:05.032: //44/xxxxxxxxxxxx/CCAPI/cc_api_voice_mode_event: callID=0x2C*Mar 1 15:36:05.032: //44/45F2AAE28044/CCAPI/cc_api_voice_mode_event: Call Pointer =634A430C*Mar 1 15:36:05.032: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(52=CC_EV_VOICE_MODE_DONE), cid(44), disp(0)*Mar 1 15:36:05.032: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct:Router#Router# cid(44)st(SSA_CS_ACTIVE)ev(SSA_EV_VOICE_MODE_DONE)oldst(SSA_CS_CONFERENCING)cfid(21)csize(2)in(1)fDest(1)*Mar 1 15:36:05.032: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct: -cid2(45)st2(SSA_CS_ACTIVE)oldst2(SSA_CS_ALERT_RCVD)*Mar 1 15:36:05.032: //44/45F2AAE28044/SSAPP:10002:21/ssaIgnore: cid(44), st(SSA_CS_ACTIVE),oldst(5), ev(52)Router#Router#! digit punchedRouter#

The phone at the terminating gateway enters digit1.

Example:*Mar 1 15:36:11.204: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_digit_begin: (dstVdbPtr=0x637EC1E0,dstCallId=0x2C, srcCallId=0x2D,

digit=1, digit_begin_flags=0x0, rtp_timestamp=0x0rtp_expiration=0x0, dest_mask=0x2)

*Mar 1 15:36:11.504: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_digit_end: (dstVdbPtr=0x637EC1E0, dstCallId=0x2C, srcCallId=0x2D,

digit=1,duration=300,xruleCallingTag=0,xruleCalledTag=0, dest_mask=0x2), digit_tone_mode=0

The phone at the terminating gateway enters digit 2.

Example:*Mar 1 15:36:11.604: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_digit_begin: (dstVdbPtr=0x637EC1E0, dstCallId=0x2C, srcCallId=0x2D,

digit=2, digit_begin_flags=0x0, rtp_timestamp=0x0rtp_expiration=0x0, dest_mask=0x2)

*Mar 1 15:36:11.904: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_digit_end: (dstVdbPtr=0x637EC1E0, dstCallId=0x2C, srcCallId=0x2D,

digit=2,duration=300,xruleCallingTag=0,xruleCalledTag=0, dest_mask=0x2), digit_tone_mode=0Router#Router#*Mar 1 15:36:14.476: //-1/xxxxxxxxxxxx/CCAPI/cc_handle_periodic_timer: Callingthe callback, ccTimerctx - 0x628B6330*Mar 1 15:36:14.476: //-1/xxxxxxxxxxxx/CCAPI/ccTimerStart: ccTimerctx - 0x628B6330Router#Router# !call hung up The user at the terminating gateway hangs up the call.Router#



Mid Call Codec PreservationYou can enable or disable codec negotiation in the middle of a call. This method defines whether a codec canbe negotiated after a call has been initiated.

Configuring Mid Call Codec Preservation at the Global Level

SUMMARY STEPS

1. enable2. configure terminal3. voice service voip4. sip5. midcall-signaling preserve-codec6. exit

DETAILED STEPS







Step 2

Enters voice service VoIP configuration mode.voice service voip

Example:Device(config)# voice service voip

Step 3

Enters voice service VoIP SIP configuration mode.sip

Example:Device(conf-voi-serv)# sip

Step 4

Disables codec negotiation in the middle of a call andpreserves the codec negotiated before the call.

midcall-signaling preserve-codec

Example:Device(conf-serv-sip)# midcall-signalingpreserve-codec

Step 5


Mid-call Re-INVITE/UPDATE ConsumptionMid Call Codec Preservation


Exits voice service SIP configuration mode and returns toglobal configuration mode.

exit

Example:Device(conf-serv-sip)# exit

Step 6

Configuring Mid Call Codec Preservation at the Dial Peer Level

SUMMARY STEPS

1. enable2. configure terminal3. dial-peer voice dial-peer tag voip4. voice-class sip midcall-signaling preserve-codec5. exit

DETAILED STEPS







Step 2

Enters dial-peer voice configuration mode.dial-peer voice dial-peer tag voip

Example:Device(config)# dial-peer voice 2 voip

Step 3

Disables codec negotiation in the middle of a call andpreserves the codec negotiated before the call.

voice-class sip midcall-signaling preserve-codec

Example:Device(conf-dial-peer)# voice-class sipmidcall-signaling preserve-codec

Step 4


Mid-call Re-INVITE/UPDATE ConsumptionConfiguring Mid Call Codec Preservation at the Dial Peer Level


Exits dial-peer voice configuration mode and returns toglobal configuration mode.

exit

Example:Device(config-dial-peer)# exit

Step 5

Example: Configuring Mid Call Codec Preservation at the Global Level

Example: Configuring Mid Call Codec Preservation at the Global LevelDevice(config)# voice service voipDevice(conf-voi-serv)# no ip address trusted authenticateDevice(conf-voi-serv)# allow-connections sip to sipDevice(conf-voi-serv)# sipDevice(conf-serv-sip)# midcall-signaling preserve-codec

Example: Configuring Mid Call Codec Preservation at the Dial Peer Level

Example: Configuring Mid Call Codec Preservation at the Dial Peer Leveldial-peer voice 107 voipdestination-pattern 74000session protocol sipv2session target ipv4:9.45.36.9incoming called-number 84000voice-class codec 1 offer-all!dial-peer voice 110 voipdestination-pattern 84000session protocol sipv2session target ipv4:9.45.35.2incoming called-number 74000voice-class codec 1 offer-allvoice-class sip midcall-signaling preserve-codec!


Mid-call Re-INVITE/UPDATE ConsumptionExample: Configuring Mid Call Codec Preservation at the Global Level

Documents

Mid-call Re-INVITE/UPDATE Consumption · Table 1: Feature Information for Mid-call Re-INVITE Consumption Feature Name Releases Feature Information TheCiscoUBEMid-call signallinghelpstodisables