IP shuffling is the ability to set up a call path between two IP endpoints by rerouting the voice channel away from the usual TDM bus connection and creating a direct IP-to-IP connection. IP shuffling saves resources like TDM bus time slots and media channels and improve voice quality by eliminating unnecessary codec conversions. To enable IP shuffling there must be at least one common codec between the two point-to-point IP endpoints.[1]

IP shuffling can take place not only inside of a system but also between multiple systems. This ability is particularly useful in a multi site call center environment where customer calls can be transferred from one person to another multiple times within the same transaction. IP shuffling will tear down each call leg and re-establish a point-to-point connection with the new calling party each time the call gets transferred, saving valuable system resources.[2]

IP Shuffling across systems edit

 
IP Shuffling between two call centers

IP shuffling is particularly useful in a multi call center environment. In this example, the customer establishes a call to a call center in Berlin, Germany.

  1. The caller is placed in a music queue as no customer service consultant is available at this time. While the customer is queuing, a service consultant becomes available in the Cape Town, South African call center.
  2. Should IP shuffling not be enabled, the call would be hair-pinning or tromboning through the Berlin call center to Cape Town, utilizing valuable Berlin media processing resources for the duration of the call.
  3. With IP shuffling enabled the call leg between the customer and the Berlin call center is torn down and a direct connection to the IP agent sitting in Cape Town is established using IP shuffling.

References edit

  1. ^ "Administration for Network Connectivity for Avaya Communication Manager" (PDF). 555-233-504 (12). February 2007: 166–167. Retrieved 30 October 2012. {{cite journal}}: Cite journal requires |journal= (help) [failed verification]
  2. ^ Coffman, Jim (December 2001). "Finding new ways to conserve IP voice network resources" (PDF): 2–3. Archived from the original (PDF) on 15 November 2012. Retrieved 30 October 2012. {{cite journal}}: Cite journal requires |journal= (help)