Multi-Hop Agent Ping

The Oracle Enterprise Communications Broker (OECB) ping function can test connectivity to endpoints that are not directly adjacent to the source OECB. This multi-hop ping capability requires that you configure special routes dedicated to sending SIP options pings to these targets.

To enable ping tests to targets that are more than one hop from the OECB, configure routes that have the string "ping:" in the Called number field. These routes also have a first agent towards the target configured in the Route field, and the last agent toward the target configured in the Destination Agent field.

The system invokes these ping: routes for ping traffic only. In addition, the system prioritizes SIP signaling traffic over ping: route traffic.

The following table shows an example of a multi-hop ping route.

Source Agent	Calling Number	Destination Agent	Called Number	Route	Cost	Policy
*	*	Target_Agnt	ping:	Adja_Agnt	0

Having configured this route, you can initiate a ping to a target, or configure agent pinging to Target_Agnt by way of Adja_Agnt.

You can also set up multi-hop ping recursion by creating multiple ping: routes that specify the complete path to the target. To create these paths, you can configure ping: routes using the Destination Agent and Route fields to define each hop in a "ping path".

Based on the two route entries in the following example, ping attempts to reach the device defined as Target_Agnt follow a two-hop path:

1. OECB to Adja_Agnt
2. Adja_Agnt to Interim_Agnt
3. Interim_Agnt to Target_Agnt

Source Agent	Calling Number	Destination Agent	Called Number	Route	Cost	Policy
*	*	Interim_Agnt	ping:	Adja_Agnt	0
*	*	Target_Agnt	ping:	Interim_Agnt	0

The OECB uses an agent status, determined by OPTIONS ping, to validate all routes using that agent. Specifying an agent's status, including in-service and out-of-service, is the same for agents using either single or multi-hop ping. The system does not use routes to out-of-service agents for any signaling traffic.