Hello,
you can find the module functions usually with grep:
henning@app01.dev ~/repositories/kamailio/src/modules/seas$ grep "as_relay_t" *
seas.c:static int w_as_relay_t(struct sip_msg *msg, char *as_name, char *foo);
seas.c: {"as_relay_t", (cmd_function)w_as_relay_t, 1, fixup_as_relay,
seas.c:static int w_as_relay_t(struct sip_msg *msg, char *entry, char *foo)
The last one is the implementation. You can also increase the log level of the existing debug statements or just increase the log level of the server to debug.
Cheers,
Henning
From: sr-users <sr-users-bounces@lists.kamailio.org>
On Behalf Of Daniel Paape
Sent: Tuesday, October 5, 2021 10:23 PM
To: sr-users@lists.kamailio.org
Subject: Re: [SR-Users] seas module
Henning
That’s exactly the problem. I never return from the as_relay_t() in the config file. I don’t know which file to look in to see where the decision is made to exit from the config script execution.
I would like to use this module for a project at work and would be willing to sort of “take it under my wing” but I need to justify it. And right now I am thwarted.
From: Henning Westerholt <hw@skalatan.de>
Sent: Tuesday, October 5, 2021 3:14 PM
To: Kamailio (SER) - Users Mailing List <sr-users@lists.kamailio.org>
Cc: Daniel Paape <dpaape@amtelco.com>
Subject: RE: seas module
Hi Daniel,
your approach sounds good. I would continue with adding some debug statements to your cfg and also to the seas module code (especially for the as_relay_t(..)). It could be that it just returned
the wrong value, as you already guessed. Just update this thread with more information that you found out, it can be then also fixed of course in the repository.
Cheers,
Henning
From: sr-users <sr-users-bounces@lists.kamailio.org>
On Behalf Of Daniel Paape
Sent: Tuesday, October 5, 2021 10:05 PM
To: sr-users@lists.kamailio.org
Subject: Re: [SR-Users] seas module
Henning, I suspected as much, however I think that this has less to do with the seas module and more to do with just an external module returning. My guess is that somehow execution is returning
(0) to whatever is executing the route block and then the config script exits. I’ve been adding debug to the source for the last two days and I just don’t see where it’s terminating.
The receive_msg function (core receive.c) returns 0 after processing the sip request. The udp_rcv_loop (core udp_server.c) then looks like it should drop through to the error label and return
-1. I don’t see where it goes from here and suspect that it was a spawned thread of execution.
From: Henning Westerholt <hw@skalatan.de>
Sent: Tuesday, October 5, 2021 2:46 PM
To: Kamailio (SER) - Users Mailing List <sr-users@lists.kamailio.org>
Cc: Daniel Paape <dpaape@amtelco.com>
Subject: RE: seas module
Hello Daniel,
the seas module is unfortunately not much used nowadays, at least according to the (lack of) discussions on this list. You probably need to dig into the code and investigate by yourself to some
extent. Maybe your requirements can be fulfilled by another, more commonly used module?
Cheers,
Henning
From: sr-users <sr-users-bounces@lists.kamailio.org>
On Behalf Of Daniel Paape
Sent: Tuesday, October 5, 2021 9:40 PM
To: sr-users@lists.kamailio.org
Subject: [SR-Users] seas module
I am having some difficulties with the seas module under Kam 5.5.2. If my application server is not connected then the config file script below never returns
if (!as_relay_t (“myserver”)) {
Xlog (“LM_NOTICE”, “myserver not connected\n”);
}
A diagnostic in the “seas.c” file does report that the app server is not connected, but the one above is never printed. Any help here would be appreciated.
This email is intended only for the use of the party to which it is addressed and may contain information that is privileged, confidential, or protected by law. If you are not the intended recipient you are hereby notified that any dissemination, copying or
distribution of this email or its contents is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer.
This email is intended only for the use of the party to which it is addressed and may contain information that is privileged, confidential, or protected by law. If you are not the intended recipient you are hereby notified that any dissemination, copying or
distribution of this email or its contents is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer.
This email is intended only for the use of the party to which it is addressed and may contain information that is privileged, confidential, or protected by law. If you are not the intended recipient you are hereby notified that any dissemination, copying or
distribution of this email or its contents is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer.