Re: [GnomeMeeting-list] newby question. Problem behind a NAT


I felt myself  in that problem as you are, and believe me it has less to do with STUN or whatever NAT config you have and more about your sound configuration.

I'm using gnome desktop, a 2.6.15 kernel with a compiled in intel8x0 sound device and a philips usb webcam with its own microphone.

I linked the sound card directly in the kernel and not as a module but you could change that and uncomment the snd-card-0 alias in the  alsa file below.

I'm using  alsa -1.0.11_rc3 driver and i don't use dbus with gnomemeeting (the dbus version i have isn't compatible wih it)

Modify your /etc/asound.conf as below:

pcm.snd_card {
     type hw
     card 0
     device 0

pcm.snd_usb {
     type hw
     card 2
     device 1

ctl.snd_usb {
     type hw
     card 2
     device 1

depending your linux distribution the /etc/alsa/module.d/alsa  or the modprobe.conf file needs to look like this:

##  ALSA portion
#alias snd-card-0 snd-intel8x0
alias snd-card-1 snd-mpu401
alias snd-card-2 snd-usb-audio

options snd-intel8x0 index=0
options snd-mpu401 index=1
options snd-usb-audio index=2

#options snd-pcm-oss adsp_map=1
##  OSS/Free portion
alias sound-slot-0 snd-intel8x0
alias sound-slot-1 snd-mpu401
alias sound-slot-2 snd-usb-audio
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss

# OSS/Free portion - card #1
alias sound-service-1-0 snd-mixer-oss
alias sound-service-1-1 snd-seq-oss
alias sound-service-1-3 snd-pcm-oss
alias sound-service-1-8 snd-seq-oss
alias sound-service-1-12 snd-pcm-oss
##  OSS/Free portion - card #2
alias sound-service-2-0 snd-mixer-oss
alias sound-service-2-3 snd-pcm-oss
alias sound-service-2-12 snd-pcm-oss

alias /dev/mixer snd-mixer-oss
alias /dev/dsp snd-pcm-oss
alias /dev/midi snd-seq-oss

# Set this to the correct number of cards.
options snd cards_limit=5

Why cards_limit=5 when i have only 3 "cards" and 2 devices ? Don't know i'm lazy to change that ;)

Now modify gnome audio configuration for alsasink as your output and alsa_src device=snd_usb as your input (necessary for the usb microphone!). You can check them in the gnome menu as well.

I don't use esd daemon at boot time but only on demand. So deactivate esd in you init script and do a /etc/init.d/esd stop to be sure it is not running. To have some sounds in gnome when you open a window you need to activate the esd sound service in the sound preferences menu.

Be aware, gnomemeeting wizard  won't work properly with the gnome sound activated. It cannot open the usb sound device, but that doesn't harm gnomemeeting functionality either. Only you will not be able to check it with the gnomemeeting wizard.

Your /etc/esd/esd.conf should look like this:

spawn_options=-terminate -nobeeps -as 2
# default options are used in spawned and non-spawned mode

If really nothing works, alter temporally your gnomemeeting 1.2.3 NAT parameters configuration and see if it works better:

IP translation = no                     <-- that depend your router: works better like that for me.
Automatic IP verification = no  <-- i don't know if that is related with theILS server disponibility but it seems more often down as working :(, so i deactivated it.

Public IP address : copy your internet address IP here, not the lan one.

STUN = yes

and somewhere in the H323 menu,

activate H245 tunnelling.

Your NAT router needs also to forward some ports to your gnomemeeting computer:

TCP 1720
UDP 5000-5016

You need nothing more if you don't want to be reached by someone using netmeeting.

As remark,  you should see cone NAT and the video and audio codecs used in your gnomemeeting history window (Tools menu i guess). To ease the debugging, compile gnomemeeting with DEBUG option ;) If you don't see audio and video activities in the gnomemeeting window you are still in trouble :(

Hope that help


Andreas Fromm a écrit :
First of all, hi to everybody.

I just started to play a bit with gnomemeeting as I got myself a Webcam
an want to videochat with my brother. We are both running gnomemeeting
(1.2.3) from debian/testing. Both of us are behind a DSL/Cable Router
with portforwarding for ports tcp:1720, udp:5000-5016 and
tcp:30000-30010. The problem we ar getting is that we can make and
receive calls, have text chats, but no sound nor video is transmittet.
The calls get killed after the timeout for inactive calls, unless we
turn off that feature. Our webcams and sound configuration seem to be
working all right (we can see ourselfs on our local windows) and the
comunication between two of my computers at home work all right, so I
think it's a NAT problem we are having here, but I don't know what else
to do. I allready looked at the FAQ and searched the mailing list, but
couldn't get any thing usefull. We also tryed out different NAT
settings, with and without stun enabled, using automatic IP checking etc.

I hope someone can halpe me!

thanks in advance

GnomeMeeting-list mailing list
GnomeMeeting-list gnome org


            |\      _,,,---,,_
      ZZZzz /,`.-'`'    -.  ;-;;,_
           |,4-  ) )-,_. ,\ (  `'-'
          '---''(_/--'  `-'\_)

My VoIP call number 661401

My Two Cents Comment
Van Roy's Law: Honesty is the best policy - there's less competition. Van Roy's Truism: Life is a whole series of circumstances beyond your control.

            |\      _,,,---,,_
      ZZZzz /,`.-'`'    -.  ;-;;,_
           |,4-  ) )-,_. ,\ (  `'-'
          '---''(_/--'  `-'\_)

My VoIP call number 661401

My Two Cents Comment
Hmmm ... A hash-singer and a cross-eyed guy were SLEEPING on a deserted island, when ...

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]