[x3d-public] Fw: Wg: The Society: let me not forget for SIP

Fri Feb 2 06:01:22 PST 2024

Dear all,

fyi.

I felt free to store this information (see the mails below) for later use, at our association's web site.

https://lc-soc-lc.or.at/sub-topic-001-smuos/vision.htm

Have a nice week
CP/V 

Gesendet: Dienstag, 30. Januar 2024 um 22:04 Uhr
Von: "Christoph Valentin via x3d-public" <x3d-public at web3d.org>
An: x3d-public at web3d.org
Cc: "Christoph Valentin" <christoph.valentin at gmx.at>
Betreff: [x3d-public] Wg: Fw: The Society: let me not forget for SIP

Please read the mail below........

Kind regards,
CP/V

--
Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.
Am 30.01.24, 20:30 schrieb Christoph Valentin <christoph.valentin at gmx.at>:

fyi.......

Comments not requested, but also not un-welcome...........

Gesendet: Dienstag, 30. Januar 2024 um 20:12 Uhr
Von: "Christoph Valentin" <christoph.valentin at gmx.at>
An: "Christoph" <christoph.valentin at gmx.at>
Cc: "Markus Sonntag" <mail at markus-sonntag.at>, "Kevin" <klw71 at yahoo.com>, "r.onickabsi.at" <r.onic at kabsi.at>, "John Carlson" <yottzumm at gmail.com>, "John R" <warthogale at aol.com>
Betreff: Fw: The Society: let me not forget for SIP

Hi Kevin,

I felt free to write down a few initial considerations -> please have a look to the attached text file.............

All this is just a preparation to maybe have a short chat at our next meeting of "The Society".

Also, I tried to do a "one man brain storming" (silly :-) ) and compiled a set of use cases for the far-end goals of "Simple Multiuser Scenes (SMS)" (being aware of the fact that I am again inventing the weel another time :-) )

Roles: Author, Controller, Player, Combined Roles
● Use Cases for the Author
● 1) create MU session (create content on server)
● 2) delete inactive MU session (delete content from server)
● 3) force delete active MU session (delete content + abort session)
● 4) update MU session (update content on server)
● 5) force update active MU session (upd. content + rejoin all participants)
● Use Cases for the Trainer = Controller
● 11) schedule MU session (create SDP[ + configure auto activation])
● 12) activate MU session (with or without invitation of participants)
● 13) pause/resume active MU session [ + embedded voice chat lesson]
● 15) deactivate/abort MU session
● Use Cases for the Trainee = Player
● 21) join MU session [ + implicit activation]
● 22) pause/resume participation (afk)
● 24) leave MU session
● 25) invite another participant
● 26) adapt rooms during active session
● Passive Use Cases (being notified about session related events)
● 90) Notify author about session/room statistics
● 91) Notify controller about session events
● 92) Notify player about session events

Kr,
CP/V

Gesendet: Samstag, 27. Januar 2024 um 00:46 Uhr
Von: "Christoph Valentin" <christoph.valentin at gmx.at>
An: "Christoph" <christoph.valentin at gmx.at>
Cc: "Markus Sonntag" <mail at markus-sonntag.at>, "Kevin" <klw71 at yahoo.com>, "r.onickabsi.at" <r.onic at kabsi.at>, "John Carlson" <yottzumm at gmail.com>, "John R" <warthogale at aol.com>
Betreff: The Society: let me not forget for SIP

Hi Christoph,

Well, the first step of our activities at "The Society", is for sure to learn a little bit about IEEE DIS.

DIS comes with the use of IP multicast addresses. It is a very simple form of networking.

Nevertheless, DIS is an international standard, as X3D is an international standard (ISO).

So DIS and X3D fit very well together. However, DIS is rather old, maybe already outdated. I heard, it is still widely used for military applications.

Second step will be / could be, to combine DIS with SIP. This week, I had some reading of RFC 3261. It seems, the use of multicast addresses could be the origin of SIP - I will describe this theory in a little paper soon.

So we should implement a very simple SIP client that interfaces with FreeWrl - better: can we use some existing SIP client? The goal of "The Society" is not to implement anything, but to test 3rd party software. Only, if we need something very special to test something else, then we will implement something.

First step: no REGISTER, only INVITE, no SIP server at all, INVITE is directly sent from SIP client to mcast address 239.255.x.x (this mcast address must be input by the user) and all clients answer with 200 OK. ACK is sent to each client via unicast address from Contact header field. No provisional responses. Only 200 OK as possible answer (or no answer at all). ACK. BYE. Contact header field holds name of the user plus the unicast address of the client. Question: how to describe DIS session in SDP?

Second step: simple kamailio server (new element) listens to mcast address 224.0.1.75 "all SIP servers". Answers with 302 Redirect (redirects to 239.255.x.x multicast address). Client calls a "room name" with Request-URI = sip:room-name at 224.0.1.75; mapping from room name to mcast address 239.255.x.x is configured at the kamailio server.

Third step: some kind of "admin" must authenticate at kamailio an can then register a 239.255.x.x address for the name of a "chat room" dynamically (mapping need not be configured at the kamailio server). Client sends INVITE to sip:room-name at 224.0.1.75

The "far-end" goal is an interworking between DIS and the BS Contact Network Sensor (which is a more recent networking technology), or even between DIS and a "HTML based" (WebGL) experimental network sensor (WebRTC based).

Sounds like a complete plan for my retirement, even for the rest of my life

Have a nice week

CP/V_______________________________________________ x3d-public mailing list x3d-public at web3d.org http://web3d.org/mailman/listinfo/x3d-public_web3d.org