Communication setup time

Répondu

S’abonner

Caroline CONNAN

• 9 janvier 2025 11:37

Hi all,

We are currently experiencing the following problem within the company: sometimes the time to establish communication on rainbow is quite long (about fifteen seconds) while the physical phone rings immediately. Sometimes also when you pick up via Rainbow, you have to wait about fifteen seconds before you can hear your interlocutor. We also recently had the "congestion" message on the call pop up.
With wireshark records, we can see by filtering with the SIP protocol that the session establishment times are sometimes abnormally long but without understanding why.
The computers are connected by wire, the throughput is sufficient, and the average delta, average jitter readings are well within the recommended ranges.
The only "anomaly" noted is an update pending on the RTC gateway.

Do you have any idea what could cause these random delays? Is this an internal communication problem between the gatewayRTC and the rainbow module or between our internal network and the external network (I'm thinking of the firewall for example)?

Thanks for your help,

Regards,

--------------------------------

Bonjour à tous,

Nous rencontrons actuellement le problème suivant au sein de l'entreprise : parfois le temps d'établissement de la communication sur rainbow est assez long (une quinzaine de secondes) alors que le téléphone physique sonne immédiatement. Parfois aussi lorsque l'on décroche via Rainbow, il faut attendre une quinzaine de secondes avant de pouvoir entendre son interlocuteur. Nous avons également eu récemment le message "congestion" sur le pop-up d'appel qui apparaissait.
Avec des enregistrements wireshark, on voit en filtrant le protocole SIP que les temps d'établissement de session sont parfois anormalement longs mais sans comprendre pourquoi.
Les ordinateurs sont connectés en filaire, le débit est suffisant, et les valeurs moyennes de delta et de gigue sont largement dans les plages recommandées.
La seule "anomalie" relevée est une mise à jour en attente sur la GatewayRTC

Avez-vous une idée de ce qui pourrait provoquer ces délais aléatoires ? Est-ce un problème interne de communication entre la gatewayRTC et le module rainbow ou entre notre réseau interne et l'extérieur (je pense au pare-feu par exemple) ?

Merci pour votre aide,

Cordialement,

 

0

• Commentaire officiel

  

  Baptiste CANDELIER

  • 27 janvier 2025 08:02

  Hello Caroline, 

  in addition to Fazal's answer, you can try our Rainbow Pilot tool which can give you some hints about connectivity issues. 

  In any case, I recommend that you contact your Rainbow reseller who can open a support ticket for you to move forward with the analysis.

  Regards,
  Baptiste
  Rainbow Customer Care Team

  Actions pour les commentaires Permalien
• 

  Fazal ABIBULLA

  • 21 janvier 2025 09:51
  • Modifié

  Hi Caroline, Hope you are doing great!

  The issue may potentially be caused by,

  Analyze SIP Signaling Delays:

  The delayed session establishment observed in Wireshark suggests a potential issue with SIP signaling. Common causes include:

  Network latency or packet loss.
  Overloaded or misconfigured SIP servers.
  Delays in DNS resolution if SIP requests rely on domain names.
  
  Inspect Rainbow WebRTC Gateway Performance:
  Verify if the WebRTC gateway is experiencing high CPU or memory usage, as this can lead to call handling delays.
  Ensure that the gateway's network connectivity is stable, with sufficient bandwidth.
  
  Check PBX and SIP Trunk Settings:
  Confirm that the PBX system is handling SIP requests efficiently.
  Ensure proper configuration of SIP trunks and no overloads or congestion during peak times.
  
  Firewall and QoS:
  Review firewall rules to ensure no delays are introduced by inspection or filtering.
  Audio Delay:

  The 15-second delay in audio upon answering could be due to media path establishment issues.

  Verify:

  STUN/TURN server accessibility for WebRTC.
  Proper NAT traversal settings for Rainbow clients and the WebRTC gateway.

  We recommend creating a Service Request (SR) on support.openrainbow.com, including the relevant logs and Wireshark captures, so we can analyze the issue further.
  
  Thanks & Regards,
  Fazal (Rainbow TAC support)

  0

  Actions pour les commentaires Permalien
• 

  Caroline CONNAN

  • 27 janvier 2025 08:18

  Hello Fazal, Baptiste,

  Thanks for your support and tips, I'm goint to try Rainbow Pilot tool and check the elements above. I'll make open a ticket is I need further analysis.

  Have a good day !

  0

  Actions pour les commentaires Permalien

Vous devez vous connecter pour laisser un commentaire.