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

[Martin Wilck]

After trying to join a conference, I get an "Unable to resolve DNS SRV record" error.

The problem seems to be caused in parse_lync_join_url by ignoring subdomains.

Our account names have the form "my.name@ts.fujitsu.com", but parse_lync_join_url transforms this to "my.name@fujitsu.com" for the inviting party, and the server can't resolve this person, causing the error.

Log files are attached.

[Martin Wilck]

Here is a very clumsy patch that actually solves this problem.
You can certainly write it better. I am not familiar with the glib functions.

[Stefan Becker]

Sorry, but your patch would break if for everybody else. I.e. for them my.name@sub.domain.com needs to be mapped to sip:organizer@domain.com;gruu;opaque....

Jakub: I'm not sure how to fix this. Use the focus URI as a template? The log shows that in his case it has the full domain ts.fujitsu.com

[Stefan Becker]

@reporter: the log doesn't show the meeting location URL. Can you please copy & paste it here?

[Martin Wilck]

https://lync.ts.fujitsu.com/Meet/gerhard.wichert/T4LFTMC3

[Stefan Becker]

Thanks.

Your problem should be fixed by git commit b09ab4b.

Closing as FIXED.

[Martin Wilck]

Thanks a lot for your quick action. Fixed the bug in less than an hour. I am very impressed.

[Martin Wilck]

Ah, btw I forgot to say that I verified git commit b09ab4b as the solution.

[Nelson Chan]

I am using pidgin 2.10.9 with sipe 1.18.5 in ubuntu 14.10. I still experience the same issue when I join a conference.

Attached the debug log for troubleshooting.

[Stefan Becker]

Please read the FAQ entry for this error message.

[Nelson Chan]

Thanks for the direction Stefan. I am able to attend a conference call after I translate the URI manually.

Is there a script handy to translate the URI? I need to attend many conference calls every day and manual translation is time consuming.

[Martin Wilck]

Reading the FAQ, a generic solution should be possible.

A) a config option somewhere telling SIPE how many host name parts to strip.
B) a trial-and-error approach trying to strip one part after the other until the SRV lookup succeeds for:

1. _sipinternaltls._tcp.pc.sub.domain.com
2. _sipinternaltls._tcp.sub.domain.com
3. _sipinternaltls._tcp.domain.com
4. _sipinternaltls._tcp.com (well, hm ...)

[Stefan Becker]

(A) configuration options are a bad idea as users never understand them and only lead to incorrect "this is how I fixed it" blog entries.

(B) those DNS SRV records will deliver incorrect result, i.e. the OCS server. This has nothing to do with the conference server.

I've filed [feature-requests:#82] with a potential idea. But without a test account the chances of getting this implemented are slim. None of my test accounts offers public conferences. It's anyway too late for 1.19.0.

[Nelson Chan]

What kind of testing do you need to perform? I may be able to offer some help. This feature is useful for me.

[Stefan Becker]

Please move all further discussion to [feature-requests:#82]. Make sure to subscribe to that feature request to receive updates.