After upgrade the webrtc, call from OXE to rainbow the call present no audio.

Beantwortet

Folgen

Guilherme De Moura

• 19. März 2025 20:15

After upgrade the webrtc, call from OXE to rainbow the call present no audio.

Incoming calls are silent after updating WebRTC to 3.0.13-191

WebRTC in version 2.4.7-708 does not have the issue.

OXE Hybrid Scenario with WebRTC.

After we upgrade the webrtc we observed the issue below.

when call from OXE to rainbow the call present no audio, looking on tcpdump captured on rainbow I could see the rainbow send the origin as a wrong IP 1.1.1.1

SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.31.0.200;rport=5060;branch=z9hG4bK801fb8f64dfa87da7a951f015709db6f
Record-Route:
From: ;tag=a300371350561788265c1f007d52321b
To: ;tag=4rZeBt5rU8D5H
Call-ID: a8a026b75d28d7f922b9d952335f573b@172.31.0.200
CSeq: 104715232 INVITE
Contact: WRG
User-Agent: Rainbow WebRTC Gateway 3.0.13-191
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, UPDATE, REFER, MESSAGE, INFO, NOTIFY
Supported: replaces
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 184
P-Asserted-Identity: "Guilherme De Moura"

v=0
o=- 1923518516 2 IN IP4 1.1.1.1
s=-
t=0 0
m=audio 38142 RTP/AVP 8 0 101
c=IN IP4 172.16.10.221
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000

During the issue if force a renegotiation the webrtc sends correct origin and contact.

I attached the logs and trace in the case.
Workaround was downgrade the version.

 

 

Best Regards

0

• Offizieller Kommentar

  

  Baptiste CANDELIER

  • 19. März 2025 20:46

  Hi Guilherme,

  From your description it may be linked to an issue that is fixed with next version 3.0.14 that will be available this Thursday.
  You may confirm the issue is the same if you have in the network some firewall having SIP-ALG active.
  Different option deactivate the SIP-ALG feature or downgrade to 2.4.7 and install 3.0.14 as soon as it is available for you (should be available on MyPortal at 5:00 pm CES)

  In case you still have the issue after upgrade to 3.0.14 then you have to open a support ticket so we can have a deeper analysis.

  Regards,
  Baptiste
  Rainbow Customer Care Team

  Aktionen für Kommentare Permalink
• 

  Guilherme De Moura

  • 24. März 2025 14:31

  Hi Baptiste,
  I updated to the new version 3.0.14-203 and it fixed the problem.
  
  Thank you very much,
  Guilherme De Moura.

  0

  Aktionen für Kommentare Permalink
• 

  Calebe Assis

  • 24. März 2025 18:34

  Hi Baptiste,

  Could you detail the issue and what was the trigger for that?

  Thanks for your support.

   

  Best Regards,

  Calebe Assis

   

  0

  Aktionen für Kommentare Permalink

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.