Hello,
If you want in-dialog pinging or BYE timeout to be used with
topology_hiding(), you can easily just create the dialog before, and
then apply topology_hiding() on top of the existing dialog, something like :
if (is_method("INVITE")) {
create_dialog("PpB");
topology_hiding();
}
When the timeout limit is reached, or when one end-point does not reply
to pings anymore, you can catch the BYEs in local_route, where you can
trigger manual accounting for that call, like :
local_route {
if (is_method("BYE")) {
acc_db_request("200 Dialog Timeout", "acc");
}
}
Regards,
Vlad Paiu
OpenSIPS Developer
http://www.opensips-solutions.com
On 04/02/2012 07:32 AM, Peter King wrote:
A quick question for the group: In reading Dialog module's
topology_hiding feature the following is mentioned:
"The great advantage of using the topology hiding functionality built
inside dialog module is that you can use all the dialog modules
functionalities: profiles, dialog variables, dialog timeouts, etc.."
While it's true that default_timeout and a value set for timeout_avp
are enforced, is it possible to use the BYE on timeout and ping
callee/caller features available with create_dialog("BPb")?
topology_hiding does not take any parameters within the parenthesis it
seems. Is there a plan on the roadmap to add BYE on timeout and
pinging to topology_hiding?
Also, when the timeout limit is reached, BYE messages are not
trasmitted from upstream to downstream, which is expected, however,
CDRs are also not written for such calls. Is this function as designed
or a bug?
Thanks,
Peer
_______________________________________________
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
