[OpenSIPS-Users] NOTIFY nat_keepalive - Bad Event

[Bogdan-Andrei Iancu]

Hi Dan,

Dan Pascu wrote:
> On Friday 27 February 2009, Bogdan-Andrei Iancu wrote:
>   
>> Hi Carlo,
>>
>> I think the problem is with the phone as they do not understand the
>> "keep-alive" event sent in NOTIFY.
>>
>> It is nothing you can do about this (in is not on the proxy side).
>> Maybe in the future we can add a module parameter for removing the
>> Event header from the REQUEST and make the dummy phone happy.
>>     
>
> That's not gonna work. A NOTIFY without an Event header is invalid and I 
> see no reason why a phone could accept it that way. Most likely one will 
> get the same (or maybe some different) negative reply.
>   
I see. Thanks for the fix.
>   
>> Anyhow, as best practice , the OPTIONS method is more appropriate for
>> nat pinging.
>>     
>
> I have to disagree. OPTIONS generate 2-3 times more traffic because of the 
> bigger replies. OTOH, it doesn't really matter if we get a 200 OK or a 
> negative reply to such a keep-alive request, does it? All it matters is 
> that the device behind NAT sends something (anything) to keep the NAT 
> open from inside. NOTIFY gets the job done with less traffic, which makes 
> it better.
>   
Indeed, the OPTIONS may generate more traffic (depends on the 
implementation - kphone sends with SDP also, other not). But when comes 
to interoperability, OPTIONS is more accepted by end devices, rather 
then NOTIFY (where the phone must implement the method and the event).

On the other hand I totally agree - the reply to a SIP ping is not 
relevant as code - relevant is just the fact that the client sends back 
traffic.

Regards,
Bogdan
>   
>> Regards,
>> Bogdan
>>
>> Carlo Dimaggio wrote:
>>     
>>> Hi all,
>>>
>>> I'm using nat_traversal and the nat_keepalive function. For phones-
>>> compatibility I have to use the "NOTIFY" method but all my registered
>>> phones reply to opensips with "Bad Request / Bad Event" (with OPTIONS
>>> method some phones reply with "200 OK"). What I am wrong?
>>>       
>
>