THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#456 - "unsupported route type: 64" after calling event route dialog:end
User who did this - Daniel-Constantin Mierla (miconda)
----------
Actually I discovered it was not backported. I just did it now. The commit on master was 4fab97fb54334a55b1fce4e0d2f417fda5727c3a
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=456#comment1568
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#456 - "unsupported route type: 64" after calling event route dialog:end
User who did this - Andrew Pogrebennyk (marduk)
----------
I see, thanks. Was it fixed by commit fbe7347 - dialog: execute internal event_route blocks under local_route type (7 weeks ago) <Daniel-Constantin Mierla> and only this commit?
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=456#comment1567
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#456 - "unsupported route type: 64" after calling event route dialog:end
User who did this - Daniel-Constantin Mierla (miconda)
----------
This should be fixed in branch 4.1, to be part of 4.1.5 next week.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=456#comment1566
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Andrew Pogrebennyk (marduk)
Attached to Project - sip-router
Summary - "unsupported route type: 64" after calling event route dialog:end
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Low
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - We are using event route dialog:end to execute some lua scripts:
event_route[dialog:end]
{
if (!lua_run("del_dlg_profile", "$ci"))
{
xlog("L_ERROR", "Failed to decrease redis counters - R=$ru ID=$ci\n");
}
else
{
xlog("L_INFO", "removed redis counters - R=$ru ID=$ci\n");
}
}
The problem is that when we have a BYE message, which triggers the event route above and is then processed by the loose_route() and finally goes to t_relay(),
Jul 31 15:56:44 prx01a proxy[12447]: NOTICE: <script>: New request - M=BYE R=sip:172.30.52.132:5080;prxroute=1 F=sip:sipwise-test2@172.30.52.103 T=sip:43991001@172.30.52.103 IP=172.17.135.86:41748 (172.30.52.135:5060) ID=0ik1N5ahpzAzCaIQmtMeqkeA1yoK1l4j
Jul 31 15:56:44 prx01a proxy[12447]: INFO: <script>: removed redis counters - R=sip:172.30.52.132:5080;prxroute=1 ID=0ik1N5ahpzAzCaIQmtMeqkeA1yoK1l4j
Jul 31 15:56:44 prx01a proxy[12447]: INFO: <script>: Stop mediaproxy for all branches - R=sip:172.30.52.132:5080;prxroute=1 ID=0ik1N5ahpzAzCaIQmtMeqkeA1yoK1l4j
Jul 31 15:56:44 prx01a proxy[12447]: INFO: <script>: Relaying request, du='<null>' - R=sip:172.30.52.132:5080;prxroute=1 ID=0ik1N5ahpzAzCaIQmtMeqkeA1yoK1l4j
the t_relay fails with "unsupported route type: 64":
Jul 31 15:56:44 prx01a proxy[12447]: : tm [tm.c:1518]: _w_t_relay_to(): ERROR: w_t_relay_to: unsupported route type: 64
it looks like event route dialog:end does not clear breaks internal state of the kamailio process.
When UAC retransmits the BYE there is no event route called and there is no problem.
root@prx01a:~# kamailio -V
version: kamailio 4.1.4 (x86_64/linux)
flags: STATS: Off, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 4MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: unknown
compiled on 20:52:15 Jul 24 2014 with gcc 4.7.2
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=456
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
The key purpose of ITV encryption is to avoid making a pattern of any sort.
If you encrypt same text / packet 10 times you will get completely
different encrypted text / packet each time. This happens due to the fact
that the encryption key changes dynamically with each new encryption done,
see the readme file for more details
https://github.com/mshary/itv/blob/master/README.md
Secondly with v2.0, it uses non-deterministic random source as well as
auto-learning, so it can adopt to new symbols and words encountered while
encrypting and update itself to use them. So technically, it can also be
used for binary data such as RTP, however RTP uses UDP which has
possibility of packet loss and thus not suitable for ITV encryption (at
least for now, this is a hot discussion within my researchers circle and we
are actively looking for a solution for this).
See release notes for v2.0 here,
https://github.com/mshary/itv/releases/tag/v2.0
Anyways, the current target is to use kamailio as SIP proxy and doubango as
SIP client for iPhone and Android. Once it is achieved it will be available
free / open source to public and then it can be actually tested against all
possible voip blocking and sniffing scenarios which we hope it would be
able to solve with minimal possible overhead. So far the prototype works
pretty good in a few voip blocked countries and GSM operators where we have
tested it.
Thank you.
On Wed, Jul 30, 2014 at 5:32 PM, Daniel Tryba <daniel(a)pocos.nl> wrote:
> On Wednesday 30 July 2014 06:37:31 Muhammad Shahzad wrote:
> > Humm, no reply so far, may be because my email was very long and no body
> > bothered to read it all. Anyways, here is the shorter more direct version
> > of it.
>
> I read it all and my only though was: use a VPN.
>
> If someone wants to stop SIP, it has an easy to spot pattern.
> If someone wants to stop VPN, they will drop every non clear connection
> which
> doesn't match a known non-VPN pattern.
>
> If I was afraid of my telco listening in on my SIP dialogs, I'd also want
> to
> encrypt RTP. Which is much more resource intensive than encrypting a few
> SIP
> messages. So if you think standard tls is to intensive you'll also have to
> create some custom lightweight rtp mangling.
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users(a)lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
I could not load the dialog module, because of a linking problem with the symbol destroy_dlg.
Found that it's declared "inline" twice which may cause an issue. With this change, that I don't dare to commit myself, I could load dialog and explore it. Can someone take a look at this, someone that understands dialog and stuff?
This was on OS/X.
Thanks
/O
diff --git a/modules/dialog/dlg_hash.h b/modules/dialog/dlg_hash.h
index 6994256..174ef15 100644
--- a/modules/dialog/dlg_hash.h
+++ b/modules/dialog/dlg_hash.h
@@ -214,7 +214,7 @@ static inline void unlink_unsafe_dlg(dlg_entry_t *d_entry, dlg_cell_t *dlg)
* \brief Destroy a dialog, run callbacks and free memory
* \param dlg destroyed dialog
*/
-inline void destroy_dlg(dlg_cell_t *dlg);
+void destroy_dlg(dlg_cell_t *dlg);
/*!