Re: [Ekiga-list] [Test site proposal]
On Saturday 13 January 2007 11:41, Damien Sandras wrote:
> Le samedi 13 janvier 2007 à 10:31 -0800, Remco Treffkorn a écrit :
> > On Saturday 13 January 2007 09:41, Damien Sandras wrote:
> > > Le samedi 13 janvier 2007 à 18:19 +0100, Daniel Huhardeaux a écrit :
> > > > Damien Sandras a écrit :
> > > > > [...]
> > > >
> > > > Hello
> > > >
> > > > > However, we are using Asterisk, and Asterisk allows setting codecs
> > > > > only for the SIP channel and not application by application, which
> > > > > is the problem.
> > > >
> > > > Don't quiet understand the meaning of this. You can set codecs per
> > > > user or peer - eg 500 Ulaw/Alaw, 502 ilbc&gsm, etc ...- Also, you can
> > > > force a codec with the ${SIP_CODEC} variable.
> > >
> > > Just try...
> > > It is not possible.
> >
> > Codec preferences can be set in the [general] section in sip.conf, but
> > overwritten in the individual extension setting. It is possible to have a
> > [500] extension with only g.711 and for example) and a [501] with gsm and
> > g.729.
>
> Sure, but 500 is not a SIP peer/user. 500 is a "local" extension that
> bridges to the Echo() application.
>
> Am I missing something?
I think the point was that the [general] section allows you to allow one list
of codecs, but the peer section overwrites that.
If all your peers have explicit codec selections, you can control the codec
list for apps by the codec list in the [general] section. How else would
asterisk make a codec selection? It's still a sip call...
Cheers,
Remco
--
Remco Treffkorn (RT445)
HAM DC2XT
[EMAIL PROTECTED] (831) 685-1201
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Very choppy sound with sip:[EMAIL PROTECTED]
>> The only thing I am getting is a "Remote user rejected call" error message. >> >> > 1). Are You sure, You have iLBC codec enabled? (don't remember if that > site accepts anything else). That's right - iLBC was not enabled. After enabling it, the results were the same as when getting a connection with [EMAIL PROTECTED] and the PCMA codec - sound so choppy that is almost unintelligible. > 2). If codec is enabled, try ekiga -d=4 (debug), and maybe post it for > analysis by Damien? The log corresponding to 30 seconds worth of call is nearly 64KB long. I wonder if such a thing can be posted here? ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] [Test site proposal]
Le samedi 13 janvier 2007 à 21:23 +0100, Jan Schampera a écrit : > On Sat, 13 Jan 2007 20:41:19 +0100 > Damien Sandras <[EMAIL PROTECTED]> wrote: > > > Sure, but 500 is not a SIP peer/user. 500 is a "local" extension that > > bridges to the Echo() application. > > Ah, you call it in the dialing plan? Yes. -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] [Test site proposal]
On Sat, 13 Jan 2007 20:41:19 +0100 Damien Sandras <[EMAIL PROTECTED]> wrote: > Sure, but 500 is not a SIP peer/user. 500 is a "local" extension that > bridges to the Echo() application. Ah, you call it in the dialing plan? J. -- "One of the main causes of the fall of the Roman Empire was that, lacking zero, they had no way to indicate successful termination of their C programs" --Robert Firth ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Router problem
On Saturday 13 January 2007 19:43, Damien Sandras wrote: > > Start 6890 > > End 6900 Those are the ports you are using for amsn, Keith. > > UDP 5060 > > TCP 1720 > That big depends on the result of the NAT test. The FAQ tells you the implications of each possible result. Anne pgp5thzlSsxuw.pgp Description: PGP signature ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Router problem
Hello, Le samedi 13 janvier 2007 à 19:06 +, Keith Powell a écrit : > Hello. > > I have just bought a web cam and am trying to get Ekiga working, but > without much success! As this is my first attempt at setting up 'web > chatting', I am very much a newbie. So sorry if this is a very basic > question. > > When I run Ekiga, without even trying to connect, the TX/RX light on > my router immediately comes on and stays on permanently. The only way > to stop it being on, is to switch the router off. It stays on even > when I have shut ekiga down. Whilst it is on, the router is blocked > and cannot be used for anything. > So Ekiga is crashing your router. Wouldn't you have a router that supposedly supports SIP and has a bug? [...] > I have been told that, in order to get Linux 'chat' programs sending > and receiving, I need the forwarding ports open in my router: > > Start 6890 > End 6900 > UDP 5060 > TCP 1720 > That's wrong. (Check the FAQ) -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] [Test site proposal]
Le samedi 13 janvier 2007 à 10:31 -0800, Remco Treffkorn a écrit :
> On Saturday 13 January 2007 09:41, Damien Sandras wrote:
> > Le samedi 13 janvier 2007 à 18:19 +0100, Daniel Huhardeaux a écrit :
> > > Damien Sandras a écrit :
> > > > [...]
> > >
> > > Hello
> > >
> > > > However, we are using Asterisk, and Asterisk allows setting codecs only
> > > > for the SIP channel and not application by application, which is the
> > > > problem.
> > >
> > > Don't quiet understand the meaning of this. You can set codecs per user
> > > or peer - eg 500 Ulaw/Alaw, 502 ilbc&gsm, etc ...- Also, you can force a
> > > codec with the ${SIP_CODEC} variable.
> >
> > Just try...
> > It is not possible.
>
> Codec preferences can be set in the [general] section in sip.conf, but
> overwritten in the individual extension setting. It is possible to have a
> [500] extension with only g.711 and for example) and a [501] with gsm and
> g.729.
>
Sure, but 500 is not a SIP peer/user. 500 is a "local" extension that
bridges to the Echo() application.
Am I missing something?
--
_ Damien Sandras
(o-
//\Ekiga Softphone : http://www.ekiga.org/
v_/_ NOVACOM : http://www.novacom.be/
FOSDEM : http://www.fosdem.org/
SIP Phone : sip:[EMAIL PROTECTED]
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Router problem
Keith Powell wrote: > Hello. > > I have just bought a web cam and am trying to get Ekiga working, but > without much success! As this is my first attempt at setting up 'web > chatting', I am very much a newbie. So sorry if this is a very basic > question. > > When I run Ekiga, without even trying to connect, the TX/RX light on > my router immediately comes on and stays on permanently. The only way > to stop it being on, is to switch the router off. It stays on even > when I have shut ekiga down. Whilst it is on, the router is blocked > and cannot be used for anything. No idea what is happening there, but I would suggest that you start by turning off video (under Preferences) and just get the audio going. > I have another problem as well, which I am sending in the same message > in case they are related. > > There is no sound. When I run the set-up wizard and do the sound test, > nothing. The mic and speaker sliders in the audio tab are completely > to the left. When I try to move them, they spring back to the left, > so the audio is always turned right down. This is a "feature" of ekiga which completely confused me when I first tried it, and had teething problems. The behaviour you describe is normal: the sliders only become active and sensible during a call. So that is one problem solved :-) A E Lawrence ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] Router problem
Hello. I have just bought a web cam and am trying to get Ekiga working, but without much success! As this is my first attempt at setting up 'web chatting', I am very much a newbie. So sorry if this is a very basic question. When I run Ekiga, without even trying to connect, the TX/RX light on my router immediately comes on and stays on permanently. The only way to stop it being on, is to switch the router off. It stays on even when I have shut ekiga down. Whilst it is on, the router is blocked and cannot be used for anything. I have another problem as well, which I am sending in the same message in case they are related. There is no sound. When I run the set-up wizard and do the sound test, nothing. The mic and speaker sliders in the audio tab are completely to the left. When I try to move them, they spring back to the left, so the audio is always turned right down. I have tried Ekiga on three Linux distributions and each has the same problems. Also, I have tested two other 'chat' programs and neither have this router problem. I have been told that, in order to get Linux 'chat' programs sending and receiving, I need the forwarding ports open in my router: Start 6890 End 6900 UDP 5060 TCP 1720 This I have done. The router works well for surfing and mailing. It's just with Ekiga! I have searched the archives and Googled, but no success. So if anyone can please help me, I would be very grateful. Many thanks Keith ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Coexistence of ekiga with an ATA
Simon Wood wrote: > Hi, Just thought I'd add my $0.02 on this. I have a set up of 3 > machines (all running Ekiga) and 1 hard phone running behind a single > OpenWrt router. > > To get this working I altered the port settings on Ekiga(s) using > gconf-editor, and enabled both STUN and Proxy (fwdnat2.pulver.net). I > have set each endpoint to use a set ports which is exclusive (doesn't > overlap any of it's siblings). > > Each endpoint has seperate FWD numbers (for testing) and can > call/message each other, albeit via going out to the internet and > coming back in again. But my ATA (= hard phone?) is *upstream* of the routers (for a reason) which may be the crucial difference. If I moved the ATA downstream, I would expect the problem to go away, but I haven't tried this so far. Otherwise my setup is just the same. Different proxy , but that should not matter. > I think that I might have seen a similar message in the past I'll > confirm later whether it happens if I turn off the proxying. Unless we are talking of a different message, turning off proxying will eliminate the message :-) > Note on ports: You *HAVE* to set ranges... otherwise Ekiga gets > upset. My IP hard-phone only needs 2 ports (SIP and RTP). So does mine, and yes all my different ekigas have different non overlapping port settings which are distinct from those of the ATA. > I see no value in placing your ATA upstream, it's ports should be > exclusive anyhow. You have missed the point, It's not the ports: it's bandwidth. I have 256Kb/s upstream and 2Mb/s downstream on a broadband connection, but I still get occasional breakups even when the ATA alone is engaged in a call. If it was downstream of a router, it would not be able to give priority to its own voip packets during a call. Oh, and I can just power the modem and ATA to maintain voip with no other machines running for environmental reasons when I don't need the rest of the network active. As I have said before everything seems to work 95% of the time, but requires this touching of the STUN setting in ekiga instances before they can make calls. It is not a big deal, but it would be nice to understand what is going on. > So your set up isn't that unusual Maybe having the ATA up front is the unusual part? A E Lawrence ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] [Test site proposal]
On Saturday 13 January 2007 09:41, Damien Sandras wrote:
> Le samedi 13 janvier 2007 à 18:19 +0100, Daniel Huhardeaux a écrit :
> > Damien Sandras a écrit :
> > > [...]
> >
> > Hello
> >
> > > However, we are using Asterisk, and Asterisk allows setting codecs only
> > > for the SIP channel and not application by application, which is the
> > > problem.
> >
> > Don't quiet understand the meaning of this. You can set codecs per user
> > or peer - eg 500 Ulaw/Alaw, 502 ilbc&gsm, etc ...- Also, you can force a
> > codec with the ${SIP_CODEC} variable.
>
> Just try...
> It is not possible.
Codec preferences can be set in the [general] section in sip.conf, but
overwritten in the individual extension setting. It is possible to have a
[500] extension with only g.711 and for example) and a [501] with gsm and
g.729.
Cheers,
Remco
--
Remco Treffkorn (RT445)
HAM DC2XT
[EMAIL PROTECTED] (831) 685-1201
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Coexistence of ekiga with an ATA
Hi, Just thought I'd add my $0.02 on this. I have a set up of 3 machines (all running Ekiga) and 1 hard phone running behind a single OpenWrt router. To get this working I altered the port settings on Ekiga(s) using gconf-editor, and enabled both STUN and Proxy (fwdnat2.pulver.net). I have set each endpoint to use a set ports which is exclusive (doesn't overlap any of it's siblings). Each endpoint has seperate FWD numbers (for testing) and can call/message each other, albeit via going out to the internet and coming back in again. I think that I might have seen a similar message in the past I'll confirm later whether it happens if I turn off the proxying. Note on ports: You *HAVE* to set ranges... otherwise Ekiga gets upset. My IP hard-phone only needs 2 ports (SIP and RTP). I'm still trying to understand the port usage, but for a single endpoint it looks like you need: 1 SIP listener Port (ie. 5080) at least 2 (per reigistered/active account) UDP ports for SIP operation (ie. 5081:5089) - it seems that these are randomly randomly from this range as an account is registered/enabled. at least 2 (1 each direction) for RTP (ie. 8080:8089) - we'll need more once multi-line starts working... :-) The better solution for this many endpoints would be setting up my own SIP proxy on the router, but I'm being lazy. I see no value in placing your ATA upstream, it's ports should be exclusive anyhow. So your set up isn't that unusual ;-) Simon. ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] [Test site proposal]
Le samedi 13 janvier 2007 à 18:19 +0100, Daniel Huhardeaux a écrit :
> Damien Sandras a écrit :
> > [...]
> Hello
> >
> > However, we are using Asterisk, and Asterisk allows setting codecs only
> > for the SIP channel and not application by application, which is the
> > problem.
> >
> Don't quiet understand the meaning of this. You can set codecs per user
> or peer - eg 500 Ulaw/Alaw, 502 ilbc&gsm, etc ...- Also, you can force a
> codec with the ${SIP_CODEC} variable.
>
Just try...
It is not possible.
--
_ Damien Sandras
(o-
//\Ekiga Softphone : http://www.ekiga.org/
v_/_ NOVACOM : http://www.novacom.be/
FOSDEM : http://www.fosdem.org/
SIP Phone : sip:[EMAIL PROTECTED]
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] [Test site proposal]
Damien Sandras a écrit :
> [...]
Hello
>
> However, we are using Asterisk, and Asterisk allows setting codecs only
> for the SIP channel and not application by application, which is the
> problem.
>
Don't quiet understand the meaning of this. You can set codecs per user
or peer - eg 500 Ulaw/Alaw, 502 ilbc&gsm, etc ...- Also, you can force a
codec with the ${SIP_CODEC} variable.
--
Daniel
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Coexistence of ekiga with an ATA
Julien Puydt wrote: > ael a écrit : > >>Initially there are 14 packets exchanged. This is while ekiga is >>starting up. At this point attempted calls to, say [EMAIL PROTECTED], fail >>usually with abnormal call termination. > > > You mean ekiga wasn't registered yet to ekiga.net ? No. Normally there is no problem with registration. This was explained earlier in this thread. I suspect that the system is behaving in some respects at least as a symmetric NAT when the STUN protocol is nondeterministic, although I have not yet tried to analyse the STUN traffic: I am a newbie and need to read the relevant rfcs. I hope to find time to do that soon. Meanwhile, things work with this odd fix of "reactivating" the STUN setting. But it would be nice to understand what is happening and to get total reliability. I did say that the captured data was the STUN traffic: it was filtered so that only packets exchanged with the stun servers were collected. So the registration phase was not captured. A E Lawrence ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] 2.04 Release
Le vendredi 12 janvier 2007 à 10:38 -0800, George Boyd a écrit : > I am considering changing over to the CVS version of Ekiga. Is 2.04 > going to be released soon, or is it worthwhile to go ahead and use the > CVS version? I would wait for 2.0.4. As soon as I have 2 minutes, I'll work on it. -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
