G'day Satya

Generally speaking, the Access Grid uses the network protocol "Multicast" by 
default to enable communication between "joined" parties. 

You might find the following document http://www.accessgrid.org/firewall-doc 
useful.

I am not 100% sure whether the AG supports " Source Specific Multicast ", but I 
simply know that the AG by default uses the multicast protocol (whether this is 
Source Specific or not - I am not sure, haven't heard the use of that 
terminology much before).

In regards to your problems, I suspect that the issue is more related to audio 
device and configuration.  You could conduct some self-testing on each of your 
Access Grids to assist with trouble shooting.  I suggest you have a look at 
http://www.accessgrid.org/qa-improve, as it provides some practical examples on 
testing Access Grid systems.

Additionally, you may wish to attend the ASIA-Pacific weekly test session to 
receive feedback about your Access Grid from other AG users.  Details for the 
session are as follows:

When:           Every Monday

Time:       
                Bangkok                 8.00am
                Beijing                 9:00am
                Manila                          9.00am
                Singapore                       9.00am
                Taipei                                  9.00am
                Perth                                   9.00am
                Seoul                           10.00am
                Tokyo                           10.00am
                Brisbane                11.00am
                Adelaide                11.30am
                Canberra                12.00pm
                Hobart                          12.00pm
                Melbourne               12.00pm
                Sydney                  12.00pm
                Auckland                        2.00pm

Venue:          APAG Lobby -> AG-EVO@AU Bridge Lobby -> EVO-AG Testing Room
                
(https://130.102.78.178:8000/Venues/ac10cd0111eb76b4d3d7bb213a5aa975b) 

Version:    AG3

Additionally, some presentation material, including AG testing and network 
information can be found 
http://www.arcs.org.au/index.php/component/content/article/77-video-collaboration/390-video-collab-pres.

Anyway - I hope helps you with solving your problems.

Cheers,
Jason.


-----Original Message-----
From: ag-tech-boun...@lists.mcs.anl.gov 
[mailto:ag-tech-boun...@lists.mcs.anl.gov] On Behalf Of N. Satyanarayana
Sent: Tuesday, 1 February 2011 03:00 PM
To: ag-t...@mcs.anl.gov
Subject: [AG-TECH] Bidirectional video/audio conference problem

Hi,

We are facing problem in realizing two way interaction with Access grid.
We have a dedicated network across three different cities with multicast 
enabled in our routers. I believe each venue can be configured with only one 
multicast group ip address with separate ports for video and audio transmission.

The network provider is saying that a node cannot be source as well as receiver 
at the same time but in AG it is observed that all the hosts participating in a 
particular venue session are transmitting both audio and video. He is saying it 
is not the right way of experimenting bidirectional communication thru 
audio/video.

He is asking whether AG supports Source Specific Multicast or not, because he 
is saying bidirectional communication thru audio/video can be realized only 
thru SSM support. But i did not find any means on how to configure SSM in 
access grid. I am using AG 3.1 all in one windows installer.

Some times we are facing audio echo and some times noise problem. I am not able 
to understand whether it is because of audio devices or network configuration.

Can you throw some light on where the problem could be as we are not able to 
conclude whether it is due to network or audio devices.

Regards,
Satya
--
N. Satyanarayana
Centre for Development of Advanced Computing (C-DAC) No. 1, Shivbagh Ameerpet 
Hyderabad - 500 016

(Off) +91-40-23737124/25

http://www.cdachyd.in/econtentquality



--
This message has been scanned for viruses and dangerous content by MailScanner, 
and is believed to be clean.

Reply via email to