Menu

#273 "Unable to resolve DNS SRV record" error when joining conference

OBSOLETE_(1.18.x)
closed-works-for-me
None
Protocol/Other
5
2016-04-23
2014-11-14
No

After upgrading to version 1.18.4 my conference links stopped working because of bug fix [#245]. Out company is using four "name parts" in https links but only two are used in sip ID:

https://server.sub.domain.com/meet/first.last/HBG846J5
sip:first.last@domain.com;gruu;opaque=app:conf:focus🆔HBG846J5

With [#245] fixed, it is now

sip:first.last@sub.domain.com;gruu;opaque=app:conf:focus🆔HBG846J5

which leads to "Unable to resolve DNS SRV record".

I can "fix" that by reverting git commit b09ab4b but it will revive the original bug.

Could it be possible to read the URL from HTML obtained from original http(s) link? It's there on several places, although encoded in various forms.

Related

Bugs: #245
Feature Requests: #82

Discussion

  • Martin Frydl

    Martin Frydl - 2014-11-14

    I've created a simple patch not fixing the issue but allowing conference links in format sip:... or conf:sip:... instead of just http(s)://. This could be used as workaround if translation from http to sip does not work. User can find the correct sip link in HTML obtained from http(s) URL and use it directly.

     
  • Stefan Becker

    Stefan Becker - 2014-12-05

    Unfortunately your patch is a no-op, because "sip:" and "conf:sip:" are already matched by parse_ocs_focus_uri() in

    :::c
    focus_uri = parse_ocs_focus_uri(uri_ue);
    if (!focus_uri) {
        focus_uri = parse_lync_join_url(uri_ue);
    }
    

    So the only thing I could "fix" would be to add that "sip:" is also accepted to the dialog text in sipe_purple_show_join_conference().

     
  • Stefan Becker

    Stefan Becker - 2014-12-07
    • status: open --> closed-works-for-me
    • assigned_to: Stefan Becker
     
  • Stefan Becker

    Stefan Becker - 2014-12-07

    Verified that sip:... and conf:sip: are already processed correctly by the current code. Therefore no changes are required.

    Added the error message and what to do about it to the FAQ

    Closing as WORKSFORME

     

Log in to post a comment.

MongoDB Logo MongoDB