Re: [SR-Users] Problems establishing SIP signaling between MsTeams and Kamailio

[wvalles]

Hello Rob and Community,

I comment that this configuration if I have it added in my kamailio.cfg in
this way.

event_route[tm:local-request] {

if(is_method("OPTIONS") && $ru =~ "pstnhub.microsoft.com") {
   append_hf("Contact:
\r\n");
}
xlog("L_INFO", "Sent out tm request: $mb\n");
}

In fact I have also followed the guide from
"https://skalatan.de/en/blog/kamailio-sbc-teams;, however I still can't
establish the connection between MsTeams and Kamailio correctly. As I said
in the previous comment, from Kamailio I see that the flag towards MsTeams
is in AP. But from MsTeams I see that the "Sip Options Status" is in
Warning.

Additionally, through Kamailio's sip_trace, I don't see Kamailio's SIP
OPTIONS 200 OK responses to MsTeams. Could you help me by taking a look at
my kamailio.cfg? Maybe there is an error in the configuration or something
additional is missing to correctly complete the signaling between Kamailio
and MsTeams. I attach my "kamailio.cfg". 

Please your support everyone.

Cheers

kamailio.cfg
  



--
Sent from: http://sip-router.1086192.n5.nabble.com/Users-f3.html

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

[SR-Users] Info: Upcoming online events - February 2021

[Daniel-Constantin Mierla]

Hello,

short note to announce a news article listing the upcoming online events
where you can watch presentation related to Kamailio, respectively
FOSDEM and ClueCon TGI. More details at:

  * https://www.kamailio.org/w/2021/01/upcoming-online-events-february-2021/

During this time where the travelling is under heavy restrictions, such
events can be a chance to keep in touch with peers in the RTC space or
learn new usefuk things.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Funding: https://www.paypal.me/dcmierla


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

[SR-Users] Loop with unable to find dialog for xxx

[David VILLAUME]

Hello,

I got some time Ack packets looping on my servers during 4 hours if I don’t 
restart the system ( 4 hours is my dialog timeout).

Jan 27 16:59:02 vma-2 kamailio[4544]: WARNING: { 1 # 
SDvl91b03-576e9e12b1569f0361fceb3625955037-agvh8j0020 * } dialog 
[dlg_handlers.c:1322]: dlg_onroute(): unable to find dialog for ACK with route 
param 'dc2.f24' [717:1071] and call-id 
'SDvl91b03-576e9e12b1569f0361fceb3625955037-agvh8j0020'
Jan 27 16:59:02 vma-2 kamailio[4545]: WARNING: { 1 # 
SDvl91b03-576e9e12b1569f0361fceb3625955037-agvh8j0020 * } dialog 
[dlg_handlers.c:1322]: dlg_onroute(): unable to find dialog for ACK with route 
param 'dc2.f24' [717:1071] and call-id 
'SDvl91b03-576e9e12b1569f0361fceb3625955037-agvh8j0020'
Jan 27 16:59:02 vma-2 kamailio[4545]: WARNING: { 1 # 
SDvl91b03-576e9e12b1569f0361fceb3625955037-agvh8j0020 * } dialog 
[dlg_handlers.c:1322]: dlg_onroute(): unable to find dialog for ACK with route 
param 'dc2.f24' [717:1071] and call-id 
'SDvl91b03-576e9e12b1569f0361fceb3625955037-agvh8j0020'
Jan 27 16:59:02 vma-2 kamailio[4544]: WARNING: { 1 # 
SDvl91b03-576e9e12b1569f0361fceb3625955037-agvh8j0020 * } dialog 
[dlg_handlers.c:1322]: dlg_onroute(): unable to find dialog for ACK with route 
param 'dc2.f24' [717:1071] and call-id 
'SDvl91b03-576e9e12b1569f0361fceb3625955037-agvh8j0020'
Jan 27 16:59:02 vma-2 kamailio[4545]: WARNING: { 1 # 
SDvl91b03-576e9e12b1569f0361fceb3625955037-agvh8j0020 * } dialog 
[dlg_handlers.c:1322]: dlg_onroute(): unable to find dialog for ACK with route 
param 'dc2.f24' [717:1071] and call-id 
'SDvl91b03-576e9e12b1569f0361fceb3625955037-agvh8j0020'


It generates approximatively 2 millions packets per loop.

On the last occurrence I noticed a ‘SIP/2.0 200 canceling’ generated per 
Kamailio before the loop started (which seems uncomon on this host)

Bellow is a screenshot of the beginning of the loop and may dialog and topos 
config.

Has anyone encountered such behavour ?

Regards,
David



[cid:image001.png@01D6F4E2.F68B5140]


modparam("dialog", "dlg_flag", 1)
modparam("dialog", "hash_size", 1024)
modparam("dialog", "default_timeout", 14500)
modparam("dialog", "event_callback", "ksr_dialog_event")
modparam("dialog", "db_url", DBURL_DLG)
modparam("dialog", "db_update_period", 15)
modparam("dialog", "db_mode", 1)


modparam("topos", "storage", "redis")
modparam("topos", "dialog_expire", 14500)
modparam("topos", "contact_host", "PUBLICIP")

modparam("topos_redis", "serverid", "topos")



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

Re: [SR-Users] websocket rd buffer size limit?

[Andrew Chen]

So what engineering is stating is we may need to support up to 65k.  The
video feature to support more video pods will produce large SDP's.

So I got a random MESSAGE to Kamailio to work with TCP 5060 with 70k
content length but when using websocket, it's limited to 64k.

On Wed, Jan 27, 2021 at 5:57 AM Daniel-Constantin Mierla 
wrote:

> Out of curiosity, how large do you expect the sip messages to be? Event
> with webrtc sdp, I haven't seen sip messages getting closer to 64kB...
>
> Cheers,
> Daniel
> On 26.01.21 22:01, Andrew Chen wrote:
>
> Ok thanks.  I also forgot to mention these are websocket SIP calls to the
> Kamailio.
>
> I also ran into a thread after googling is to update the following in
> tls_server.c
>
> #define TLS_RD_MBUF_SZ 65536
> #define TLS_WR_MBUF_SZ 65536
>
> I will try both options.
>
> Thanks again!
>
> On Tue, Jan 26, 2021 at 1:15 PM Daniel-Constantin Mierla <
> mico...@gmail.com> wrote:
>
>> Hello,
>>
>> this seems to be related to the SIP message max size, not to the tcp
>> buffer size.
>>
>> You have to recompile kamailio after changing BUF_SIZE in the
>> src/core/config.h.
>>
>> Cheers,
>> Daniel
>> On 26.01.21 18:43, Andrew Chen wrote:
>>
>> Hey group,
>>
>> I was wondering if there is a way to control the websocket buffer size to
>> support large SIP messages.  I received the following error when sending
>> content-length of 65000
>>
>> 2021-01-26T17:32:19.251408+00:00 sjomainkama50 kamailio[31871]:
>> 109(32008) WARNING: websocket [*ws_frame.c*:482]:
>> decode_and_validate_ws_frame(): message is too long for our buffer size
>> (65535 / 66151)
>>
>>
>> I am assuming this is controlled  by the tcp_rd_buf params which I have
>> set to 131k:
>>
>>
>> *tcp_*rd_buf_size=131072
>>
>>
>> and this is my tcp_wr_buf params:
>>
>> *tcp_*wq_blk_size=131072
>>
>> *tcp_*conn_wq_max=131072
>>
>>
>>
>> Please advise.
>>
>>
>> Thanks.
>>
>>
>> --
>> Andy Chen
>> Sr. Telephony Lead Engineer
>> achen@ fuze.com
>>
>>
>>
>> *Confidentiality Notice: The information contained in this e-mail and any
>> attachments may be confidential. If you are not an intended recipient, you
>> are hereby notified that any dissemination, distribution or copying of
>> this
>> e-mail is strictly prohibited. If you have received this e-mail in error,
>> please notify the sender and permanently delete the e-mail and any
>> attachments immediately. You should not retain, copy or use this e-mail or
>> any attachment for any purpose, nor disclose all or any part of the
>> contents to any other person. Thank you.*
>>
>> ___
>> Kamailio (SER) - Users Mailing 
>> Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
>> --
>> Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- 
>> www.linkedin.com/in/miconda
>> Funding: https://www.paypal.me/dcmierla
>>
>>
>
> --
> Andy Chen
> Sr. Telephony Lead Engineer
> 415 516 5535 (M)
> achen@ fuze.com
>
>
> *Confidentiality Notice: The information contained in this e-mail and any
> attachments may be confidential. If you are not an intended recipient, you
> are hereby notified that any dissemination, distribution or copying of this
> e-mail is strictly prohibited. If you have received this e-mail in error,
> please notify the sender and permanently delete the e-mail and any
> attachments immediately. You should not retain, copy or use this e-mail or
> any attachment for any purpose, nor disclose all or any part of the
> contents to any other person. Thank you.*
>
> --
> Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- 
> www.linkedin.com/in/miconda
> Funding: https://www.paypal.me/dcmierla
>
>

-- 
Andy Chen
Sr. Telephony Lead Engineer
415 516 5535 (M)
achen@ fuze.com

-- 
*Confidentiality Notice: The information contained in this e-mail and any
attachments may be confidential. If you are not an intended recipient, you
are hereby notified that any dissemination, distribution or copying of this
e-mail is strictly prohibited. If you have received this e-mail in error,
please notify the sender and permanently delete the e-mail and any
attachments immediately. You should not retain, copy or use this e-mail or
any attachment for any purpose, nor disclose all or any part of the
contents to any other person. Thank you.*
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] kamailio 5.4.3 ubuntu 20.04 tls - http_async_client

