On 12/30/2011 03:09 PM, James Lamanna wrote:
On Fri, Dec 30, 2011 at 11:55 AM, Kevin P. Fleming wrote:
On 12/30/2011 12:29 PM, James Lamanna wrote:
On Fri, Dec 30, 2011 at 8:35 AM, James Lamannawrote:
On Fri, Dec 30, 2011 at 6:02 AM, Kevin P. Fleming
wrote:
On 12/30/2011 04:07 AM, J
On Fri, Dec 30, 2011 at 11:55 AM, Kevin P. Fleming wrote:
> On 12/30/2011 12:29 PM, James Lamanna wrote:
>>
>> On Fri, Dec 30, 2011 at 8:35 AM, James Lamanna wrote:
>>>
>>> On Fri, Dec 30, 2011 at 6:02 AM, Kevin P. Fleming
>>> wrote:
On 12/30/2011 04:07 AM, James Lamanna wrote:
>
>
On 12/30/2011 12:29 PM, James Lamanna wrote:
On Fri, Dec 30, 2011 at 8:35 AM, James Lamanna wrote:
On Fri, Dec 30, 2011 at 6:02 AM, Kevin P. Fleming wrote:
On 12/30/2011 04:07 AM, James Lamanna wrote:
Hi,
I've been trying to fix NOTIFY replies (specifically keep-alives) in
1.4.42
(I can't u
On Fri, Dec 30, 2011 at 8:35 AM, James Lamanna wrote:
> On Fri, Dec 30, 2011 at 6:02 AM, Kevin P. Fleming
> wrote:
>> On 12/30/2011 04:07 AM, James Lamanna wrote:
>>>
>>> Hi,
>>> I've been trying to fix NOTIFY replies (specifically keep-alives) in
>>> 1.4.42
>>> (I can't upgrade to 1.8.x at the
On Fri, Dec 30, 2011 at 6:02 AM, Kevin P. Fleming wrote:
> On 12/30/2011 04:07 AM, James Lamanna wrote:
>>
>> Hi,
>> I've been trying to fix NOTIFY replies (specifically keep-alives) in
>> 1.4.42
>> (I can't upgrade to 1.8.x at the moment for various reasons).
>>
>> I've noticed for user agents th
On 12/30/2011 04:07 AM, James Lamanna wrote:
Hi,
I've been trying to fix NOTIFY replies (specifically keep-alives) in 1.4.42
(I can't upgrade to 1.8.x at the moment for various reasons).
I've noticed for user agents that have a VIA header with a different
port than the port the NOTIFY was sent f
Hi,
I've been trying to fix NOTIFY replies (specifically keep-alives) in 1.4.42
(I can't upgrade to 1.8.x at the moment for various reasons).
I've noticed for user agents that have a VIA header with a different
port than the port the NOTIFY was sent from,
the NOTIFY reply will always be sent back