Created by Unknown User (johnny.widen@ltu.se), last modified on Mar 17, 2010
Category
General
Description
-- We need to over this. Jan will test
Status
No labels
1 Comment
Unknown User (matjaz.batic@arnes.si)
As SIP integration I had in mind an SIP/H.323 compatibility
to have the ability to make 1 H.323 call in a meeting, so we could bridge those two worlds. (Proubably there is a server limit due to CPU)
(similar functionaliuty as EVO has)
If you are in a meeting you can call using SIP, or H.323 and then
-all users in H.323 see all AC cameras as 1 H.323 user
-all H.323 users are in AC seen as 1 AC camera
-host sets what is sent back from AC to H.323 (all cameras withouth incoming H323 stream, all cameras, content )
-host sets what is sent back as content H.239 (which share pod is sending the shared stuff to the H.323, recieving H.239 into share pod is an overkill)
1 Comment
Unknown User (matjaz.batic@arnes.si)
As SIP integration I had in mind an SIP/H.323 compatibility
to have the ability to make 1 H.323 call in a meeting, so we could bridge those two worlds. (Proubably there is a server limit due to CPU)
(similar functionaliuty as EVO has)
If you are in a meeting you can call using SIP, or H.323 and then
-all users in H.323 see all AC cameras as 1 H.323 user
-all H.323 users are in AC seen as 1 AC camera
-host sets what is sent back from AC to H.323 (all cameras withouth incoming H323 stream, all cameras, content )
-host sets what is sent back as content H.239 (which share pod is sending the shared stuff to the H.323, recieving H.239 into share pod is an overkill)