[Filippo Graziola]

Hello,

here are the results for ssl packages (dpkg -l | grep ssl):

ii  libcrypt-openssl-bignum-perl 0.09-1build3
 amd64Perl module to access OpenSSL multiprecision integer
arithmetic libraries
ii  libcrypt-openssl-random-perl 0.15-1build2
 amd64module to access the OpenSSL pseudo-random number generator
ii  libcrypt-openssl-rsa-perl0.31-1build1
 amd64module for RSA encryption using OpenSSL
ii  libevent-openssl-2.1-7:amd64 2.1.11-stable-1
amd64Asynchronous event notification library (openssl)
ii  libgnutls-openssl27:amd643.6.13-2ubuntu1.3
amd64GNU TLS library - OpenSSL wrapper
ii  libssl-dev:amd64 1.1.1f-1ubuntu2.1
amd64Secure Sockets Layer toolkit - development files
ii  libssl1.1:amd64  1.1.1f-1ubuntu2.1
amd64Secure Sockets Layer toolkit - shared libraries
ii  libwavpack1:amd645.2.0-1ubuntu0.1
 amd64audio codec (lossy and lossless) - library
ii  libxmlsec1-openssl:amd64 1.2.28-2
 amd64Openssl engine for the XML security library
ii  libzstd1:amd64   1.4.4+dfsg-3
 amd64fast lossless compression algorithm
