Shuffling an audio connection between two IP endpoints means rerouting the voice channel away from the usual TDM bus connection and creating a direct IP-to-IP connection. Shuffling saves resources such as G4xx Media Gateway or Avaya Aura® Media Server channels and improves voice quality by bypassing transcoding. Both endpoints must be capable of shuffling.
Communication Manager uses the following criteria to determine whether a shuffled audio connection is possible:
A point-to-point voice connection exists between two endpoints.
No other active call on either endpoint, including in-use or held calls, requires TDM connectivity. For example, applying tones, announcement, conferencing, and others.
The endpoints are in the same network region or in different, interconnected regions.
Both endpoints or connection segments are administered for shuffling by setting the Direct IP-IP Audio Connections field to y for shuffled IP calls to use a public IP address by default.
If the Direct IP-IP Audio Connections field is y, during registration the endpoint might indicate that it does not support audio shuffling. In this scenario, the a call cannot be shuffled. If the Direct IP-IP Audio Connections field is n, during registration the endpoint might indicate that it can support audio shuffling. The calls to that endpoint cannot be shuffled, giving precedence to the endpoint administration.
The rules for Internetwork region connection management are met.
At least one common codec is present between the endpoints involved and the Inter-network region Connection Management codec list.
The endpoints have at least one codec in common as shown in the current codec negotiations between the endpoint and the switch.
Both endpoints can connect through the same G4xx Media Gateway or Avaya Aura® Media Server.