Sorry. After more coffee and re-reading I understand patch23 is a backwards
step after 4.0.4 is installed, so further patching sipxbridge is not
necessary.
============================
Tony Graziano, Manager
Telephone: 434.984.8430
Fax: 434.984.8431

Email: tgrazi...@myitdepartment.net

LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
Fax: 434.984.8427

Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/

----- Original Message -----
From: M. Ranganathan <mra...@gmail.com>
To: Tony Graziano <tgrazi...@myitdepartment.net>
Cc: Sipx-users list <sipx-users@list.sipfoundry.org>
Sent: Fri Nov 20 07:41:38 2009
Subject: Re: [sipx-users] 4.0.4 upgrade and sipxbridge pacth

On Fri, Nov 20, 2009 at 7:24 AM, M. Ranganathan <mra...@gmail.com> wrote:
> On Fri, Nov 20, 2009 at 4:59 AM, Tony Graziano
> <tgrazi...@myitdepartment.net> wrote:
>> When installing sipxecs 4.0.4 update, what level of the sipxbridge pacth
>> is
>> the equivalent to? patch 23?
>
>
> I fixed two more issues after that having to do with Max-Forwards
> header missing from an ITSP inbound INVITE and consultative transfers
> from SMC (counterpath) 3456 phone getting  dropped  when MOH is
> enabled on sipxbridge (XX-7039). I did not post a patch after I fixed
> these issues.
>

Another issue that was fixed :

Stuck CDR record on consultative hairpin transfer to the PSTN.


Ranga


>>
>> Thanks,
>> Tony
>> _______________________________________________
>> sipx-users mailing list sipx-users@list.sipfoundry.org
>> List Archive: http://list.sipfoundry.org/archive/sipx-users
>> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
>> sipXecs IP PBX -- http://www.sipfoundry.org/
>>
>
>
>
> --
> M. Ranganathan
>



-- 
M. Ranganathan
_______________________________________________
sipx-users mailing list sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to