You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Hi, I've seen this once and dismissed as a fluke, however this weird behavior seems to persist, albeit happening not very often. Basically, I am seeing strange "xyz.local" entries in the initial set of candidates provided by the SIP.js in the first INVITE. Usually this happens just once after a fresh connection is established, and after that everything goes to normal. I've observed this with both demo-1 and demo-2 applications.
Describe the bug
Hi, I've seen this once and dismissed as a fluke, however this weird behavior seems to persist, albeit happening not very often. Basically, I am seeing strange "xyz.local" entries in the initial set of candidates provided by the SIP.js in the first INVITE. Usually this happens just once after a fresh connection is established, and after that everything goes to normal. I've observed this with both demo-1 and demo-2 applications.
Logs
To Reproduce (if possible)
Steps to reproduce the behavior:
Expected behavior
Only proper candidates should be included into the INVITE
Observed behavior
a=candidate:1774936281 1 udp 2113937151 6772ddeb-1940-4ab0-b86b-f6e6bf850c8e.local 59387 typ host generation 0 network-cost 999
Environment Information
The text was updated successfully, but these errors were encountered: