Adrian, To be more specific: - the router is not blocking sip - no sip-alg - the timeout for the nat seems to be lower than the timeout for the registration. So the router will simply cut the connection for the reverse nat. So the invites to the UA behind the router are "running" on a closed port.
I would like to have a solution to solve this for the most UA - without any configuration issue on the UA or the router. BR uwe > Uwe, > > It really depends on how strange is strange. Is this about routers that > seem to block incoming SIP traffic? There is a topic about this on > http://voip-info.org search for SIP ALG. > > If is about something else maybe you can define strange and other people > might help. > > Adrian > > > On Apr 9, 2009, at 2:43 PM, Uwe Kastens wrote: > >> Hello, >> >> I am searching for a solution for some SIP Clients which are behind some >> strange router. What is the best way to handle this? Send keepalive >> messages from the router to the UA or force the UA to send keepalive >> packages. >> >> I think a can handle this by modparam("nathelper", "sipping_method", >> "INFO")? >> >> BR >> >> Uwe >> >> -- >> >> kiste lat: 54.322684, lon: 10.13586 >> >> _______________________________________________ >> Users mailing list >> [email protected] <mailto:[email protected]> >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -- kiste lat: 54.322684, lon: 10.13586 _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
