[asterisk-users] Asterisk 1.8.3

[Satish Patel]

Holy cow!!

Can I just build 1.8.2 over existing 1.8.3 ?

When we are going to fix all this thing???

--
Sent from my iPhone

On Apr 7, 2011, at 8:37 AM, "Bryant Zimmerman" <BryantZ at zktech.com>  
wrote:

>
> On Apr 6, 2011, at 8:54 PM, Edwin Lam <edwin.lam at officegeneral.com>
> wrote:
>
> > On 4/6/11 3:02 PM, Bryant Zimmerman wrote:
> >>
> >> Thanks for your response. I have added the patch for 18818 per
> >> Michel Verbrask's
> >> recomendation. It appers that it has made quite a difference. I
> >> don't have an PRI
> >> connections as all of our PRI's are connected via SIP gateways. I
> >> did run into
> >> serveral instances wher I had to kill -9 the process as well but
> >> post patch I have
> >> been in good shape know on wood. I hope there will be a new release
> >> that will
> >> address the stability issues very soon if they release 1.8.4
> >> without cleaning this
> >> up I won't move unitl it is addressed.
> >
> > looking back at the messages file for the past 2 days. it
> > just hanged on totally different events none of which related
> > to Local channels.
> >
> > as far as the PRI not hearing early media issue. here's the
> > excerpt from the messages file after "pri debug on" command:
> >
> > *********************
> >
> > -- Executing [18008291011 at out_going_x:1] Dial("SIP/
>
> ... Parts Removed see origional response
>
> > -- Processing IE 30 (cs0, Progress Indicator)
> > -- PROGRESS with cause code 127 received
> > -- DAHDI/34-1 is making progress passing it to SIP/4988-6-00000b45
> >
> > ***********************************
> >
> > i used the same SIP station to dial the same 800 number
> > on both versions (1.8.3.2 & 1.6.2.17). the output are
> > pretty much identical except on 1.8.3.2, after the
> > "PROGRESS with cause code 127..." message. i would hear
> > nothing until the other side timed out & hang up, whereas on
> > 1.6.2.17. i got the "DAHDI/... is making progress passing it to
> > SIP..."
> > message and can hear the early media from the other side.
> >
> >
> >> For Now 1.8.3..2 is very bad.
> >
> > agreed...
>
>  From: "Satish Patel" <satish_lx at hotmail.com>
> Sent: Thursday, April 07, 2011 8:22 AM
> Oh! Boy,
>
> Is it ture 1.8.3 is unstable? We are planning to put this in
> production. Please suggest me what should I do?
>
>
> Satish
>
> For me 1.8.3.2 has been the worst build that I have tried to use as  
> far a stability in a very long time. We are having issues with  
> deadlocks and voicemail.
> I don't have a good option for you if you want to run 1.8 currently  
> the most stable release version I have found is 1.8.2.3 but I am  
> having the Voicemail issues there as well.
> Things like messages not deleting propperly and hanging up the mail  
> box so users can't check them.
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
>               http://www.asterisk.org/hello
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20110407/f38555c7/attachment.htm>