Hi,
awesome, i did not notice this :)
Documentation for match_dialog:
"to cope with bogus sequential requests that do not have Route headers,
so they are not handled by loose_route(). "
Thanks for the hint.
Best Regards
On 02/22/2013 12:07 PM, Vlad Paiu wrote:
Hello,
No worries.
It would be good if you could post the question on the OpenSIPS users
mailing list, in the sense that other people might run into the same
issue.
You can force explicit matching of the dialog by calling the
'match_dialog' function from the dialog module.
The match_dialog() function doesn't rely on the presence of Route
headers, but rather it does SIP-wise matching of the dialog.
So the code would look like
if (has_totag()) {
if (loose_route() || match_dialog()) {
# process sequential messages belonging to a known dialog on
our server
}
}
Best Regards,
Vlad Paiu
OpenSIPS Developer
http://www.opensips-solutions.com
On 02/22/2013 11:17 AM, Max Mühlbronner wrote:
Hi,
Sorry to bother you directly, but it seems you were involed in this
problem.
http://lists.opensips.org/pipermail/users/2011-January/016473.html
Bug was closed:
http://sourceforge.net/tracker/?func=detail&aid=3090388&group_id=232389&atid=1086413
Do you know if there is any fix/possibility to fix this issue in
newer versions of opensips?
I am currently running on opensips1.7.2 and i am not sure if i can
now use fix_dialog(), when if(loose_route()) returns false (BYE from
linksys client does not mirror the route header, so loose_route does
return false.) ?
Do you know how other people fixed this issue in opensips? Weirdly
enough the clients are all Linksys atas (mostly PAP2t, but i think
also SPA8000).
Thanks very much, sorry to bother you but i thought maybe you are the
one to ask :)
Best Regards
Max M.
On 02/18/2013 04:30 PM, Vlad Paiu wrote:
Hello,
A new *DB_CACHEDB* module has been added to OpenSIPS trunk, and it
will also be present in the future 1.10 release.
The *DB_CACHEDB* module is a translator from the noSQL interface to
the SQL interface - it provides the SQL API while directly operating
with a noSQL engine. Thus, any OpenSIPS module that would regularily
need a regular SQL-based database, will now be able to run over a
NoSQL back-end, allowing for a much easier distribution and
integration of the currently existing OpenSIPS modules in a
distributed environment.
With this new module, you can easily achieve distribution of things
like your subscriber base, your DIDs and LCR information, etc, with
zero changes to the actual modules, and minimal changes at the
OpenSIPS script level.
While there currently is support for simply storing the location
information and the dialog information in a NoSQL back-end, further
work is needed in this direction.
For more information about the module, as well as usage examples and
the list of current limitation, please visit [1]
Testing and feedback are very much welcome.
[1] http://www.opensips.org/html/docs/modules/devel/db_cachedb
Best Regards,
--
Vlad Paiu
OpenSIPS Developer
http://www.opensips-solutions.com
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
