[OpenSIPS-Users] external applications
Prathibha B
prathibhab.tvm at gmail.com
Sat Apr 6 09:29:45 UTC 2024
will accounting module help here?
On Sat, 6 Apr 2024 at 13:04, Prathibha B <prathibhab.tvm at gmail.com> wrote:
> When will the dialog status be in unconfirmed state? I've checked it the
> initial state of the call before getting any response. It returns Early
> state if the state is trying. But never returns unconfirmed state.
>
> Sent from Outlook for Android <https://aka.ms/AAb9ysg>
> ------------------------------
> *From:* Prathibha B <prathibhab.tvm at gmail.com>
> *Sent:* Saturday, April 6, 2024 10:36:05 AM
> *To:* OpenSIPS users mailling list <users at lists.opensips.org>
> *Subject:* Re: [OpenSIPS-Users] external applications
>
> PFA
>
> On Sat, 6 Apr 2024 at 07:14, Prathibha B <prathibhab.tvm at gmail.com> wrote:
>
> If someone attempts to make a call and cancels it, I need to maintain a
> log of those calls for reporting purposes.
>
> Sent from Outlook for Android <https://aka.ms/AAb9ysg>
> ------------------------------
> *From:* Users <users-bounces at lists.opensips.org> on behalf of Ben Newlin <
> Ben.Newlin at genesys.com>
> *Sent:* Friday, April 5, 2024 7:36:52 PM
> *To:* OpenSIPS users mailling list <users at lists.opensips.org>
> *Subject:* Re: [OpenSIPS-Users] external applications
>
>
> If you are executing that as the first command in the main route block the
> dialog will not have been created yet. The $DLG_status variable is only
> valid after the dialog has been created either by a call to create_dialog
> or by using another module that requires and auto-creates a dialog.
>
>
>
> Additionally, $DLG_status is documented to only be available for
> sequential requests, and only after calling loose_route (or match_dialog or
> topology_hiding_match, I believe).
>
>
>
> https://opensips.org/docs/modules/3.4.x/dialog.html#pv_DLG_status
>
> https://opensips.org/docs/modules/3.4.x/dialog.html#func_create_dialog
>
>
>
> I still don’t understand why you need some event to capture the start of
> the call. Even if you are not creating the dialog directly, your routing
> script has to have some sort of logic that is specific to a new call.
> Whatever you are trying to “capture” can be captured there.
>
>
>
> If you cannot identify the path a new call will take through your script,
> I don’t think anyone here will be able to help you much, at least not
> without the entire script.
>
>
>
> Ben Newlin
>
>
>
> *From: *Users <users-bounces at lists.opensips.org> on behalf of Prathibha B
> <prathibhab.tvm at gmail.com>
> *Date: *Friday, April 5, 2024 at 3:42 AM
> *To: *OpenSIPS users mailling list <users at lists.opensips.org>
> *Subject: *Re: [OpenSIPS-Users] external applications
>
> * EXTERNAL EMAIL - Please use caution with links and attachments *
>
>
> ------------------------------
>
> route {
> if($DLG_status == 1)
> xlog("UNCONFIRMED\n");
>
> }
>
>
>
> On Fri, 5 Apr 2024 at 13:09, Prathibha B <prathibhab.tvm at gmail.com> wrote:
>
> I am not getting $DLG_status = UNCONFORMED at the start of the call. Can
> someone help?
>
>
>
>
>
> --
> Regards,
> B.Prathibha
>
--
Regards,
B.Prathibha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240406/ef530076/attachment-0001.html>
More information about the Users
mailing list