Hello,

are the other headers (Via, Record-Route) handled by the topos module for OPTIONS request? Is only Contact header left?

Regarding topoh: there can be some enhancements to try to shorten the size of those values, from what I know, short text compressing can get 20-30% compression rate, but not always and I am not sure will actually help with those SBCes. Have you able to figure out the size of the header values when they fail to handle the sip messages?

On the other hand, I am eager to see how those SBC are going to do when STIR/SHAKEN is added (soon by US/North America carriers), the Identity header is quite large...

Cheers,
Daniel

On 31.03.20 15:11, Enzo wrote:
 
Hello,
 
I just realisied I made a mistake and send this reply to the wrong mail address.
 
The OPTIONS are keepalive-request and out-of-dialog. So topos is not able to manage these?
 
I also tried topoh. Topoh was able to mask the contact header even in out-of-dialog OPTIONS. 
The main reason to switch to topos is the line=sr-parameter. Some calls got a very long line=sr-parameter which lead to problems with different SBC vendors.
 
line=sr-N6IAzBqLOBFsWLZfz.P7M.PszBjAWByXoSI7g.ulNJuzWqI0kqKlCxWwk.t5j6KskhrfW4u1RqtHPq31KLssWquZM.phWIp0MwpPjKpd..g-Oqs0..gSoF47.9pWotgMgLsWgqud.qfhOq46.RfP.SN7.jfWoUId.9r9NqudCEfWkFuC.RfsRU0Kg9e5Ctp0owpIWFcsmwtzkmvb>
 
 
Is there any way to reduce the length of the line=sr-parameter?
 
Thanks!
 
Best Regards
Enzo
 
 
Gesendet: Donnerstag, 12. März 2020 um 08:40 Uhr
Von: "Daniel-Constantin Mierla" <miconda@gmail.com>
An: "Kamailio (SER) - Users Mailing List" <sr-users@lists.kamailio.org>, Enzo <voiper@gmx.net>
Betreff: Re: [SR-Users] Use topos module to hide contact in OPTIONS request

Hello,

the module aimed at supporting topology hiding for calls. Is the OPTIONS part of a dialog or out-of-dialog (like a keepalive request)?

Cheers,
Daniel

On 11.03.20 16:02, Enzo wrote:
Hi all
I have a problem with the topos module. The contact header in OPTIONS request is not changed. It is working fine with INVITE. Is there any special configuration with OPTIONS?
 
I am using:
version: kamailio 5.3.2 (x86_64/linux) 7ba545
 
This is the debug log:
Mar 11 15:52:13 kamtest /usr/local/kamailio/sbin/kamailio[55606]: DEBUG: topos [tps_msg.c:934]: tps_request_sent(): handling outgoing request (0, 0)
Mar 11 15:52:13 kamtest /usr/local/kamailio/sbin/kamailio[55606]: DEBUG: topos [tps_msg.c:376]: tps_pack_message(): compacted headers - x_via1: [SIP/2.0/UDP 122.123.145.146;branch=z9hG4bK8ee.c6d59104d9f494f8ba1f75ed3f9ec8cf.0](79) - x_via2: [SIP/2.0/UDP 172.26.52.104:5060;branch=z9hG4bK00E0F5150A04105449BBEB83377A](73) - x_vbranch1: [z9hG4bK8ee.c6d59104d9f494f8ba1f75ed3f9ec8cf.0](45)
Mar 11 15:52:13 kamtest /usr/local/kamailio/sbin/kamailio[55606]: DEBUG: topos [tps_msg.c:485]: tps_pack_message(): compacted headers - a_rr: [](0) - b_rr: [](0) - s_rr: [](0)
Mar 11 15:52:13 kamtest /usr/local/kamailio/sbin/kamailio[55606]: DEBUG: topos [tps_msg.c:490]: tps_pack_message(): compacted headers - as_contact: [](0) - bs_contact: [](0)
Mar 11 15:52:13 kamtest /usr/local/kamailio/sbin/kamailio[55606]: DEBUG: topos [tps_storage.c:126]: tps_storage_lock_get(): tps lock get: 337
Mar 11 15:52:13 kamtest /usr/local/kamailio/sbin/kamailio[55606]: DEBUG: topos_redis [topos_redis_storage.c:764]: tps_redis_load_branch(): loading branch record for [b:x:z9hG4bK8ee.c6d59104d9f494f8ba1f75ed3f9ec8cf.0]
Mar 11 15:52:13 kamtest /usr/local/kamailio/sbin/kamailio[55606]: DEBUG: topos_redis [topos_redis_storage.c:782]: tps_redis_load_branch(): hmap with key [b:x:z9hG4bK8ee.c6d59104d9f494f8ba1f75ed3f9ec8cf.0] not found
Mar 11 15:52:13 kamtest /usr/local/kamailio/sbin/kamailio[55606]: DEBUG: topos [tps_storage.c:391]: tps_storage_link_msg(): downstream: yes - acontact: [sip:172.26.52.104:5060] - bcontact: []
Mar 11 15:52:13 kamtest /usr/local/kamailio/sbin/kamailio[55606]: WARNING: topos [tps_storage.c:434]: tps_storage_record(): no local address - do record routing for all initial requests
Mar 11 15:52:13 kamtest /usr/local/kamailio/sbin/kamailio[55606]: INFO: topos_redis [topos_redis_storage.c:163]: tps_redis_insert_dialog(): no uuid for this message
Mar 11 15:52:13 kamtest /usr/local/kamailio/sbin/kamailio[55606]: ERROR: topos [tps_storage.c:445]: tps_storage_record(): failed to store
Mar 11 15:52:13 kamtest /usr/local/kamailio/sbin/kamailio[55606]: DEBUG: topos [tps_storage.c:138]: tps_storage_lock_release(): tps lock release: 337
Mar 11 15:52:13 kamtest /usr/local/kamailio/sbin/kamailio[55606]: DEBUG: topos [topos_mod.c:449]: tps_msg_sent(): new outbound buffer generated

This is the config I use:
modparam("ndb_redis", "server", "name=srv8;addr=127.0.0.1;port=6379;db=8")
modparam("topos", "storage", "redis")
modparam("topos_redis", "serverid", "srv8")
modparam("topos", "branch_expire", 14400)
modparam("topos", "dialog_expire", 14400)
 
Best Regards
Enzo
 
 
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com

_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda