Re: [Ekiga-list] ekiga answers with delay ¿... ?

[Bent Bagger]

On 24/11/06, Craig Southeren [EMAIL PROTECTED] wrote:

 I know that Asterisk has a nasty habit of changing the payload type -
 perhaps this is what is happening? Can anyone confirm?

I do not know how nasty Asterisk is with regards to changing payload
type. I believe that after having finished the negotiation, Asterisk
sticks to the selected codec. In any case, the order of codec
preference is totally under the control of the Asterisk sysadm (order
of 'allow's in the SIP channel configuration - sip.conf)

I have just run an experiment on my asterisk where I forced both Ekiga
and Asterisk to use one and the same codec - ulaw (PCMU) in this case.
The problem still persists: I did not hear the first part of the echo
test greeting.

Best regards,

Bent
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] ekiga answers with delay ¿... ?

[Craig Southeren]

On Thu, 23 Nov 2006 12:40:51 +0100
Daniel Huhardeaux [EMAIL PROTECTED] wrote:

 Julien Puydt a écrit :
  [...]
  to reach. So, ekiga wastes 1 or 2 seconds for establishing the connexion
  ¿...?. With twinkle there isn't this delay.
  
 
  Known bug : asterisk begins to send the voice before it acknowledged 
  which codec it will use for that!

 Not a bug in Asterisk: Ekiga is not ready but should be.

I've only just noticed this thread, so please accept my apologies for
the late reply.

It's not unusual for a calling endpoint to receive media before it
receive acknwledgement that the call has been answered. With some
protocols (like H.323) this can be due to the timing of the signalling
(which is carried via TCP) and the RTP (which is carried on UDP). For
SIP, it can be due to the media and signalling taking different paths.
Or it can just be due to delays in the receiving endpoint.

Regardless, the calling endpoint should be ready to receive RTP at any
time after it sends to call offer and OPAL should do this already.

However, if the receiving endpoint uses a different payload type than
the one offered, then the receiving endpoint won't be able to accept the
incoming RTP data until the signalling reply is received. 

I know that Asterisk has a nasty habit of changing the payload type -
perhaps this is what is happening? Can anyone confirm?

   Craig

---
 Craig Southeren  Post Increment – VoIP Consulting and Software
 [EMAIL PROTECTED]   www.postincrement.com.au

 Phone:  +61 243654666  ICQ: #86852844
 Fax:+61 243656905  MSN: [EMAIL PROTECTED]
 Mobile: +61 417231046  Jabber: [EMAIL PROTECTED]

 It takes a man to suffer ignorance and smile.
  Be yourself, no matter what they say.   Sting


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] ekiga answers with delay ¿... ?

[Julien Puydt]

Agustín Treceño a écrit :
 Hello everybody!
 
 I have a pbx asterisk configured and i want to try ekiga like softphone
 (until now i use twinkle). Everything is ok, but when i make a call, i
 receive the ring tone for 2 seconds, therefore i ear the message you are
 trying to reach insted of enter the extension of the person you are 
 trying
 to reach. So, ekiga wastes 1 or 2 seconds for establishing the connexion
 ¿...?. With twinkle there isn't this delay.

Known bug : asterisk begins to send the voice before it acknowledged 
which codec it will use for that!

Snark on #ekiga
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list