[Asterisk-video] Videomixing in MeetMe

[Pauli Østerø]

Hi Lorenzo,

Now i got the Videomixer working. Somehow the mcu-settings was defined under [general] instead of [videomixer].

But now i got another problem, but I doubt its related with Confiance. I keep getting kicked off Asterisk after about 5 seconds, and these messages appear in the CLI

[Aug 27 12:43:02] WARNING[8155]: chan_sip.c:1909 retrans_pkt: Maximum retries exceeded on transmission NWM1NzNkYmM2MGM1ZThiMmVkZGExZjQ5NmNkOGJkY2Y. for seqno 2 (Critical Response)
[Aug 27 12:43:02] WARNING[8155]: chan_sip.c:1926 retrans_pkt: Hanging up call NWM1NzNkYmM2MGM1ZThiMmVkZGExZjQ5NmNkOGJkY2Y. - no reply to our critical packet.
[Aug 27 12:43:02] WARNING[8160]: app_meetme.c:3962 conf_run: Couldn't remove UserID 1 from local Conference 8671000 Users' list...
    -- Remote Users removed from Conference 8671000 Users' list...
    -- The Conference 8671000 has been deleted from the BFCP Server.
    --  VideoMixer RTP-Listener (34) for ConferenceID 8671000 stopped
    -- Hungup 'Zap/pseudo-1745540256'
  == Spawn extension (video, 8671000, 1) exited non-zero on 'SIP/10002-081cffd0'
    -- Executing [h at video:1] Hangup("SIP/10002-081cffd0", "") in new stack
  == Spawn extension (video, h, 1) exited non-zero on 'SIP/10002-081cffd0'
    -- Saved useragent "eyeBeam release 1010f stamp 39239" for peer 10002

I've been searching all over for the "no reply to our critical packet"-error, but all the answers seems to be related to some kind of NAT problems. The thing is, that the server and clients are all sitting on the same class C network with no NAT or firewalls blocking.

Best regards,
Pauli

-----Original Message-----
From: Lorenzo Miniero [mailto:lorenzo.miniero at unina.it] 
Sent: 24. august 2007 16:24
To: asterisk-video at lists.digium.com
Cc: Pauli Østerø
Subject: Re: [Asterisk-video] Videomixing in MeetMe

Hi Pauli,

thanks for your interest, it's very appreciated.

About your problem, it looks like Asterisk fails at connecting to the mixer on 
startup, and so disables its functionality. Can you check in the rest of the 
verbose startup output if there are any messages related to the mixer? All is 
done in another thread and so it could appear while other modules are being 
loaded. Besides, check with 'xcon info' console command if there's any other 
info.

You might try setting the mcu_ip to your local ip instead of 127.0.0.1 and see 
if it helps. However, I can't see any information about the parsing of the 
mcu-related lines on startup: so it appears they are not being read at all.

Keep me updated, regards,
Lorenzo