ii  openssl  1.1.1f-1ubuntu2.1
amd64Secure Sockets Layer toolkit - cryptographic utility
ii  perl-openssl-defaults:amd64  4
amd64version compatibility baseline for Perl OpenSSL packages
ii  python3-openssl  19.0.0-1build1
 all  Python 3 wrapper around the OpenSSL library
ii  ssl-cert 1.0.39
 all  simple debconf wrapper for OpenSSL

here is the result of ldd on tls.so:

 linux-vdso.so.1 (0x7ffd687d6000)
libssl.so.1.1 => /lib/x86_64-linux-gnu/libssl.so.1.1 (0x7f9feaf1c000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x7f9feaef9000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f9fead07000)
libcrypto.so.1.1 => /lib/x86_64-linux-gnu/libcrypto.so.1.1
(0x7f9feaa31000)
/lib64/ld-linux-x86-64.so.2 (0x7f9feb071000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f9feaa2b000)

thanks
Filippo


Il giorno mer 27 gen 2021 alle ore 13:11 Daniel-Constantin Mierla <
mico...@gmail.com> ha scritto:

> Hello,
>
> can you give more details about libssl on Ubuntu 20.04? The version (apt
> show libssl, or apt search libssl, ...), eventually the ldd over the tls.so
> kamailio module.
>
> Cheers,
> Daniel
> On 26.01.21 16:10, Filippo Graziola wrote:
>
> Hello,
>
> thanks for the fast reply, I just tried kamailio (5.4.3) from kamailio
> repo on debian buster, self-signed certificates, same minimal
> configuration. No error on start, so it seems specific for ubuntu.
>
> Il giorno mar 26 gen 2021 alle ore 15:39 Daniel-Constantin Mierla <
> mico...@gmail.com> ha scritto:
>
>> Hello,
>>
>> would you be able to test on Debian 10 (maybe using docker or virtual
>> machine/virtualbox) and see if you get the same issue?
>>
>> I do not have Ubuntu 20.04 at hand and I haven't encountered any issue
>> lately with tls on Debian 10. In this way we can rule out if it is specific
>> to Ubuntu version of the libraries or not.
>>
>> Cheers,
>> Daniel
>> On 26.01.21 15:06, Filippo Graziola wrote:
>>
>> Hi all,
>> I have an issue related (my guess) to tls and http_async_client module
>> that result in a segmentation fault and a not correct handle of tls
>> connections.
>>
>> First with only tls module loaded, not forked:
>>
>>  0(1021) INFO:  [core/tcp_main.c:4983]: init_tcp(): using epoll_lt
>> as the io watch method (auto detected)
>>  0(1021) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import
>> bind_ob - maybe module is not loaded
>>  0(1021) INFO: rr [rr_mod.c:185]: mod_init(): outbound module not
>> available
>>  0(1021) INFO: tls [tls_mod.c:389]: mod_init(): With ECDH-Support!
>>  0(1021) INFO: tls [tls_mod.c:392]: mod_init(): With Diffie Hellman
>>  0(1021) WARNING: tls [tls_init.c:784]: tls_h_mod_init_f(): openssl bug
>> #1491 (crash/mem leaks on low memory) workaround enabled (on low memory tls
>> operations will fail preemptively) with free memory thresholds 4718592 and
>> 2359296 bytes
>>  0(1021) INFO:  [core/cfg/cfg_ctx.c:595]: cfg_set_now():
>> tls.low_mem_threshold1 has been changed to 4718592
>>  0(1021) INFO:  [core/cfg/cfg_ctx.c:595]: cfg_set_now():
>> tls.low_mem_threshold2 has been changed to 2359296
>>  0(1021) INFO:  [main.c:2833]: main(): processes (at least): 9 -
>> shm size: 67108864 - pkg size: 67108864
>>  0(1021) INFO:  [core/udp_server.c:154]:
>> probe_max_receive_buffer(): SO_RCVBUF is initially 212992
>>  0(1021) INFO:  [core/udp_server.c:206]:
>> probe_max_receive_buffer(): SO_RCVBUF is finally 425984
>>  0(1021) INFO: tls [tls_domain.c:305]: ksr_tls_fill_missing():
>> TLSs: tls_method=12
>>  0(1021) INFO: tls [tls_domain.c:317]: ksr_tls_fill_missing():
>> TLSs: certificate='/etc/kamailio/fullchain.pem'
>>  0(1021) INFO: tls 

