Hunt Group configured with REX still trying Rainbow Client even when the rainbow agent is logged off

Follow

Karthick D

• May 07, 2020 03:36
• Edited

In a OXE cyclic hunt group with 1 IP phone and 1 Remote Extension (Rainbow Client) in it.  When the Rainbow client is logged out, the hunt group still tries to ring the client.  We can see in the SIP trace the OXE making a call towards the WebRTC GW and the WebRTC GW replies with 180 ringing.  After the rotation timer expires, the call does move onto the IP Phone but then tries the Rainbow client again after the IP phone has been rung for the timer length.  Shouldn't the OXE be seeing the Rainbow client (remote extension) as out of service and not try to ring it. 

Is there a way to stop ringing at REX until it is logged in again?

0

• 

  Claire DECHRISTE

  • May 07, 2020 09:21

  Hello,

  You can use parameter RINGINGAUTO="false" on the WebRTC GW:

  mpconfig --RINGINGAUTO=[true|false]
  true (default value): Ringback tone is played when calling a disconnected device.
  false: The call will be hung up when a disconnected device is called.

  Available since: OXE m340230 and WebRTCGateway 1.73.14

  Regards

  Claire Dechristé

  1

  Comment actions Permalink
• 

  Karthick D

  • May 13, 2020 00:39

  Hello Claire,

  This parameter change is helpful as expected.

  OXE is now getting "480 Temporarily unavailable" message from WebRTC and the call stays with the first extension of the huntgroup.

  Thank you!

  0

  Comment actions Permalink
• 

  Subramani Boobalan

  • June 04, 2020 06:41
  • Edited

  Hello Claire,

  After RINGINGAUTO="false" on the WebRTC, it leads to High utilization issue on OXE.

  If the call arrives to hunt group where all the 4 REX users are logged off, still WebRTC responds “486 busy here” for one complete cycle of hunt but it does not stop with that.
  I.e the hunting continues in this condition like a loop then leads to High utilization.

  Parameter Available since: OXE m340230 m450112 and WebRTCGateway 1.73.14

  Customer is in OXE: M4.501.12.a & WebRTCGateway 1.74.16

  0

  Comment actions Permalink
• 

  Claire DECHRISTE

  • June 05, 2020 07:30

  Hello Boobalan,

  Please open a SR on OXE side so that the problem can be analyzed.

  Regards,

  Claire

  0

  Comment actions Permalink
• 

  Subramani Boobalan

  • June 06, 2020 06:02

  Ok, Thank you.

  0

  Comment actions Permalink

Please sign in to leave a comment.