Re: NAT and NOTIFY messages

"M. Ranganathan" <[email protected]>
Newsgroups gmane.comp.voip.nist-sip
Message-ID <[email protected]>
Lauri,

Are you using the same provider to send out the NOTIFY as the provider 
you use to respond to the SUBSCRIBE? . Maybe its a different UDP socket 
which would be the case if you used a different provider. That could be 
one reason.

Regards

Ranga

Lauri Tielinen wrote:

> Hello!
>
> I'm working on presence server using JAIN-SIP and I'm wondering if 
> someone could give me some help with traversing through NAT.
>
> I've got following quite basic SIPp flow:
> Client                Server
> REGISTER  ---------->
> 200       <----------
> SUBSCRIBE ---------->
> 200       <----------
> NOTIFY    <----------
> 200       ---------->
>
> Currently responses (200) are going nicely through the NAT with UDP 
> and TCP, but I'm unable to get NOTIFY messages through to the client.
>
> Responses are sent by using server transaction and I've tested NOTIFY 
> messages by using Dialog so far. I've also tried sending NOTIFY 
> statelessly, but that fails naturally. I also tried setting 
> CACHE_SERVER_CONNECTIONS and CACHE_CLIENT_CONNECTIONS to true, but 
> didn't notice any difference.
>
> What approach would be correct to handle sending of NOTIFY messages? 
> The NAT mapping is planned to be kept alive by sending REGISTER 
> messages often enough. I'm feeling that I'm looking in wrong direction 
> at the moment or missing something pretty simple so little help would 
> be appreciated.
>
> I'm using latest JAIN-SIP 1.2 from CVS.
>
> Best Regards,
>
> - Lauri Tielinen
>
> _______________________________________________
> nist-sip mailing list
> [email protected]
> http://www-x.antd.nist.gov/mailman/listinfo/nist-sip
>


-- 
M. Ranganathan 

Advanced Networking Technologies Division,
National Institute of Standards and Technology (NIST),
100 Bureau Drive, Stop 8920, Gaithersburg, MD 20899. 
tel:301 975 3664 , fax:301 590 0932 http://w3.antd.nist.gov/
Advanced Networking Technologies For the People!
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.