Re: [SR-Users] Problems establishing SIP signaling between MsTeams and Kamailio

[rob.van.den.bulk]

https://skalatan.de/en/blog/kamailio-sbc-teams

event_route[tm:local-request] {

if(is_method("OPTIONS") && $ru =~ "pstnhub.microsoft.com") {
   append_hf("Contact:
\r\n");
}
xlog("L_INFO", "Sent out tm request: $mb\n");
}

-Oorspronkelijk bericht-
Van: sr-users  Namens wvalles
Verzonden: woensdag 27 januari 2021 01:21
Aan: sr-us...@lists.sip-router.org
Onderwerp: Re: [SR-Users] Problems establishing SIP signaling between
MsTeams and Kamailio

Hello Rob and Community,

After a while, I finally got the connection from my Kamailio server to
MsTeams and I can validate that the connection to MsTeams is in AP.

[root @ kamailio-server kamailio] # kamcmd dispatcher.list | egrep "URI |
FLAGS"
URI: sip: sip.pstnhub.microsoft.com;
transport = tls
FLAGS: AP

However, from the admin panel of MsTeams (Direct Routing) I see that the
connection to my sbc "sbc.netvoiceperu.com" is with TLS connectivity status
in "Active" but the SIP options status is in "Warning".

I have made calls from MsTeams thinking that the SIP options status would
change to "active" but it is still in "Warning" state. On the other hand, I
have enabled a siptrace in Kamailio and verify that the SIP OPTIONS from
kamailio are being sent in the following format to MsTeams.

OPTIONS sip: sip.pstnhub.microsoft.com; transport = tls SIP / 2.0
Via: SIP / 2.0 / TLS
161.35.44.66:5061;branch=z9hG4bKea07.52224687.0
To: 
From: ; tag =
d3569c818b500aeb8c373426e76c2884-81763c71
CSeq: 10 OPTIONS
Call-ID: 13ea237a751e0c48-9148@161.35.44.66
Max-Forwards: 70
Content-Length: 0
User-Agent: kamailio (5.4.0 (x86_64 / linux))

As you can see, the SIP OPTIONS sent from Kamailio to MsTeams does not
contain the "Contact" field, which in theory said "Contact" field should
have been added by Kamailio according to the configuration added in
kamailio.cfg

event_route [tm: local-request] {
sip_trace ();
if (is_method ("OPTIONS") && $ ru = ~ "pstnhub.microsoft.com") {
   append_hf ("Contact:  \ r \ n");
}
xlog ("L_INFO", "Sent out tm request: $ mb \ n"); }

As additional information, I inform you that I also managed to observe the
SIP OPTIONS that MsTeams sends to Kamailio.

OPTIONS sip: sbc.netvoiceperu.com: 5061; transport = tls SIP / 2.0
FROM: ; tag =
f1bdeb5f-662f-4544-a436-e9aa9ad78da4
TO: 
CSEQ: 1 OPTIONS
CALL-ID: c47e2782-16c3-49cb-8931-24e9709d260a
MAX-FORWARDS: 70
VIA: SIP / 2.0 / TLS 52.114.75.24:5061;branch=z9hG4bK48b0e6be
CONTACT: 
CONTENT-LENGTH: 0
USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2021.1.15.7 i.EUWE.10
ALLOW: INVITE, ACK, OPTIONS, CANCEL, BYE, NOTIFY

However I don't see the 200 OK SIP responses from Kamailio to MsTeams.

I think this may be the reason why I see the SIP OPTIONS status in "Warning"
from the MsTeams panel. Maybe the contact field is not being added in the
SIP OPTIONS messages that Kamailio sends to MsTeams and for that reason I
don't see 200OK responses from MsTeams.

Could you help me solve this please.

Cheers




--
Sent from: http://sip-router.1086192.n5.nabble.com/Users-f3.html

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


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

Re: [SR-Users] kamailio 5.4.3 ubuntu 20.04 tls - http_async_client

[Daniel-Constantin Mierla]

Hello,

can you give more details about libssl on Ubuntu 20.04? The version (apt
show libssl, or apt search libssl, ...), eventually the ldd over the
tls.so kamailio module.

Cheers,
Daniel

On 26.01.21 16:10, Filippo Graziola wrote:
> Hello,
>
> thanks for the fast reply, I just tried kamailio (5.4.3) from kamailio
> repo on debian buster, self-signed certificates, same minimal
> configuration. No error on start, so it seems specific for ubuntu.
>
> Il giorno mar 26 gen 2021 alle ore 15:39 Daniel-Constantin Mierla
> mailto:mico...@gmail.com>> ha scritto:
>
> Hello,
>
> would you be able to test on Debian 10 (maybe using docker or
> virtual machine/virtualbox) and see if you get the same issue?
>
> I do not have Ubuntu 20.04 at hand and I haven't encountered any
> issue lately with tls on Debian 10. In this way we can rule out if
> it is specific to Ubuntu version of the libraries or not.
>
> Cheers,
> Daniel
>
> On 26.01.21 15:06, Filippo Graziola wrote:
>> Hi all,
>> I have an issue related (my guess) to tls and http_async_client
>> module that result in a segmentation fault and a not correct
>> handle of tls connections.
>>
>> First with only tls module loaded, not forked:
>>
>>  0(1021) INFO:  [core/tcp_main.c:4983]: init_tcp(): using
>> epoll_lt as the io watch method (auto detected)
>>  0(1021) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable
>> to import bind_ob - maybe module is not loaded
>>  0(1021) INFO: rr [rr_mod.c:185]: mod_init(): outbound module not
>> available
>>  0(1021) INFO: tls [tls_mod.c:389]: mod_init(): With ECDH-Support!
>>  0(1021) INFO: tls [tls_mod.c:392]: mod_init(): With Diffie Hellman
>>  0(1021) WARNING: tls [tls_init.c:784]: tls_h_mod_init_f():
>> openssl bug #1491 (crash/mem leaks on low memory) workaround
>> enabled (on low memory tls operations will fail preemptively)
>> with free memory thresholds 4718592 and 2359296 bytes
>>  0(1021) INFO:  [core/cfg/cfg_ctx.c:595]: cfg_set_now():
>> tls.low_mem_threshold1 has been changed to 4718592
>>  0(1021) INFO:  [core/cfg/cfg_ctx.c:595]: cfg_set_now():
>> tls.low_mem_threshold2 has been changed to 2359296
>>  0(1021) INFO:  [main.c:2833]: main(): processes (at
>> least): 9 - shm size: 67108864 - pkg size: 67108864
>>  0(1021) INFO:  [core/udp_server.c:154]:
>> probe_max_receive_buffer(): SO_RCVBUF is initially 212992
>>  0(1021) INFO:  [core/udp_server.c:206]:
>> probe_max_receive_buffer(): SO_RCVBUF is finally 425984
>>  0(1021) INFO: tls [tls_domain.c:305]: ksr_tls_fill_missing():
>> TLSs: tls_method=12
>>  0(1021) INFO: tls [tls_domain.c:317]: ksr_tls_fill_missing():
>> TLSs: certificate='/etc/kamailio/fullchain.pem'
>>  0(1021) INFO: tls [tls_domain.c:324]: ksr_tls_fill_missing():
>> TLSs: ca_list='(null)'
>>  0(1021) INFO: tls [tls_domain.c:331]: ksr_tls_fill_missing():
>> TLSs: crl='(null)'
>>  0(1021) INFO: tls [tls_domain.c:334]: ksr_tls_fill_missing():
>> TLSs: require_certificate=0
>>  0(1021) INFO: tls [tls_domain.c:342]: ksr_tls_fill_missing():
>> TLSs: cipher_list='(null)'
>>  0(1021) INFO: tls [tls_domain.c:349]: ksr_tls_fill_missing():
>> TLSs: private_key='/etc/kamailio/privkey.pem'
>>  0(1021) INFO: tls [tls_domain.c:352]: ksr_tls_fill_missing():
>> TLSs: verify_certificate=0
>>  0(1021) INFO: tls [tls_domain.c:356]: ksr_tls_fill_missing():
>> TLSs: verify_depth=9
>>  0(1021) INFO: tls [tls_domain.c:359]: ksr_tls_fill_missing():
>> TLSs: verify_client=0
>>  0(1021) NOTICE: tls [tls_domain.c:1105]: ksr_tls_fix_domain():
>> registered server_name callback handler for socket [:0],
>> server_name='' ...
>>  0(1021) INFO: tls [tls_domain.c:711]: set_verification():
>> TLSs: No client certificate required and no checks performed
>>  0(1021) INFO: tls [tls_domain.c:305]: ksr_tls_fill_missing():
>> TLSc: tls_method=20
>>  0(1021) INFO: tls [tls_domain.c:317]: ksr_tls_fill_missing():
>> TLSc: certificate='(null)'
>>  0(1021) INFO: tls [tls_domain.c:324]: ksr_tls_fill_missing():
>> TLSc: ca_list='(null)'
>>  0(1021) INFO: tls [tls_domain.c:331]: ksr_tls_fill_missing():
>> TLSc: crl='(null)'
>>  0(1021) INFO: tls [tls_domain.c:334]: ksr_tls_fill_missing():
>> TLSc: require_certificate=0
>>  0(1021) INFO: tls [tls_domain.c:342]: ksr_tls_fill_missing():
>> TLSc: cipher_list='(null)'
>>  0(1021) INFO: tls [tls_domain.c:349]: ksr_tls_fill_missing():
>> TLSc: private_key='(null)'
>>  0(1021) INFO: tls [tls_domain.c:352]: ksr_tls_fill_missing():
>> TLSc: verify_certificate=0
>>  0(1021) INFO: tls [tls_domain.c:356]: ksr_tls_fill_missing():
>> TLSc: verify_depth=9
>>  0(1021) INFO: tls [tls_domain.c:359]: ksr_tls_fill_missing():
>> TLSc: verify_client=0
>>  0(1021) INFO: tls [tls_domain.c:714]: 

Re: [SR-Users] websocket rd buffer size limit?

[Daniel-Constantin Mierla]

Out of curiosity, how large do you expect the sip messages to be? Event
with webrtc sdp, I haven't seen sip messages getting closer to 64kB...

Cheers,
Daniel

On 26.01.21 22:01, Andrew Chen wrote:
> Ok thanks.  I also forgot to mention these are websocket SIP calls to
> the Kamailio.
>
> I also ran into a thread after googling is to update the following in
> tls_server.c
>
> #define TLS_RD_MBUF_SZ65536
> #define TLS_WR_MBUF_SZ65536
>
> I will try both options.
>
> Thanks again!
>
> On Tue, Jan 26, 2021 at 1:15 PM Daniel-Constantin Mierla
> mailto:mico...@gmail.com>> wrote:
>
> Hello,
>
> this seems to be related to the SIP message max size, not to the
> tcp buffer size.
>
> You have to recompile kamailio after changing BUF_SIZE in the
> src/core/config.h.
>
> Cheers,
> Daniel
>
> On 26.01.21 18:43, Andrew Chen wrote:
>> Hey group,
>>
>> I was wondering if there is a way to control the websocket buffer
>> size to support large SIP messages.  I received the following
>> error when sending content-length of 65000
>>
>> 2021-01-26T17:32:19.251408+00:00 sjomainkama50 kamailio[31871]:
>> 109(32008) WARNING: websocket [*ws_frame.c*:482]:
>> decode_and_validate_ws_frame(): message is too long for our
>> buffer size (65535 / 66151)
>>
>>
>> I am assuming this is controlled  by the tcp_rd_buf params which
>> I have set to 131k:
>>
>>
>> *tcp_*rd_buf_size=131072
>>
>>
>> and this is my tcp_wr_buf params:
>>
>> *tcp_*wq_blk_size=131072
>>
>> *tcp_*conn_wq_max=131072
>>
>>
>>
>> Please advise.
>>
>>
>> Thanks.
>>
>>
>> -- 
>> Andy Chen
>> Sr. Telephony Lead Engineer
>> achen@ fuze.com 
>>
>>
>>
>> *Confidentiality Notice: The information contained in this e-mail
>> and any
>> attachments may be confidential. If you are not an intended
>> recipient, you
>> are hereby notified that any dissemination, distribution or
>> copying of this
>> e-mail is strictly prohibited. If you have received this e-mail
>> in error,
>> please notify the sender and permanently delete the e-mail and any
>> attachments immediately. You should not retain, copy or use this
>> e-mail or
>> any attachment for any purpose, nor disclose all or any part of the
>> contents to any other person. Thank you.*
>>
>> ___
>> 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 
> Funding: https://www.paypal.me/dcmierla 
>
>
>
> -- 
> Andy Chen
> Sr. Telephony Lead Engineer
> 415 516 5535 (M)
> achen@ fuze.com 
>
>
> *Confidentiality Notice: The information contained in this e-mail and any
> attachments may be confidential. If you are not an intended recipient, you
> are hereby notified that any dissemination, distribution or copying of
> this
> e-mail is strictly prohibited. If you have received this e-mail in error,
> please notify the sender and permanently delete the e-mail and any
> attachments immediately. You should not retain, copy or use this e-mail or
> any attachment for any purpose, nor disclose all or any part of the
> contents to any other person. Thank you.* 

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Funding: https://www.paypal.me/dcmierla

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

[SR-Users] UACREG to many Asterisk

[Javier Valencia]

Hi there!

Go ahead I apologize for my English.

I have a Kamailio 5.4 with the DISPATCHER module and UAC enabled (for 
remote REGISTER), the DISPATCHER has several SETIDs, and they have one 
or more Asterisk balanced behind it.


In Kamalio script, when an endpoint does REGISTER, I enable the REGISTER 
of the UAC module. And when it expires or expires=0 I disable the 
REGISTER in the UAC module.


In the UACREG table in the database, L_UUID (unique key), L_USERNAME, 
R_USERNAME, and AUTH_USERNAME have the same value. For example CST100EXT100.


Knowing that the DISPATCHER and UAC modules have no relationship, but 
that when a SETID has several balanced Asterisks, how can I make the UAC 
module send the REGISTER to all the Asterisks of a SETID?


Clarifications;

1.- I cannot update the Asterisk, which are currently in version 11. 
They do not support PATH.


2.- I can modify the content of the UACREG table so that l_uuid has a 
suffix '_X'.


3.- Call jsonrpc_exec several times to enable the REGISTER in the UAC 
module.


(diff emulated)
< jsonrpc_exec ('{"id": 1, "jsonrpc": "2.0", "method": "uac.reg_enable", 
"params": ["l_uuid", "s: $ au"]}') ;
> jsonrpc_exec ('{"id": 1, "jsonrpc": "2.0", "method": 
"uac.reg_enable", "params": ["l_uuid", "s: $ au_1"]}') ;
> jsonrpc_exec ('{"id": 1, "jsonrpc": "2.0", "method": 
"uac.reg_enable", "params": ["l_uuid", "s: $ au_2"]}') ;
> jsonrpc_exec ('{"id": 1, "jsonrpc": "2.0", "method": 
"uac.reg_enable", "params": ["l_uuid", "s: $ au_3"]}') ;


But I want to know if there is any more elegant way to do this.

Cheers, JV

--
Logo 


Javier Valencia | CTO
Centro de Negocios Martín Buendía
Camino de las Cañadas, nº 1C, Portal 1, 2ºG
29649 Mijas (Málaga)

#   951562080 (T)  | 687486759 (M) 
#   www.voiper.es 



AVISO LEGAL
---

Este mensaje contiene información confidencial destinada para ser leída
exclusivamente por el destinatario. Queda prohibida la reproducción,
publicación, divulgación, total o parcial del mensaje así como el uso no
autorizados por el emisor. En caso de recibir el mensaje por error, se ruega
su comunicación al remitente lo antes posible. Por favor, indique
inmediatamente si usted o su empresa no aceptan comunicaciones de este tipo
por Internet.

Las opiniones, conclusiones y demás información incluida en este mensaje que
no esté relacionada con asuntos profesionales de SMART RECARGAS, S.L, se
entenderá que nunca se ha dado, ni está respaldado por el mismo.

Responsable del Tratamiento de Datos

SMART RECARGAS , SL
Camino de las Cañadas, 1C PORTAL 1 2º G
29651 MIJAS COSTA (MALAGA)

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

[SR-Users] event_route[core:receive-parse-error] missing from docs

[Henning Westerholt]

Hello,

I noticed that the core "event_route[core:receive-parse-error]" was missing 
from the cookbook, so I have added it there.

https://www.kamailio.org/wiki/cookbooks/devel/core#event_route

Cheers,

Henning

--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://gilawa.com

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

Re: [SR-Users] Kamailio as MS-Teams SBC

[Davide Zanichelli]

Hello

im still having trouble with ack and bye ...

in inbound call my teams client stuck in "calling"

and seems that dont like my ack



tag: snd
pid: 131292
process: 6
time: 1611683788.220244
date: Tue Jan 26 17:56:28 2021
proto: tls ipv4
srcip: 69.172.96.197
srcport: 5061
dstip: 52.114.75.24
dstport: 5061

ACK sip:+1...@sip.pstnhub.microsoft.com:5061;transport=tls SIP/2.0
Record-Route: 
Via: SIP/2.0/TLS 69.172.96.197:5061
;branch=z9hG4bKaf91.b6d38c1afb72b2dd4847cc3f7d99d698.0
v:SIP/2.0/UDP
185.132.68.116;received=185.132.68.116;rport=5060;branch=z9hG4bKZXc92a9KDyUFg
Max-Forwards:69
f:"Davide Zanichelli";tag=DKU70jvS4K86p
t:;tag=25f6b5d613cb478aa1d495a391860101
i:9493b287-a2f6-4891-859c-231994af46d6
CSeq:31288100 ACK
m:
l:0



Il giorno gio 21 gen 2021 alle ore 09:18 Davide Zanichelli <
dav.zaniche...@gmail.com> ha scritto:

> Hello
> i dont understand why teams reply me 481 !!!
>
> Thanks
> davide
>
> 
> 
> tag: snd
> pid: 102385
> process: 6
> time: 1611216424.610918
> date: Thu Jan 21 08:07:04 2021
> proto: tls ipv4
> srcip: 69.172.96.197
> srcport: 5061
> dstip: 52.114.75.24
> dstport: 5061
> 
> BYE sip:+1...@sip.pstnhub.microsoft.com:5061;transport=tls SIP/2.0
> Record-Route:  ;transport=tls;r2=on;ftag=7NFv9B0B3K6QB;lr>
> Record-Route: 
> Via: SIP/2.0/TLS 69.172.96.197:5061
> ;branch=z9hG4bK02e5.5f6af95bad6e683b84ebf07b31a7755f.0
> v:SIP/2.0/UDP
> 185.132.68.116;received=185.132.68.116;rport=5060;branch=z9hG4bK9j0gNmmXj9Q6D
> Max-Forwards:69
> f:"Davide Zanichelli";tag=7NFv9B0B3K6QB
> t: ;user=phone>;tag=da13ee6f8a0f4277b597fa9fd40a783f
> i:781214b3-d662-1239-fc81-9259e6a86632
> CSeq:31054416 BYE
> User-Agent:FreeSWITCH-mod_sofia/1.6.20~64bit
>
> Allow:INVITE,ACK,BYE,CANCEL,OPTIONS,MESSAGE,INFO,UPDATE,REGISTER,REFER,PRACK,NOTIFY,PUBLISH,SUBSCRIBE
> k:precondition,100rel,path,replaces
> Reason:Q.850;cause=16;text="NORMAL_CLEARING"
> l:0
>
> 
> 
> tag: rcv
> pid: 102417
> process: 38
> time: 1611216424.629297
> date: Thu Jan 21 08:07:04 2021
> proto: tls ipv4
> srcip: 52.114.75.24
> srcport: 5061
> dstip: 69.172.96.197
> dstport: 5061
> 
> SIP/2.0 481 Call Leg/Transaction Does Not Exist
> FROM: "Davide Zanichelli";tag=7NFv9B0B3K6QB
> TO:  ;user=phone>;tag=da13ee6f8a0f4277b597fa9fd40a783f
> CSEQ: 31054416 BYE
> CALL-ID: 781214b3-d662-1239-fc81-9259e6a86632
> VIA: SIP/2.0/TLS 
> 69.172.96.197:5061;branch=z9hG4bK02e5.5f6af95bad6e683b84ebf07b31a7755f.0,SIP/2.0/UDP
> 185.132.68.116;received=185.132.68.116;branch=z9hG4bK9j0gNmmXj9Q6D;rport=5060
> REASON: Q.850;cause=95;text="90301fea-2875-4a99-b6f0-25e35ff07710;Call leg
> unavailable"
> CONTENT-LENGTH: 0
> ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY
> SERVER: Microsoft.PSTNHub.SIPProxy v.2021.1.15.7 i.EUWE.8
>
> Il giorno mer 20 gen 2021 alle ore 18:03 Richard Fuchs 
> ha scritto:
>
>> On 19/01/2021 07.11, Daniel-Constantin Mierla wrote:
>> > Hello,
>> >
>> > I built rtpengine deb packages for debian just a few days ago and all
>> > went fine. I used the file mr8.5.1.5.tar.gz from the github releases
>> > of rtpengine project.
>> >
>> > However, I noticed that some past releases fail to build because of
>> > the tests. I had to edit a bit the Makefile to disable the tests target.
>>
>> If some of the tests are causing a problem, you can let me know and I'll
>> see if they can be defused to make things work for everybody.
>>
>> Cheers
>>
>>
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users