Hello!
I’ve tried many variants, but unsuccessfully.
After BYE message, dialog change state to [5] and fetch_dlg_val doesn’t export
any stored values.
Are the other ways to save dialog-related values after BYE message?
Best regards,
Alexander Mustafin
mustafin.aleksa...@gmail.com
09 нояб.
Hi, Alexander!
Well, this is pretty weird, since if in the previous route (the one that
calls the BYE route) you can access the variables you should be able to
see them here too.
Are you sure you are talking about the same request? Can you print some
logs in the previous route (the one that
Hi, Răzvan!
I’m using topology_hiding() function - and loose_route() will always false.
match_dialog() in this route return TRUE and $DLG_status return 5 (dialog ended)
route[BYE] {
xlog(L_DEBUG, ~ Enter in [BYE] section ~);
xlog( DIALOG status [$DLG_status]); #DEBUG
Hi, Alexander!
Are you fetching the value before the loose_route() function call? It
should be available only after loose_route() or match_dialog() are
executed on the BYE request.
Best regards,
Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 11/08/2013 05:37
Hi, Alexander!
So basically you're saying that after the loose_route() call you can no
longer access the dialog variable? Are you sure you are calling the BYE
route only in this place?
You should check if you are really in a dialog context. Inside the BYE
route, just print the $DLG_status
Hi!
I’m want pass to dialog additional values, such as incoming and outgoing gate
from drouting.
I’m use store_dlg_value(incoming_gate»,$avp(gw_id)) and this value
successfully pass to dialog (I can see it in dialog table in MySQL) and in log:
Nov 8 04:27:28 ops /usr/sbin/opensips[21074]:
