1 <?xml version=
"1.0" encoding=
"ISO-8859-1"?>
2 <rss version='
2.0' xmlns:lj='http://www.livejournal.org/rss/lj/
1.0/'
>
4 <title>Petter Reinholdtsen - Entries from May
2020</title>
5 <description>Entries from May
2020</description>
6 <link>http://people.skolelinux.org/pere/blog/
</link>
10 <title>Jami as a Zoom client, a trick for password protected rooms...
</title>
11 <link>http://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html
</guid>
13 <pubDate>Fri,
8 May
2020 13:
30:
00 +
0200</pubDate>
14 <description><p
>Half a year ago,
15 <a href=
"http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html
">I
16 wrote
</a
> about
<a href=
"https://jami.net/
">the Jami communication
17 client
</a
>, capable of peer-to-peer encrypted communication. It
18 handle both messages, audio and video. It uses distributed hash
19 tables instead of central infrastructure to connect its users to each
20 other, which in my book is a plus. I mentioned briefly that it could
21 also work as a SIP client, which came in handy when the higher
22 educational sector in Norway started to promote Zoom as its video
23 conferencing solution. I am reluctant to use the official Zoom client
24 software, due to their
<a href=
"https://zoom.us/terms
">copyright
25 license clauses
</a
> prohibiting users to reverse engineer (for example
26 to check the security) and benchmark it, and thus prefer to connect to
27 Zoom meetings with free software clients.
</p
>
29 <p
>Jami worked OK as a SIP client to Zoom as long as there was no
30 password set on the room. The Jami daemon leak memory like crazy
31 (approximately
1 GiB a minute) when I am connected to the video
32 conference, so I had to restart the client every
7-
10 minutes, which
33 is not a great. I tried to get other SIP Linux clients to work
34 without success, so I decided I would have to live with this wart
35 until someone managed to fix the leak in the dring code base. But
36 another problem showed up once the rooms were password protected. I
37 could not get my dial tone signaling through from Jami to Zoom, and
38 dial tone signaling is used to enter the password when connecting to
39 Zoom. I tried a lot of different permutations with my Jami and
40 Asterisk setup to try to figure out why the signaling did not get
41 through, only to finally discover that the fundamental problem seem to
42 be that Zoom is simply not able to receive dial tone signaling when
43 connecting via SIP. There seem to be nothing wrong with the Jami and
44 Asterisk end, it is simply broken in the Zoom end. I got help from a
45 very skilled VoIP engineer figuring out this last part. And being a
46 very skilled engineer, he was also able to locate a solution for me.
47 Or to be exact, a workaround that solve my initial problem of
48 connecting to password protected Zoom rooms using Jami.
</p
>
50 <p
>So, how do you do this, I am sure you are wondering by now. The
52 <a href=
"https://support.zoom.us/hc/en-us/articles/
202405539-H-
323-SIP-Room-Connector-Dial-Strings#sip
">documented
53 from Zoom
</a
>, and it is to modify the SIP address to include the room
54 password. What is most surprising about this is that the
55 automatically generated email from Zoom with instructions on how to
56 connect via SIP do not mention this. The SIP address to use normally
57 consist of the room ID (a number), an @ character and the IP address
58 of the Zoom SIP gateway. But Zoom understand a lot more than just the
59 room ID in front of the at sign. The format is
"<tt
>[Meeting
60 ID].[Password].[Layout].[Host Key]
</tt
>", and you can hear see how you
61 can both enter password, control the layout (full screen, active
62 presence and gallery) and specify the host key to start the meeting.
63 The full SIP address entered into Jami to provide the password will
64 then look like this (all using made up numbers):
</p
>
66 <p
><blockquote
>
67 <tt
>sip:
657837644.522827@
192.168.169.170</tt
>
68 </blockquote
></p
>
70 <p
>Now if only jami would reduce its memory usage, I could even
71 recommend this setup to others. :)
</p
>
73 <p
>As usual, if you use Bitcoin and want to show your support of my
74 activities, please send Bitcoin donations to my address
75 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>