<span style="font-family: Arial, Helvetica, sans-serif; font-size: 10pt"><br />
<br />
<br />
On Apr 7, 2011, at 8:51 AM, Ishfaq Malik <ish@pack-net.co.uk> wrote:<br />
<br />
> On Thu, 2011-04-07 at 08:37 -0400, Bryant Zimmerman wrote:<br />
>><br />
>> On Apr 6, 2011, at 8:54 PM, Edwin Lam <edwin.lam@officegeneral.com><br />
>> wrote:<br />
>><br />
>>> On 4/6/11 3:02 PM, Bryant Zimmerman wrote:<br />
>>>><br />
>>>> Thanks for your response. I have added the patch for 18818 per<br />
>>>> Michel Verbrask's<br />
>>>> recomendation. It appers that it has made quite a difference. I<br />
>>>> don't have an PRI<br />
>>>> connections as all of our PRI's are connected via SIP gateways. I<br />
>>>> did run into<br />
>>>> serveral instances wher I had to kill -9 the process as well but<br />
>>>> post patch I have<br />
>>>> been in good shape know on wood. I hope there will be a new<br />
>> release<br />
>>>> that will<br />
>>>> address the stability issues very soon if they release 1.8.4<br />
>>>> without cleaning this<br />
>>>> up I won't move unitl it is addressed.<br />
>>><br />
>>> looking back at the messages file for the past 2 days. it<br />
>>> just hanged on totally different events none of which related<br />
>>> to Local channels.<br />
>>><br />
>>> as far as the PRI not hearing early media issue. here's the<br />
>>> excerpt from the messages file after "pri debug on" command:<br />
>>><br />
>>> *********************<br />
>>><br />
>>> -- Executing [18008291011@out_going_x:1] Dial("SIP/ <br />
>><br />
>> ... Parts Removed see origional response<br />
>><br />
>>> -- Processing IE 30 (cs0, Progress Indicator)<br />
>>> -- PROGRESS with cause code 127 received<br />
>>> -- DAHDI/34-1 is making progress passing it to SIP/4988-6-00000b45<br />
>>><br />
>>> ***********************************<br />
>>><br />
>>> i used the same SIP station to dial the same 800 number<br />
>>> on both versions (1.8.3.2 & 1.6.2.17). the output are<br />
>>> pretty much identical except on 1.8.3.2, after the<br />
>>> "PROGRESS with cause code 127..." message. i would hear<br />
>>> nothing until the other side timed out & hang up, whereas on<br />
>>> 1.6.2.17. i got the "DAHDI/... is making progress passing it to<br />
>>> SIP..."<br />
>>> message and can hear the early media from the other side.<br />
>>><br />
>>><br />
>>>> For Now 1.8.3..2 is very bad.<br />
>>><br />
>>> agreed...<br />
>><br />
>> From: "Satish Patel" <satish_lx@hotmail.com><br />
>> Sent: Thursday, April 07, 2011 8:22 AM<br />
>> Oh! Boy,<br />
>><br />
>> Is it ture 1.8.3 is unstable? We are planning to put this in<br />
>> production. Please suggest me what should I do?<br />
>><br />
>><br />
>> Satish<br />
>><br />
>> For me 1.8.3.2 has been the worst build that I have tried to use as<br />
>> far a stability in a very long time. We are having issues<br />
>> with deadlocks and voicemail.<br />
>> I don't have a good option for you if you want to run 1.8 currently<br />
>> the most stable release version I have found is 1.8.2.3 but I am<br />
>> having the Voicemail issues there as well.<br />
>> Things like messages not deleting propperly and hanging up the mail<br />
>> box so users can't check them.<br />
><br />
> 1.8.2 is unusable if you use RealTime without the patch in this issue<br />
><br />
> https://issues.asterisk.org/bug_view_advanced_page.php?bug_id=18403<br />
><br />
><br />
<br />
<span style="font-family: tahoma; font-size: 13px;"> <b>From</b>: "Satish Patel" <satish_lx@hotmail.com><br />
<b>Sent</b>: Thursday, April 07, 2011 9:06 AM<br />
<br />
</span>We don't have realtime configuration everything is in plain text file.<br />
<br />
Is 1.8.3 has realtime issue or general issue?<br />
<br />
Satish<br />
I have seen my issues with the realtime disabled and using just plain text. The issues get worse for me when we move to our realtime confgs. So from my perspective I would say you might get farther with realtime off but I would not bank on it.<br />
<br />
<br /></span>