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
>
ehalf Of brian
> 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---
sterisk-Users] RTP timestamps (was: AArgh, * and the 7960)
>
> 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
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 i
> 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. You
> > 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
> 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-s
> 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.
> 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 realisti
> > As you already know, the timestamp problem with cisco phones dropping
> > packets has been associated with at least two channels.
> >
> > 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
10 matches
Mail list logo
