Free 1z0-404 – Oracle Communications Session Border Controller 7 Basic Implementation Essentials Practice Test Question

Select all that apply, then click Submit answer.

• ○

  It is necessary to locate the SIP session to troubleshoot and check if there is a 404 Routes Not Found SIP error message.

• ○

  It is recommended to look for 183 Session Progress SIP error messages that indicate routing issues.

• ○

  It is recommended to check the called number by looking at the Request-URI of the INVITE message and making sure it is a valid number to be routed.

• ○

  It is recommended to find the CANCEL method received by the Session Border Controller which typically identifies a SIP routing issue.

• ○

  It is necessary to find an initial INVITE received by the Session Border Controller which gets a 503 Service Unavailable SIP error message.
  

Select all that apply, then click Submit answer.

• ○

  It can only have one steering pool port per realm.

• ○

  It is a layer 3 abstraction of a VoIP network.

• ○

  It is a logical definition of a network or group of networks comprising devices that provide real-time communication.

• ○

  It is a layer 5 abstraction of a VoIP network.

• ○

  It is a collection of IP devices that perform IP routing functions.
  

Select all that apply, then click Submit answer.

• ○

  SIP does not provide for resource reservation.

• ○

  SIP defines native methods for negotiating media streams.

• ○

  A SIP transaction occurs between a client and a server.

• ○

  To set up a voice session, SIP relies on protocols such as SDP and RTP.

• ○

  SIP signaling can only be used for voice over IP thereby limiting its use as a general signaling protocol.
  

Select all that apply, then click Submit answer.

• ○

  Egress realm can be any, depending on time-of-day, called number, and so on.

• ○

  Dynamic realm bridging is the routing of a signaling message coming from a given ingress realm to a next hop in an egress realm.

• ○

  Dynamic realm bridging is a one-to-one association accomplished by using SIP-NAT.

• ○

  Ingress and egress realms are unconditionally paired.

• ○

  Dynamic realm bridging decisions are based solely on layer 3 (IP) information.
  

Select all that apply, then click Submit answer.

• ○

  Navigate to the media-manager configuration branch and configure the realm-config configuration element.

• ○

  Navigate to the session-router configuration branch and configure the sipd-address configuration element.

• ○

  Navigate to the session-router configuration branch and configure the local-policy configuration element.

• ○

  Navigate to the session-router configuration branch and configure the sip-nat configuration element.

• ○

  Navigate to the media-manager configuration branch and configure the access-control configuration element.
  

Select an option, then click Submit answer.

• ○

  Secondary only

• ○

  Active node that no longer has a heartbeat

• ○

  Standby only

• ○

  Active only

• ○

  Standby or Active
  

Select an option, then click Submit answer.

• ○

  You are creating a sip-port element with the same address parameter value of another sip-port.

• ○

  You are creating a sip-port element with the same port parameter value of another sip-port.

• ○

  You are creating a sip-port element with the same transport-protocol parameter value of another sip-port.

• ○

  You are creating a sip-interface element with the same realm-id parameter value of another sip-interface.

• ○

  You are creating a sip-interface element with a different realm-id parameter value of another sip-interface.
  

Select an option, then click Submit answer.

• ○

  the IP utility address and its virtual MAC address

• ○

  the virtual IP address and its hardcoded MAC address

• ○

  the IP utility address and its hardcoded MAC address

• ○

  the virtual IP address and its virtual MAC address

• ○

  the IP utility address and the MAC utility address
  

Select an option, then click Submit answer.

• ○

  the Session Border Controller will never use the SIP-NAT mechanism for routing

• ○

  the Session Border Controller will not use the registration cache for routing

• ○

  all endpoints in the realm will be cached when registered

• ○

  only endpoints behind NAT in the realm will be cached when registered

• ○

  the Session Border Controller will never use the local-policy mechanism for routing
  

Select an option, then click Submit answer.

• ○

  The default community strings are acme and packet.

• ○

  The default community strings are public and private.

• ○

  Community strings are in passive mode.

• ○

  There are no default community strings.

• ○

  Only one trap receiver can be configured.