Which two SIP packet handling behavior will result with this CISCO Unified Border Element (CUBE) configuration?

Refer to the exhibit. Which two SIP packet handling behavior will result with this CISCO Unified Border Element (CUBE) configuration? (Choose two)


A. Unsupported content/MIME pass-through
B. SIP Refer is not supported when received on this CUBE
C. Privacy headers received on SIP massage will be replaced with NON-privacy headers on this CUBE
D. P-Preferred identities
E. Mid-call codec changes

cisco-exams

2 thoughts on “Which two SIP packet handling behavior will result with this CISCO Unified Border Element (CUBE) configuration?

  1. no supplementary-service sip refer: This is used to disable The SIP REFER method and to rather use an INVITE to complete supplementary services such as call transfer. Typically when an event such a transfer occurs within a dialog, CUCM/endpoint will send a REFER to the CUBE. CUBE will then pass this REFER to the other end. If you dont want to use this in scenarios where the ITSP cube is talking to doesnt support this, then you can disable it or do waht is called REFER consumption and then allow CUBE to re-originate the transfer using a normal INVITE.

Leave a Reply

Your email address will not be published. Required fields are marked *


The reCAPTCHA verification period has expired. Please reload the page.