Hi,
One more interesting fact, i see correlation with DTMF features, after i
disabled corresponding options on dial commands (like htw) the
timestamps on rtp are constantly growing and no more one way audio
problems after call transfer, hold, parking etc. So it seems there is a
bug related to
Hi All,
Could somebody explain me how the timestamps are computed in asterisk
while bridging two sip channels ?
I've got situation with my provider, who changed some things in config
and added some codecs (that much i know) and after that we got one way
audio issues. It seems that the problem
Liivo,
I wonder if you are dealing with this general class of issues:
https://issues.asterisk.org/view.php?id=11491
-- Alex
--
Alex Balashov - Principal
Evariste Systems
Web : http://www.evaristesys.com/
Tel : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
Hi Alex,
Yes, it's almost the same, except the fact that in my case timestamps
sometimes decrease drastically. In internal network I have Snom 3xx
phones with upgraded firmware, internal leg has no issues, i captured
both legs and phones-asterisk part is ok, the other part,
asterisk-provider
On Wed, 19 May 2004, Rich Adamson wrote:
As you already know, the timestamp problem with cisco phones dropping
packets has been associated with at least two channels.
snip
Although iax capi are getting hammered, the real issue seems to be
that no one has opened a high sev TAC case to fix
As you already know, the timestamp problem with cisco phones dropping
packets has been associated with at least two channels.
snip
Although iax capi are getting hammered, the real issue seems to be
that no one has opened a high sev TAC case to fix the root problem.
If I was the one
Problems (just for bkw):
1. Stable does not include the major iax2 fixes that were corrected last
month 2. Head has a iax2/gsm sequence number issue
both result in choppy audio when transcoded to sip on Cisco phones.
As has been noted MULTIPLE TIMES on this list, there is no realistic
You're not the only one with this frustration / show stopper, and
regardless
of what bkw says, its a serious problem that for whatever reason, a few
arrogant people refuse to acknowledge.
Get ethereal traces where we can see timestamps and we can figure it out.
My phones aren't doing this.
I presented a stopgap solution to this list earlier this week (TDMoE
between
two * boxes to give you clean RTP timestamps to the Ciscos connected to
*1,
and *2 to the world)
That's just silly to have to do this. Collect me some timestamp info so we
can see this invalid timestamp non-sense
Problems (just for bkw):
1. Stable does not include the major iax2 fixes that were corrected last
month 2. Head has a iax2/gsm sequence number issue
both result in choppy audio when transcoded to sip on Cisco phones.
As has been noted MULTIPLE TIMES on this list, there is no realistic
That's not even close to an acceptable solution. Try this for
perspective...
A new service provider is getting ready to provide iax termination service
to asterisk users throughout the world. Lots of systems and agreements in
place. There is no usable cvs code to start the offering. Your
On Fri, 21 May 2004, brian wrote:
Get ethereal traces where we can see timestamps and we can figure it out.
I did. See a post a few days ago (in the AArgh thread). But I'm the
chan_capi problem guy... :(
Other than that I can't reproduce the problem, trust me I HAVE tried.
Appreciate it.
Care to find me on IRC and let me look at it and see if I can fix it?
bkw
-Original Message-
From: [EMAIL PROTECTED] [mailto:asterisk-users-
[EMAIL PROTECTED] On Behalf Of Vic Cross
Sent: Friday, May 21, 2004 9:04 AM
To: [EMAIL PROTECTED]
Subject: RE: [Asterisk-Users] RTP
Sent: Friday, May 21, 2004 9:26 AM
To: [EMAIL PROTECTED]
Subject: RE: [Asterisk-Users] RTP timestamps (was: AArgh, * and the 7960)
Care to find me on IRC and let me look at it and see if I can fix it?
bkw
-Original Message-
From: [EMAIL PROTECTED] [mailto:asterisk-users-
[EMAIL
-Original Message-
From: [EMAIL PROTECTED] [mailto:asterisk-users-
[EMAIL PROTECTED] On Behalf Of Vic Cross
Sent: Friday, May 21, 2004 9:04 AM
To: [EMAIL PROTECTED]
Subject: RE: [Asterisk-Users] RTP timestamps (was: AArgh, * and the
7960)
On Fri, 21 May 2004, brian wrote
This time stamp issue is all gone.. now if everyone will just UPDATE!
bkw
- Original Message -
From: Andres [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, May 21, 2004 4:14 PM
Subject: Re: [Asterisk-Users] RTP timestamps
VC: My phone is broken: I get no audio.
TAC: Show
brian k. west wrote:
This time stamp issue is all gone.. now if everyone will just UPDATE!
bkw
It is not gone. We updated one more time all our Asterisk boxes l0 days
ago (fresh checkout). And the problem was also evident (no other
providers involved in the tests, just calls between all our
On Fri, 2004-05-21 at 18:22, Andres wrote:
It is not gone. We updated one more time all our Asterisk boxes l0 days
ago (fresh checkout). And the problem was also evident (no other
providers involved in the tests, just calls between all our boxes). We
quickly put in place the rtp.c hack
Watch the CVS logs the update was put in stable TODAY for a timestamp issue
in chan_iax2.c
bkw
- Original Message -
From: Andres [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, May 21, 2004 5:22 PM
Subject: Re: [Asterisk-Users] RTP timestamps
brian k. west wrote:
This time
Excellent! I'll give it a shot.
-brian
brian k. west wrote:
This time stamp issue is all gone.. now if everyone will just UPDATE!
bkw
- Original Message -
From: Andres [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, May 21, 2004 4:14 PM
Subject: Re: [Asterisk-Users] RTP timestamps
20 matches
Mail list logo
