subject:"\[SR\-Users\] Kamailio as SBC"

Re: [SR-Users] Kamailio like SBC with Teams

2020-04-24 Thread sip user

Hi, I have it works now..

In this scenario:

Teams -> Kamailio -> Asterisk

When I call from Teams to any number I redirect all to Asterisk extension
registrated over Kamailio.
I received the call in Asterisk and I can work... but when I received the
call, not received the number dialled, always received to s extension in
Asterisk.

Can i rewrite the number dialled and send it to my Asterisk extension, and
in my Asterisk see the number dialed?

Thanks for all

El mar., 21 abr. 2020 a las 19:05, sip user ()
escribió:

> Sorry..
>
> I received the invite with the dial number.. But i do not received de
> ACK..
>
> Can I check any way if I received the ACK?
>
> Thanks
>
> El martes, 21 de abril de 2020, sip user  escribió:
>
>> Thanks Sergiu..
>>
>> It works for me.
>>
>> Now, when I make a call from Teams, in syslog I see:
>>
>> Apr 21 10:39:39 vps793907 /usr/sbin/kamailio[20651]: DEBUG: 
>> [parser/msg_parser.c:623]: parse_msg(): SIP Request:
>> Apr 21 10:39:39 vps793907 /usr/sbin/kamailio[20651]: DEBUG: 
>> [parser/msg_parser.c:625]: parse_msg():  method:  
>> Apr 21 10:39:39 vps793907 /usr/sbin/kamailio[20651]: DEBUG: 
>> [parser/msg_parser.c:627]: parse_msg():  uri: > :5061;user=phone;transport=tls>
>> Apr 21 10:39:39 vps793907 /usr/sbin/kamailio[20651]: DEBUG: 
>> [parser/msg_parser.c:629]: parse_msg():  version: 
>>
>> But now How can I do to "transfer" the call to a kamailio user or to my
>> Asterisk?
>>
>> Thanks for all
>>
>> El mar., 21 abr. 2020 a las 6:18, Sergiu Pojoga ()
>> escribió:
>>
>>> Check out below thread, it explains it all.
>>>
>>> https://lists.kamailio.org/pipermail/sr-users/2020-March/108684.html
>>>
>>> On Mon, Apr 20, 2020 at 3:24 PM sip user  wrote:
>>>
 Sorry.. Im a bit loose in this one...

 So, ive use letsencrypy to generate the certificate, and the CA, how i
 have to generate?

 Thanks

 El lun., 20 abr. 2020 19:06, Sergiu Pojoga 
 escribió:

> ca_list= /etc/letsencrypt/live/FQND/chain.pem
>
> Is that pointing to your Root CA certificate? I highly doubt it.
> That's probably the reason why you get "tls_read_f(): TLS
> write:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate
> verify failed"
>
> On Mon, Apr 20, 2020 at 11:53 AM sip user 
> wrote:
>
>> Hi..
>>
>> Thank you all very much for answering me.
>>
>> I have made many test:
>>
>> First, I've installed ssl cert with letsencrypt, like
>> https://www.fredposner.com/1836/kamailio-tls-and-letsencrypt/, this
>> one i made it before.
>>
>> I've configured tls.cfg like:
>>
>> [server:default]
>> method = TLSv1.2
>> verify_certificate = yes
>> require_certificate = yes
>> private_key = /etc/letsencrypt/live/FQND/privkey.pem
>> certificate = /etc/letsencrypt/live/FQDN/fullchain.pem
>> ca_list= /etc/letsencrypt/live/FQND/chain.pem
>>
>> [client:default]
>> method = TLSv1.2
>> verify_certificate = yes
>> require_certificate = yes
>> private_key = /etc/letsencrypt/live/FQND/privkey.pem
>> certificate = /etc/letsencrypt/live/FQDN/fullchain.pem
>> ca_list= /etc/letsencrypt/live/FQND/chain.pem
>>
>> In syslog I received:
>>
>> Apr 20 17:31:25 vps793907 /usr/sbin/kamailio[8481]: INFO:

Re: [SR-Users] Kamailio like SBC with Teams

2020-04-21 Thread sip user

Sorry..

I received the invite with the dial number.. But i do not received de ACK..

Can I check any way if I received the ACK?

Thanks

El martes, 21 de abril de 2020, sip user  escribió:

> Thanks Sergiu..
>
> It works for me.
>
> Now, when I make a call from Teams, in syslog I see:
>
> Apr 21 10:39:39 vps793907 /usr/sbin/kamailio[20651]: DEBUG: 
> [parser/msg_parser.c:623]: parse_msg(): SIP Request:
> Apr 21 10:39:39 vps793907 /usr/sbin/kamailio[20651]: DEBUG: 
> [parser/msg_parser.c:625]: parse_msg():  method:  
> Apr 21 10:39:39 vps793907 /usr/sbin/kamailio[20651]: DEBUG: 
> [parser/msg_parser.c:627]: parse_msg():  uri:  :5061;user=phone;transport=tls>
> Apr 21 10:39:39 vps793907 /usr/sbin/kamailio[20651]: DEBUG: 
> [parser/msg_parser.c:629]: parse_msg():  version: 
>
> But now How can I do to "transfer" the call to a kamailio user or to my
> Asterisk?
>
> Thanks for all
>
> El mar., 21 abr. 2020 a las 6:18, Sergiu Pojoga ()
> escribió:
>
>> Check out below thread, it explains it all.
>>
>> https://lists.kamailio.org/pipermail/sr-users/2020-March/108684.html
>>
>> On Mon, Apr 20, 2020 at 3:24 PM sip user  wrote:
>>
>>> Sorry.. Im a bit loose in this one...
>>>
>>> So, ive use letsencrypy to generate the certificate, and the CA, how i
>>> have to generate?
>>>
>>> Thanks
>>>
>>> El lun., 20 abr. 2020 19:06, Sergiu Pojoga  escribió:
>>>
 ca_list= /etc/letsencrypt/live/FQND/chain.pem

 Is that pointing to your Root CA certificate? I highly doubt it.
 That's probably the reason why you get "tls_read_f(): TLS
 write:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate
 verify failed"

 On Mon, Apr 20, 2020 at 11:53 AM sip user  wrote:

> Hi..
>
> Thank you all very much for answering me.
>
> I have made many test:
>
> First, I've installed ssl cert with letsencrypt, like
> https://www.fredposner.com/1836/kamailio-tls-and-letsencrypt/, this
> one i made it before.
>
> I've configured tls.cfg like:
>
> [server:default]
> method = TLSv1.2
> verify_certificate = yes
> require_certificate = yes
> private_key = /etc/letsencrypt/live/FQND/privkey.pem
> certificate = /etc/letsencrypt/live/FQDN/fullchain.pem
> ca_list= /etc/letsencrypt/live/FQND/chain.pem
>
> [client:default]
> method = TLSv1.2
> verify_certificate = yes
> require_certificate = yes
> private_key = /etc/letsencrypt/live/FQND/privkey.pem
> certificate = /etc/letsencrypt/live/FQDN/fullchain.pem
> ca_list= /etc/letsencrypt/live/FQND/chain.pem
>
> In syslog I received:
>
> Apr 20 17:31:25 vps793907 /usr/sbin/kamailio[8481]: INFO:

Re: [SR-Users] Kamailio like SBC with Teams

2020-04-21 Thread sip user

Thanks Sergiu..

It works for me.

Now, when I make a call from Teams, in syslog I see:

Apr 21 10:39:39 vps793907 /usr/sbin/kamailio[20651]: DEBUG: 
[parser/msg_parser.c:623]: parse_msg(): SIP Request:
Apr 21 10:39:39 vps793907 /usr/sbin/kamailio[20651]: DEBUG: 
[parser/msg_parser.c:625]: parse_msg():  method:  
Apr 21 10:39:39 vps793907 /usr/sbin/kamailio[20651]: DEBUG: 
[parser/msg_parser.c:627]: parse_msg():  uri: 
Apr 21 10:39:39 vps793907 /usr/sbin/kamailio[20651]: DEBUG: 
[parser/msg_parser.c:629]: parse_msg():  version: 

But now How can I do to "transfer" the call to a kamailio user or to my
Asterisk?

Thanks for all

El mar., 21 abr. 2020 a las 6:18, Sergiu Pojoga ()
escribió:

> Check out below thread, it explains it all.
>
> https://lists.kamailio.org/pipermail/sr-users/2020-March/108684.html
>
> On Mon, Apr 20, 2020 at 3:24 PM sip user  wrote:
>
>> Sorry.. Im a bit loose in this one...
>>
>> So, ive use letsencrypy to generate the certificate, and the CA, how i
>> have to generate?
>>
>> Thanks
>>
>> El lun., 20 abr. 2020 19:06, Sergiu Pojoga  escribió:
>>
>>> ca_list= /etc/letsencrypt/live/FQND/chain.pem
>>>
>>> Is that pointing to your Root CA certificate? I highly doubt it.
>>> That's probably the reason why you get "tls_read_f(): TLS
>>> write:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate
>>> verify failed"
>>>
>>> On Mon, Apr 20, 2020 at 11:53 AM sip user  wrote:
>>>
 Hi..

 Thank you all very much for answering me.

 I have made many test:

 First, I've installed ssl cert with letsencrypt, like
 https://www.fredposner.com/1836/kamailio-tls-and-letsencrypt/, this
 one i made it before.

 I've configured tls.cfg like:

 [server:default]
 method = TLSv1.2
 verify_certificate = yes
 require_certificate = yes
 private_key = /etc/letsencrypt/live/FQND/privkey.pem
 certificate = /etc/letsencrypt/live/FQDN/fullchain.pem
 ca_list= /etc/letsencrypt/live/FQND/chain.pem

 [client:default]
 method = TLSv1.2
 verify_certificate = yes
 require_certificate = yes
 private_key = /etc/letsencrypt/live/FQND/privkey.pem
 certificate = /etc/letsencrypt/live/FQDN/fullchain.pem
 ca_list= /etc/letsencrypt/live/FQND/chain.pem

 In syslog I received:

 Apr 20 17:31:25 vps793907 /usr/sbin/kamailio[8481]: INFO:

Re: [SR-Users] Kamailio like SBC with Teams

2020-04-20 Thread Sergiu Pojoga

Check out below thread, it explains it all.

https://lists.kamailio.org/pipermail/sr-users/2020-March/108684.html

On Mon, Apr 20, 2020 at 3:24 PM sip user  wrote:

> Sorry.. Im a bit loose in this one...
>
> So, ive use letsencrypy to generate the certificate, and the CA, how i
> have to generate?
>
> Thanks
>
> El lun., 20 abr. 2020 19:06, Sergiu Pojoga  escribió:
>
>> ca_list= /etc/letsencrypt/live/FQND/chain.pem
>>
>> Is that pointing to your Root CA certificate? I highly doubt it.
>> That's probably the reason why you get "tls_read_f(): TLS
>> write:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate
>> verify failed"
>>
>> On Mon, Apr 20, 2020 at 11:53 AM sip user  wrote:
>>
>>> Hi..
>>>
>>> Thank you all very much for answering me.
>>>
>>> I have made many test:
>>>
>>> First, I've installed ssl cert with letsencrypt, like
>>> https://www.fredposner.com/1836/kamailio-tls-and-letsencrypt/, this one
>>> i made it before.
>>>
>>> I've configured tls.cfg like:
>>>
>>> [server:default]
>>> method = TLSv1.2
>>> verify_certificate = yes
>>> require_certificate = yes
>>> private_key = /etc/letsencrypt/live/FQND/privkey.pem
>>> certificate = /etc/letsencrypt/live/FQDN/fullchain.pem
>>> ca_list= /etc/letsencrypt/live/FQND/chain.pem
>>>
>>> [client:default]
>>> method = TLSv1.2
>>> verify_certificate = yes
>>> require_certificate = yes
>>> private_key = /etc/letsencrypt/live/FQND/privkey.pem
>>> certificate = /etc/letsencrypt/live/FQDN/fullchain.pem
>>> ca_list= /etc/letsencrypt/live/FQND/chain.pem
>>>
>>> In syslog I received:
>>>
>>> Apr 20 17:31:25 vps793907 /usr/sbin/kamailio[8481]: INFO:

Re: [SR-Users] Kamailio like SBC with Teams

2020-04-20 Thread sip user

Sorry.. Im a bit loose in this one...

So, ive use letsencrypy to generate the certificate, and the CA, how i have
to generate?

Thanks

El lun., 20 abr. 2020 19:06, Sergiu Pojoga  escribió:

> ca_list= /etc/letsencrypt/live/FQND/chain.pem
>
> Is that pointing to your Root CA certificate? I highly doubt it.
> That's probably the reason why you get "tls_read_f(): TLS
> write:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate
> verify failed"
>
> On Mon, Apr 20, 2020 at 11:53 AM sip user  wrote:
>
>> Hi..
>>
>> Thank you all very much for answering me.
>>
>> I have made many test:
>>
>> First, I've installed ssl cert with letsencrypt, like
>> https://www.fredposner.com/1836/kamailio-tls-and-letsencrypt/, this one
>> i made it before.
>>
>> I've configured tls.cfg like:
>>
>> [server:default]
>> method = TLSv1.2
>> verify_certificate = yes
>> require_certificate = yes
>> private_key = /etc/letsencrypt/live/FQND/privkey.pem
>> certificate = /etc/letsencrypt/live/FQDN/fullchain.pem
>> ca_list= /etc/letsencrypt/live/FQND/chain.pem
>>
>> [client:default]
>> method = TLSv1.2
>> verify_certificate = yes
>> require_certificate = yes
>> private_key = /etc/letsencrypt/live/FQND/privkey.pem
>> certificate = /etc/letsencrypt/live/FQDN/fullchain.pem
>> ca_list= /etc/letsencrypt/live/FQND/chain.pem
>>
>> In syslog I received:
>>
>> Apr 20 17:31:25 vps793907 /usr/sbin/kamailio[8481]: INFO:

Re: [SR-Users] Kamailio like SBC with Teams

2020-04-20 Thread Sergiu Pojoga

ca_list= /etc/letsencrypt/live/FQND/chain.pem

Is that pointing to your Root CA certificate? I highly doubt it.
That's probably the reason why you get "tls_read_f(): TLS
write:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate
verify failed"

On Mon, Apr 20, 2020 at 11:53 AM sip user  wrote:

> Hi..
>
> Thank you all very much for answering me.
>
> I have made many test:
>
> First, I've installed ssl cert with letsencrypt, like
> https://www.fredposner.com/1836/kamailio-tls-and-letsencrypt/, this one i
> made it before.
>
> I've configured tls.cfg like:
>
> [server:default]
> method = TLSv1.2
> verify_certificate = yes
> require_certificate = yes
> private_key = /etc/letsencrypt/live/FQND/privkey.pem
> certificate = /etc/letsencrypt/live/FQDN/fullchain.pem
> ca_list= /etc/letsencrypt/live/FQND/chain.pem
>
> [client:default]
> method = TLSv1.2
> verify_certificate = yes
> require_certificate = yes
> private_key = /etc/letsencrypt/live/FQND/privkey.pem
> certificate = /etc/letsencrypt/live/FQDN/fullchain.pem
> ca_list= /etc/letsencrypt/live/FQND/chain.pem
>
> In syslog I received:
>
> Apr 20 17:31:25 vps793907 /usr/sbin/kamailio[8481]: INFO:

Re: [SR-Users] Kamailio like SBC with Teams

2020-04-20 Thread sip user

Hi..

Thank you all very much for answering me.

I have made many test:

First, I've installed ssl cert with letsencrypt, like
https://www.fredposner.com/1836/kamailio-tls-and-letsencrypt/, this one i
made it before.

I've configured tls.cfg like:

[server:default]
method = TLSv1.2
verify_certificate = yes
require_certificate = yes
private_key = /etc/letsencrypt/live/FQND/privkey.pem
certificate = /etc/letsencrypt/live/FQDN/fullchain.pem
ca_list= /etc/letsencrypt/live/FQND/chain.pem

[client:default]
method = TLSv1.2
verify_certificate = yes
require_certificate = yes
private_key = /etc/letsencrypt/live/FQND/privkey.pem
certificate = /etc/letsencrypt/live/FQDN/fullchain.pem
ca_list= /etc/letsencrypt/live/FQND/chain.pem

In syslog I received:

Apr 20 17:31:25 vps793907 /usr/sbin/kamailio[8481]: INFO:

Re: [SR-Users] Kamailio like SBC with Teams

2020-04-18 Thread Yuriy Nasida

after real write: c=
>>> 0x7f90f2438f80 n=1468 fd=9
>>> > Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
>>> [tcp_main.c:2551]: tcpconn_do_send(): tcp_send: buf=
>>> > Apr 15 11:11:41 vps793907 kamailio[23122]: #026#003#003
>>> > Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
>>> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9c1700, 9, 2,
>>> 0x7f90f2438f80), fd_no=1
>>> > Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
>>> [tcp_read.c:296]: tcp_read_data(): EOF on 0x7f90f2438f80, FD 9
>>> > Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
>>> [tcp_read.c:1291]: tcp_read_req(): tcp_read_req: EOF
>>> > Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
>>> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9c1700, 9, -1, 0x10)
>>> fd_no=2 called
>>> > Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
>>> [tcp_read.c:1434]: release_tcpconn(): releasing con 0x7f90f2438f80, state
>>> -1, fd=9, id=30
>>> > Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
>>> [tcp_read.c:1435]: release_tcpconn():  extra_data 0x7f90f2432b40
>>> > Apr 15 11:11:42 vps793907 kamailio[23122]: 13(23167) DEBUG: 
>>> [tcp_main.c:3331]: handle_tcp_child(): handle_tcp_child: reader response=
>>> 7f90f2438f80, -1 from 1
>>> > Apr 15 11:11:42 vps793907 kamailio[23122]: 13(23167) DEBUG: tls
>>> [tls_server.c:604]: tls_h_close(): Closing SSL connection 0x7f90f2432b40
>>> >
>>> > I don't see any different.
>>> >
>>> > I know that the module is loaded because I see:
>>> >
>>> > exec: *** cfgtrace:request_route=[DEFAULT_ROUTE]
>>> c=[/etc/kamailio/kamailio.cfg] l=486 a=5 n=route
>>> >
>>> > When I restart kamailio, but when I "launch" a call from Teams to my
>>> Kamailio I only see that.
>>> >
>>> > To configure it, I follow
>>> https://skalatan.de/en/blog/kamailio-sbc-teams.. But I cannot make it
>>> works..
>>> >
>>> > Any more thing that i can test or do??
>>> >
>>> > Thanks
>>> >
>>> > El jue., 16 abr. 2020 a las 14:20, Nasida Yuriy ()
>>> escribió:
>>> >>
>>> >> Wow, so many people want to configure kamailio with MS. First of all
>>> i think you need to get sip debug  between kamailio and MS. Kamilio has
>>> module to save sip traces. This way you will get sip debug decrypted.
>>> >>
>>> >>
>>> >> 
>>> >> От: sr-users  от имени sip user
>>> 
>>> >> Отправлено: 16 апреля 2020 г. 10:19
>>> >> Кому: sr-users@lists.kamailio.org 
>>> >> Тема: [SR-Users] Kamailio like SBC with Teams
>>> >>
>>> >> Hello good morning ... I am new to this list and I was starting to
>>> mess with Kamailio, mainly to set it up as SBC against Teams, in this case.
>>> >>
>>> >> But I can't get it to work for me. If I launch a call from the Teams,
>>> in the Kamailio I see:
>>> >>
>>> >> 1.- In syslog:
>>> >>
>>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
>>> [ip_addr.c:243]: print_ip(): tcpconn_new: new tcp connection: 52.114.7.24
>>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
>>> [tcp_main.c:1073]: tcpconn_new(): tcpconn_new: on port 4160, type 3
>>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
>>> [tcp_main.c:1382]: tcpconn_add(): tcpconn_add: hashes: 171:1857:1187, 30
>>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
>>> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0xa1f240, 23, 2,
>>> 0x7f90f2438f80), fd_no=17
>>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
>>> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0xa1f240, 23, -1, 0x0)
>>> fd_no=18 called
>>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
>>> [tcp_main.c:4219]: handle_tcpconn_ev(): tcp: DBG: sending to child, events 1
>>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
>>> [tcp_main.c:3902]: send2child(): selected tcp worker 1 10(23159) for
>>> activity on [tls:SBC_IP:5061], 0x7f90f2438f80
>>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
>&g

Re: [SR-Users] Kamailio like SBC with Teams

2020-04-17 Thread Sergiu Pojoga

mailio[23122]: 10(23159) DEBUG: 
>>> [tcp_main.c:2551]: tcpconn_do_send(): tcp_send: buf=
>>> > Apr 15 11:11:41 vps793907 kamailio[23122]: #026#003#003
>>> > Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
>>> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9c1700, 9, 2,
>>> 0x7f90f2438f80), fd_no=1
>>> > Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
>>> [tcp_read.c:296]: tcp_read_data(): EOF on 0x7f90f2438f80, FD 9
>>> > Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
>>> [tcp_read.c:1291]: tcp_read_req(): tcp_read_req: EOF
>>> > Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
>>> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9c1700, 9, -1, 0x10)
>>> fd_no=2 called
>>> > Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
>>> [tcp_read.c:1434]: release_tcpconn(): releasing con 0x7f90f2438f80, state
>>> -1, fd=9, id=30
>>> > Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
>>> [tcp_read.c:1435]: release_tcpconn():  extra_data 0x7f90f2432b40
>>> > Apr 15 11:11:42 vps793907 kamailio[23122]: 13(23167) DEBUG: 
>>> [tcp_main.c:3331]: handle_tcp_child(): handle_tcp_child: reader response=
>>> 7f90f2438f80, -1 from 1
>>> > Apr 15 11:11:42 vps793907 kamailio[23122]: 13(23167) DEBUG: tls
>>> [tls_server.c:604]: tls_h_close(): Closing SSL connection 0x7f90f2432b40
>>> >
>>> > I don't see any different.
>>> >
>>> > I know that the module is loaded because I see:
>>> >
>>> > exec: *** cfgtrace:request_route=[DEFAULT_ROUTE]
>>> c=[/etc/kamailio/kamailio.cfg] l=486 a=5 n=route
>>> >
>>> > When I restart kamailio, but when I "launch" a call from Teams to my
>>> Kamailio I only see that.
>>> >
>>> > To configure it, I follow
>>> https://skalatan.de/en/blog/kamailio-sbc-teams.. But I cannot make it
>>> works..
>>> >
>>> > Any more thing that i can test or do??
>>> >
>>> > Thanks
>>> >
>>> > El jue., 16 abr. 2020 a las 14:20, Nasida Yuriy ()
>>> escribió:
>>> >>
>>> >> Wow, so many people want to configure kamailio with MS. First of all
>>> i think you need to get sip debug  between kamailio and MS. Kamilio has
>>> module to save sip traces. This way you will get sip debug decrypted.
>>> >>
>>> >>
>>> >> 
>>> >> От: sr-users  от имени sip user
>>> 
>>> >> Отправлено: 16 апреля 2020 г. 10:19
>>> >> Кому: sr-users@lists.kamailio.org 
>>> >> Тема: [SR-Users] Kamailio like SBC with Teams
>>> >>
>>> >> Hello good morning ... I am new to this list and I was starting to
>>> mess with Kamailio, mainly to set it up as SBC against Teams, in this case.
>>> >>
>>> >> But I can't get it to work for me. If I launch a call from the Teams,
>>> in the Kamailio I see:
>>> >>
>>> >> 1.- In syslog:
>>> >>
>>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
>>> [ip_addr.c:243]: print_ip(): tcpconn_new: new tcp connection: 52.114.7.24
>>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
>>> [tcp_main.c:1073]: tcpconn_new(): tcpconn_new: on port 4160, type 3
>>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
>>> [tcp_main.c:1382]: tcpconn_add(): tcpconn_add: hashes: 171:1857:1187, 30
>>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
>>> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0xa1f240, 23, 2,
>>> 0x7f90f2438f80), fd_no=17
>>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
>>> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0xa1f240, 23, -1, 0x0)
>>> fd_no=18 called
>>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
>>> [tcp_main.c:4219]: handle_tcpconn_ev(): tcp: DBG: sending to child, events 1
>>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
>>> [tcp_main.c:3902]: send2child(): selected tcp worker 1 10(23159) for
>>> activity on [tls:SBC_IP:5061], 0x7f90f2438f80
>>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
>>> [tcp_read.c:1507]: handle_io(): received n=8 con=0x7f90f2438f80, fd=9
>>> >> Apr 15 11:11:41

Re: [SR-Users] Kamailio like SBC with Teams

2020-04-17 Thread sip user

_req: EOF
>> > Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
>> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9c1700, 9, -1, 0x10)
>> fd_no=2 called
>> > Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
>> [tcp_read.c:1434]: release_tcpconn(): releasing con 0x7f90f2438f80, state
>> -1, fd=9, id=30
>> > Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
>> [tcp_read.c:1435]: release_tcpconn():  extra_data 0x7f90f2432b40
>> > Apr 15 11:11:42 vps793907 kamailio[23122]: 13(23167) DEBUG: 
>> [tcp_main.c:3331]: handle_tcp_child(): handle_tcp_child: reader response=
>> 7f90f2438f80, -1 from 1
>> > Apr 15 11:11:42 vps793907 kamailio[23122]: 13(23167) DEBUG: tls
>> [tls_server.c:604]: tls_h_close(): Closing SSL connection 0x7f90f2432b40
>> >
>> > I don't see any different.
>> >
>> > I know that the module is loaded because I see:
>> >
>> > exec: *** cfgtrace:request_route=[DEFAULT_ROUTE]
>> c=[/etc/kamailio/kamailio.cfg] l=486 a=5 n=route
>> >
>> > When I restart kamailio, but when I "launch" a call from Teams to my
>> Kamailio I only see that.
>> >
>> > To configure it, I follow
>> https://skalatan.de/en/blog/kamailio-sbc-teams.. But I cannot make it
>> works..
>> >
>> > Any more thing that i can test or do??
>> >
>> > Thanks
>> >
>> > El jue., 16 abr. 2020 a las 14:20, Nasida Yuriy ()
>> escribió:
>> >>
>> >> Wow, so many people want to configure kamailio with MS. First of all i
>> think you need to get sip debug  between kamailio and MS. Kamilio has
>> module to save sip traces. This way you will get sip debug decrypted.
>> >>
>> >>
>> >> 
>> >> От: sr-users  от имени sip user <
>> sipuser...@gmail.com>
>> >> Отправлено: 16 апреля 2020 г. 10:19
>> >> Кому: sr-users@lists.kamailio.org 
>> >> Тема: [SR-Users] Kamailio like SBC with Teams
>> >>
>> >> Hello good morning ... I am new to this list and I was starting to
>> mess with Kamailio, mainly to set it up as SBC against Teams, in this case.
>> >>
>> >> But I can't get it to work for me. If I launch a call from the Teams,
>> in the Kamailio I see:
>> >>
>> >> 1.- In syslog:
>> >>
>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
>> [ip_addr.c:243]: print_ip(): tcpconn_new: new tcp connection: 52.114.7.24
>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
>> [tcp_main.c:1073]: tcpconn_new(): tcpconn_new: on port 4160, type 3
>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
>> [tcp_main.c:1382]: tcpconn_add(): tcpconn_add: hashes: 171:1857:1187, 30
>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
>> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0xa1f240, 23, 2,
>> 0x7f90f2438f80), fd_no=17
>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
>> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0xa1f240, 23, -1, 0x0)
>> fd_no=18 called
>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
>> [tcp_main.c:4219]: handle_tcpconn_ev(): tcp: DBG: sending to child, events 1
>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
>> [tcp_main.c:3902]: send2child(): selected tcp worker 1 10(23159) for
>> activity on [tls:SBC_IP:5061], 0x7f90f2438f80
>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
>> [tcp_read.c:1507]: handle_io(): received n=8 con=0x7f90f2438f80, fd=9
>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: tls
>> [tls_server.c:184]: tls_complete_init(): Using TLS domain TLSs
>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: tls
>> [tls_domain.c:700]: sr_ssl_ctx_info_callback(): SSL handshake started
>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
>> [tcp_main.c:2516]: tcpconn_do_send(): tcp_send: sending...
>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
>> [tcp_main.c:2550]: tcpconn_do_send(): tcp_send: after real write: c=
>> 0x7f90f2438f80 n=1468 fd=9
>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
>> [tcp_main.c:2551]: tcpconn_do_send(): tcp_send: buf=
>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: #026#003#003
>> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
>> [io_wait

Re: [SR-Users] Kamailio like SBC with Teams

2020-04-17 Thread Yuriy Nasida

Wow, so many people want to configure kamailio with MS. First of all i
think you need to get sip debug  between kamailio and MS. Kamilio has
module to save sip traces. This way you will get sip debug decrypted.

On Thu, 16 Apr 2020 at 10:26, sip user  wrote:

> Hello good morning ... I am new to this list and I was starting to mess
> with Kamailio, mainly to set it up as SBC against Teams, in this case.
>
> But I can't get it to work for me. If I launch a call from the Teams, in
> the Kamailio I see:
>
> 1.- In syslog:
>
> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
> [ip_addr.c:243]: print_ip(): tcpconn_new: new tcp connection: 52.114.7.24
> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
> [tcp_main.c:1073]: tcpconn_new(): tcpconn_new: on port 4160, type 3
> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
> [tcp_main.c:1382]: tcpconn_add(): tcpconn_add: hashes: 171:1857:1187, 30
> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0xa1f240, 23, 2,
> 0x7f90f2438f80), fd_no=17
> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0xa1f240, 23, -1, 0x0)
> fd_no=18 called
> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
> [tcp_main.c:4219]: handle_tcpconn_ev(): tcp: DBG: sending to child, events 1
> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
> [tcp_main.c:3902]: send2child(): selected tcp worker 1 10(23159) for
> activity on [tls:SBC_IP:5061], 0x7f90f2438f80
> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
> [tcp_read.c:1507]: handle_io(): received n=8 con=0x7f90f2438f80, fd=9
> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: tls
> [tls_server.c:184]: tls_complete_init(): Using TLS domain TLSs
> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: tls
> [tls_domain.c:700]: sr_ssl_ctx_info_callback(): SSL handshake started
> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
> [tcp_main.c:2516]: tcpconn_do_send(): tcp_send: sending...
> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
> [tcp_main.c:2550]: tcpconn_do_send(): tcp_send: after real write: c=
> 0x7f90f2438f80 n=1468 fd=9
> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
> [tcp_main.c:2551]: tcpconn_do_send(): tcp_send: buf=
> Apr 15 11:11:41 vps793907 kamailio[23122]: #026#003#003
> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9c1700, 9, 2,
> 0x7f90f2438f80), fd_no=1
> Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
> [tcp_read.c:296]: tcp_read_data(): EOF on 0x7f90f2438f80, FD 9
> Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
> [tcp_read.c:1291]: tcp_read_req(): tcp_read_req: EOF
> Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9c1700, 9, -1, 0x10)
> fd_no=2 called
> Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
> [tcp_read.c:1434]: release_tcpconn(): releasing con 0x7f90f2438f80, state
> -1, fd=9, id=30
> Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
> [tcp_read.c:1435]: release_tcpconn():  extra_data 0x7f90f2432b40
> Apr 15 11:11:42 vps793907 kamailio[23122]: 13(23167) DEBUG: 
> [tcp_main.c:3331]: handle_tcp_child(): handle_tcp_child: reader response=
> 7f90f2438f80, -1 from 1
> Apr 15 11:11:42 vps793907 kamailio[23122]: 13(23167) DEBUG: tls
> [tls_server.c:604]: tls_h_close(): Closing SSL connection 0x7f90f2432b40
>
> 2.- With TCPDUMP:
>
> 11:13:09.311797 IP SBC_IP .1024 > SBC_IP .eu.sip-tls: Flags [S], seq
> 261244614, win 64240, options [mss 1440,nop,wscale 8,nop,nop,sackOK],
> length 0
> 11:13:09.311898 IP  SBC_IP .eu.sip-tls > 52.114.76.76.1024: Flags [S.],
> seq 812357247, ack 261244615, win 29200, options [mss
> 1460,nop,nop,sackOK,nop,wscale 7], length 0
> 11:13:09.340358 IP 52.114.76.76.1024 >  SBC_IP .eu.sip-tls: Flags [.], ack
> 1, win 2053, length 0
> 11:13:09.340560 IP 52.114.76.76.1024 > SBC_IP .eu.sip-tls: Flags [P.], seq
> 1:187, ack 1, win 2053, length 186
> 11:13:09.340578 IP SBC_IP .eu.sip-tls > 52.114.76.76.1024: Flags [.], ack
> 187, win 237, length 0
> 11:13:09.341361 IP SBC_IP .eu.sip-tls > 52.114.76.76.1024: Flags [P.], seq
> 1:1469, ack 187, win 237, length 1468
> 11:13:09.369606 IP 52.114.76.76.1024 > SBC_IP .eu.sip-tls: Flags [.], ack
> 1469, win 2053, length 0
> 11:13:12.451498 IP 52.114.7.24.1216 > SBC_IP .eu.sip-tls: Flags [S], seq
> 309084204, win 64240, options [mss 1440,nop,wscale 8,nop,nop,sackOK],
> length 0
> 11:13:12.451587 IP SBC_IP .eu.sip-tls > 52.114.7.24.1216: Flags [S.], seq
> 3275066862, ack 309084205, win 29200, options [mss
> 1460,nop,nop,sackOK,nop,wscale 7], length 0
> 11:13:12.707119 IP 52.114.7.24.1216 > SBC_IP .eu.sip-tls: Flags [.], ack
> 1, win 2053, length 0
> 11:13:12.707311 IP 52.114.7.24.1216 > SBC_IP .eu.sip-tls: Flags [P.],

Re: [SR-Users] Kamailio like SBC with Teams

2020-04-16 Thread Sergiu Pojoga

UTE]
> c=[/etc/kamailio/kamailio.cfg] l=486 a=5 n=route
> >
> > When I restart kamailio, but when I "launch" a call from Teams to my
> Kamailio I only see that.
> >
> > To configure it, I follow https://skalatan.de/en/blog/kamailio-sbc-teams..
> But I cannot make it works..
> >
> > Any more thing that i can test or do??
> >
> > Thanks
> >
> > El jue., 16 abr. 2020 a las 14:20, Nasida Yuriy ()
> escribió:
> >>
> >> Wow, so many people want to configure kamailio with MS. First of all i
> think you need to get sip debug  between kamailio and MS. Kamilio has
> module to save sip traces. This way you will get sip debug decrypted.
> >>
> >>
> >> 
> >> От: sr-users  от имени sip user <
> sipuser...@gmail.com>
> >> Отправлено: 16 апреля 2020 г. 10:19
> >> Кому: sr-users@lists.kamailio.org 
> >> Тема: [SR-Users] Kamailio like SBC with Teams
> >>
> >> Hello good morning ... I am new to this list and I was starting to mess
> with Kamailio, mainly to set it up as SBC against Teams, in this case.
> >>
> >> But I can't get it to work for me. If I launch a call from the Teams,
> in the Kamailio I see:
> >>
> >> 1.- In syslog:
> >>
> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
> [ip_addr.c:243]: print_ip(): tcpconn_new: new tcp connection: 52.114.7.24
> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
> [tcp_main.c:1073]: tcpconn_new(): tcpconn_new: on port 4160, type 3
> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
> [tcp_main.c:1382]: tcpconn_add(): tcpconn_add: hashes: 171:1857:1187, 30
> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0xa1f240, 23, 2,
> 0x7f90f2438f80), fd_no=17
> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0xa1f240, 23, -1, 0x0)
> fd_no=18 called
> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
> [tcp_main.c:4219]: handle_tcpconn_ev(): tcp: DBG: sending to child, events 1
> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
> [tcp_main.c:3902]: send2child(): selected tcp worker 1 10(23159) for
> activity on [tls:SBC_IP:5061], 0x7f90f2438f80
> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
> [tcp_read.c:1507]: handle_io(): received n=8 con=0x7f90f2438f80, fd=9
> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: tls
> [tls_server.c:184]: tls_complete_init(): Using TLS domain TLSs
> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: tls
> [tls_domain.c:700]: sr_ssl_ctx_info_callback(): SSL handshake started
> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
> [tcp_main.c:2516]: tcpconn_do_send(): tcp_send: sending...
> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
> [tcp_main.c:2550]: tcpconn_do_send(): tcp_send: after real write: c=
> 0x7f90f2438f80 n=1468 fd=9
> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
> [tcp_main.c:2551]: tcpconn_do_send(): tcp_send: buf=
> >> Apr 15 11:11:41 vps793907 kamailio[23122]: #026#003#003
> >> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9c1700, 9, 2,
> 0x7f90f2438f80), fd_no=1
> >> Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
> [tcp_read.c:296]: tcp_read_data(): EOF on 0x7f90f2438f80, FD 9
> >> Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
> [tcp_read.c:1291]: tcp_read_req(): tcp_read_req: EOF
> >> Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9c1700, 9, -1, 0x10)
> fd_no=2 called
> >> Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
> [tcp_read.c:1434]: release_tcpconn(): releasing con 0x7f90f2438f80, state
> -1, fd=9, id=30
> >> Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
> [tcp_read.c:1435]: release_tcpconn():  extra_data 0x7f90f2432b40
> >> Apr 15 11:11:42 vps793907 kamailio[23122]: 13(23167) DEBUG: 
> [tcp_main.c:3331]: handle_tcp_child(): handle_tcp_child: reader response=
> 7f90f2438f80, -1 from 1
> >> Apr 15 11:11:42 vps793907 kamailio[23122]: 13(23167) DEBUG: tls
> [tls_server.c:604]: tls_h_close(): Closing SSL connection 0x7f90f2432b40
> >>
> >> 2.- With TCPDUMP:
> >>
> >> 11:13:09.311797 IP SBC_IP .1024 > SBC_IP .eu.sip-tls: Flags [S], seq
> 261244614

Re: [SR-Users] Kamailio like SBC with Teams

2020-04-16 Thread Ovidiu Sas

; you need to get sip debug  between kamailio and MS. Kamilio has module to 
>> save sip traces. This way you will get sip debug decrypted.
>>
>>
>> 
>> От: sr-users  от имени sip user 
>> 
>> Отправлено: 16 апреля 2020 г. 10:19
>> Кому: sr-users@lists.kamailio.org 
>> Тема: [SR-Users] Kamailio like SBC with Teams
>>
>> Hello good morning ... I am new to this list and I was starting to mess with 
>> Kamailio, mainly to set it up as SBC against Teams, in this case.
>>
>> But I can't get it to work for me. If I launch a call from the Teams, in the 
>> Kamailio I see:
>>
>> 1.- In syslog:
>>
>> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG:  
>> [ip_addr.c:243]: print_ip(): tcpconn_new: new tcp connection: 52.114.7.24
>> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG:  
>> [tcp_main.c:1073]: tcpconn_new(): tcpconn_new: on port 4160, type 3
>> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG:  
>> [tcp_main.c:1382]: tcpconn_add(): tcpconn_add: hashes: 171:1857:1187, 30
>> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG:  
>> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0xa1f240, 23, 2, 
>> 0x7f90f2438f80), fd_no=17
>> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG:  
>> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0xa1f240, 23, -1, 0x0) 
>> fd_no=18 called
>> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG:  
>> [tcp_main.c:4219]: handle_tcpconn_ev(): tcp: DBG: sending to child, events 1
>> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG:  
>> [tcp_main.c:3902]: send2child(): selected tcp worker 1 10(23159) for 
>> activity on [tls:SBC_IP:5061], 0x7f90f2438f80
>> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG:  
>> [tcp_read.c:1507]: handle_io(): received n=8 con=0x7f90f2438f80, fd=9
>> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: tls 
>> [tls_server.c:184]: tls_complete_init(): Using TLS domain TLSs
>> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: tls 
>> [tls_domain.c:700]: sr_ssl_ctx_info_callback(): SSL handshake started
>> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG:  
>> [tcp_main.c:2516]: tcpconn_do_send(): tcp_send: sending...
>> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG:  
>> [tcp_main.c:2550]: tcpconn_do_send(): tcp_send: after real write: c= 
>> 0x7f90f2438f80 n=1468 fd=9
>> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG:  
>> [tcp_main.c:2551]: tcpconn_do_send(): tcp_send: buf=
>> Apr 15 11:11:41 vps793907 kamailio[23122]: #026#003#003
>> Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG:  
>> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9c1700, 9, 2, 
>> 0x7f90f2438f80), fd_no=1
>> Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG:  
>> [tcp_read.c:296]: tcp_read_data(): EOF on 0x7f90f2438f80, FD 9
>> Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG:  
>> [tcp_read.c:1291]: tcp_read_req(): tcp_read_req: EOF
>> Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG:  
>> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9c1700, 9, -1, 0x10) 
>> fd_no=2 called
>> Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG:  
>> [tcp_read.c:1434]: release_tcpconn(): releasing con 0x7f90f2438f80, state 
>> -1, fd=9, id=30
>> Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG:  
>> [tcp_read.c:1435]: release_tcpconn():  extra_data 0x7f90f2432b40
>> Apr 15 11:11:42 vps793907 kamailio[23122]: 13(23167) DEBUG:  
>> [tcp_main.c:3331]: handle_tcp_child(): handle_tcp_child: reader response= 
>> 7f90f2438f80, -1 from 1
>> Apr 15 11:11:42 vps793907 kamailio[23122]: 13(23167) DEBUG: tls 
>> [tls_server.c:604]: tls_h_close(): Closing SSL connection 0x7f90f2432b40
>>
>> 2.- With TCPDUMP:
>>
>> 11:13:09.311797 IP SBC_IP .1024 > SBC_IP .eu.sip-tls: Flags [S], seq 
>> 261244614, win 64240, options [mss 1440,nop,wscale 8,nop,nop,sackOK], length >> 0
>> 11:13:09.311898 IP  SBC_IP .eu.sip-tls > 52.114.76.76.1024: Flags [S.], seq 
>> 812357247, ack 261244615, win 29200, options [mss 
>> 1460,nop,nop,sackOK,nop,wscale 7], length 0
>> 11:13:09.340358 IP 52.114.76.76.1024 >  SBC_IP .eu.sip-tls: Flags [.], ack 
>> 1, win 2053, length 0
>> 11:13:09.340560 IP 52.114.76.76.1024 > SBC_IP .eu.sip-tls: Flags [P.], seq 
>> 1:187, ack 1, win 2053, length 186
>> 11:13:09.340578 IP SBC_IP .eu.sip-tls > 52.114.76.76.1024: Flags [.], ack 
>> 187, win 237, length 0
&

Re: [SR-Users] Kamailio like SBC with Teams

2020-04-16 Thread sip user

Hi Nasida.. Thanks for answerd to me...

I've activarted the debugger module, and I see the same:

Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
[ip_addr.c:243]: print_ip(): tcpconn_new: new tcp connection: 52.114.7.24
Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
[tcp_main.c:1073]: tcpconn_new(): tcpconn_new: on port 4160, type 3
Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
[tcp_main.c:1382]: tcpconn_add(): tcpconn_add: hashes: 171:1857:1187, 30
Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
[io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0xa1f240, 23, 2,
0x7f90f2438f80), fd_no=17
Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
[io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0xa1f240, 23, -1, 0x0)
fd_no=18 called
Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
[tcp_main.c:4219]: handle_tcpconn_ev(): tcp: DBG: sending to child, events 1
Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
[tcp_main.c:3902]: send2child(): selected tcp worker 1 10(23159) for
activity on [tls:SBC_IP:5061], 0x7f90f2438f80
Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
[tcp_read.c:1507]: handle_io(): received n=8 con=0x7f90f2438f80, fd=9
Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: tls
[tls_server.c:184]: tls_complete_init(): Using TLS domain TLSs
Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: tls
[tls_domain.c:700]: sr_ssl_ctx_info_callback(): SSL handshake started
Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
[tcp_main.c:2516]: tcpconn_do_send(): tcp_send: sending...
Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
[tcp_main.c:2550]: tcpconn_do_send(): tcp_send: after real write: c=
0x7f90f2438f80 n=1468 fd=9
Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
[tcp_main.c:2551]: tcpconn_do_send(): tcp_send: buf=
Apr 15 11:11:41 vps793907 kamailio[23122]: #026#003#003
Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
[io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9c1700, 9, 2,
0x7f90f2438f80), fd_no=1
Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
[tcp_read.c:296]: tcp_read_data(): EOF on 0x7f90f2438f80, FD 9
Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
[tcp_read.c:1291]: tcp_read_req(): tcp_read_req: EOF
Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
[io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9c1700, 9, -1, 0x10)
fd_no=2 called
Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
[tcp_read.c:1434]: release_tcpconn(): releasing con 0x7f90f2438f80, state
-1, fd=9, id=30
Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
[tcp_read.c:1435]: release_tcpconn():  extra_data 0x7f90f2432b40
Apr 15 11:11:42 vps793907 kamailio[23122]: 13(23167) DEBUG: 
[tcp_main.c:3331]: handle_tcp_child(): handle_tcp_child: reader response=
7f90f2438f80, -1 from 1
Apr 15 11:11:42 vps793907 kamailio[23122]: 13(23167) DEBUG: tls
[tls_server.c:604]: tls_h_close(): Closing SSL connection 0x7f90f2432b40

I don't see any different.

I know that the module is loaded because I see:

exec: *** cfgtrace:request_route=[DEFAULT_ROUTE]
c=[/etc/kamailio/kamailio.cfg] l=486 a=5 n=route

When I restart kamailio, but when I "launch" a call from Teams to my
Kamailio I only see that.

To configure it, I follow https://skalatan.de/en/blog/kamailio-sbc-teams..
But I cannot make it works..

Any more thing that i can test or do??

Thanks

El jue., 16 abr. 2020 a las 14:20, Nasida Yuriy () escribió:

> Wow, so many people want to configure kamailio with MS. First of all i
> think you need to get sip debug  between kamailio and MS. Kamilio has
> module to save sip traces. This way you will get sip debug decrypted.
>
>
> --
> *От:* sr-users  от имени sip user <
> sipuser...@gmail.com>
> *Отправлено:* 16 апреля 2020 г. 10:19
> *Кому:* sr-users@lists.kamailio.org 
> *Тема:* [SR-Users] Kamailio like SBC with Teams
>
> Hello good morning ... I am new to this list and I was starting to mess
> with Kamailio, mainly to set it up as SBC against Teams, in this case.
>
> But I can't get it to work for me. If I launch a call from the Teams, in
> the Kamailio I see:
>
> 1.- In syslog:
>
> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
> [ip_addr.c:243]: print_ip(): tcpconn_new: new tcp connection: 52.114.7.24
> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
> [tcp_main.c:1073]: tcpconn_new(): tcpconn_new: on port 4160, type 3
> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
> [tcp_main.c:1382]: tcpconn_add(): tcpconn_add: hashes: 171:1857:1187, 30
> Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0xa1f240, 23, 2,
> 0x7f90f2438f80), fd_no=17
> Apr 15 11:11:41 vps793907 kamailio[23122]:

Re: [SR-Users] Kamailio like SBC with Teams

2020-04-16 Thread Nasida Yuriy

Wow, so many people want to configure kamailio with MS. First of all i think 
you need to get sip debug  between kamailio and MS. Kamilio has module to save 
sip traces. This way you will get sip debug decrypted.



От: sr-users  от имени sip user 

Отправлено: 16 апреля 2020 г. 10:19
Кому: sr-users@lists.kamailio.org 
Тема: [SR-Users] Kamailio like SBC with Teams

Hello good morning ... I am new to this list and I was starting to mess with 
Kamailio, mainly to set it up as SBC against Teams, in this case.

But I can't get it to work for me. If I launch a call from the Teams, in the 
Kamailio I see:

1.- In syslog:

Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG:  
[ip_addr.c:243]: print_ip(): tcpconn_new: new tcp connection: 52.114.7.24
Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG:  
[tcp_main.c:1073]: tcpconn_new(): tcpconn_new: on port 4160, type 3
Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG:  
[tcp_main.c:1382]: tcpconn_add(): tcpconn_add: hashes: 171:1857:1187, 30
Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG:  
[io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0xa1f240, 23, 2, 
0x7f90f2438f80), fd_no=17
Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG:  
[io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0xa1f240, 23, -1, 0x0) 
fd_no=18 called
Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG:  
[tcp_main.c:4219]: handle_tcpconn_ev(): tcp: DBG: sending to child, events 1
Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG:  
[tcp_main.c:3902]: send2child(): selected tcp worker 1 10(23159) for activity 
on [tls:SBC_IP:5061], 0x7f90f2438f80
Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG:  
[tcp_read.c:1507]: handle_io(): received n=8 con=0x7f90f2438f80, fd=9
Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: tls 
[tls_server.c:184]: tls_complete_init(): Using TLS domain TLSs
Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: tls 
[tls_domain.c:700]: sr_ssl_ctx_info_callback(): SSL handshake started
Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG:  
[tcp_main.c:2516]: tcpconn_do_send(): tcp_send: sending...
Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG:  
[tcp_main.c:2550]: tcpconn_do_send(): tcp_send: after real write: c= 
0x7f90f2438f80 n=1468 fd=9
Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG:  
[tcp_main.c:2551]: tcpconn_do_send(): tcp_send: buf=
Apr 15 11:11:41 vps793907 kamailio[23122]: #026#003#003
Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG:  
[io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9c1700, 9, 2, 
0x7f90f2438f80), fd_no=1
Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG:  
[tcp_read.c:296]: tcp_read_data(): EOF on 0x7f90f2438f80, FD 9
Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG:  
[tcp_read.c:1291]: tcp_read_req(): tcp_read_req: EOF
Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG:  
[io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9c1700, 9, -1, 0x10) 
fd_no=2 called
Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG:  
[tcp_read.c:1434]: release_tcpconn(): releasing con 0x7f90f2438f80, state -1, 
fd=9, id=30
Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG:  
[tcp_read.c:1435]: release_tcpconn():  extra_data 0x7f90f2432b40
Apr 15 11:11:42 vps793907 kamailio[23122]: 13(23167) DEBUG:  
[tcp_main.c:3331]: handle_tcp_child(): handle_tcp_child: reader response= 
7f90f2438f80, -1 from 1
Apr 15 11:11:42 vps793907 kamailio[23122]: 13(23167) DEBUG: tls 
[tls_server.c:604]: tls_h_close(): Closing SSL connection 0x7f90f2432b40

2.- With TCPDUMP:

11:13:09.311797 IP SBC_IP .1024 > SBC_IP .eu.sip-tls: Flags [S], seq 261244614, 
win 64240, options [mss 1440,nop,wscale 8,nop,nop,sackOK], length 0
11:13:09.311898 IP  SBC_IP .eu.sip-tls > 52.114.76.76.1024: Flags [S.], seq 
812357247, ack 261244615, win 29200, options [mss 
1460,nop,nop,sackOK,nop,wscale 7], length 0
11:13:09.340358 IP 52.114.76.76.1024 >  SBC_IP .eu.sip-tls: Flags [.], ack 1, 
win 2053, length 0
11:13:09.340560 IP 52.114.76.76.1024 > SBC_IP .eu.sip-tls: Flags [P.], seq 
1:187, ack 1, win 2053, length 186
11:13:09.340578 IP SBC_IP .eu.sip-tls > 52.114.76.76.1024: Flags [.], ack 187, 
win 237, length 0
11:13:09.341361 IP SBC_IP .eu.sip-tls > 52.114.76.76.1024: Flags [P.], seq 
1:1469, ack 187, win 237, length 1468
11:13:09.369606 IP 52.114.76.76.1024 > SBC_IP .eu.sip-tls: Flags [.], ack 1469, 
win 2053, length 0
11:13:12.451498 IP 52.114.7.24.1216 > SBC_IP .eu.sip-tls: Flags [S], seq 
309084204, win 64240, options [mss 1440,nop,wscale 8,nop,nop,sackOK], length 0
11:13:12.451587 IP SBC_IP .eu.sip-tls > 52.114.7.24.1216: Flags [S.], seq 
3275066862, ack 309084205, win 29200, options [mss 
1460,nop,nop,sackOK,nop,wscale 7], length 0
11:13:12.707119 IP 52.114.7.24.1216 > SBC_IP .eu.sip-tls: Flags [.], ack 1, win 
2053, length 0
11:13:12.707311 IP 52.114.

[SR-Users] Kamailio like SBC with Teams

2020-04-16 Thread sip user

Hello good morning ... I am new to this list and I was starting to mess
with Kamailio, mainly to set it up as SBC against Teams, in this case.

But I can't get it to work for me. If I launch a call from the Teams, in
the Kamailio I see:

1.- In syslog:

Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
[ip_addr.c:243]: print_ip(): tcpconn_new: new tcp connection: 52.114.7.24
Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
[tcp_main.c:1073]: tcpconn_new(): tcpconn_new: on port 4160, type 3
Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
[tcp_main.c:1382]: tcpconn_add(): tcpconn_add: hashes: 171:1857:1187, 30
Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
[io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0xa1f240, 23, 2,
0x7f90f2438f80), fd_no=17
Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
[io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0xa1f240, 23, -1, 0x0)
fd_no=18 called
Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
[tcp_main.c:4219]: handle_tcpconn_ev(): tcp: DBG: sending to child, events 1
Apr 15 11:11:41 vps793907 kamailio[23122]: 13(23167) DEBUG: 
[tcp_main.c:3902]: send2child(): selected tcp worker 1 10(23159) for
activity on [tls:SBC_IP:5061], 0x7f90f2438f80
Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
[tcp_read.c:1507]: handle_io(): received n=8 con=0x7f90f2438f80, fd=9
Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: tls
[tls_server.c:184]: tls_complete_init(): Using TLS domain TLSs
Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: tls
[tls_domain.c:700]: sr_ssl_ctx_info_callback(): SSL handshake started
Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
[tcp_main.c:2516]: tcpconn_do_send(): tcp_send: sending...
Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
[tcp_main.c:2550]: tcpconn_do_send(): tcp_send: after real write: c=
0x7f90f2438f80 n=1468 fd=9
Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
[tcp_main.c:2551]: tcpconn_do_send(): tcp_send: buf=
Apr 15 11:11:41 vps793907 kamailio[23122]: #026#003#003
Apr 15 11:11:41 vps793907 kamailio[23122]: 10(23159) DEBUG: 
[io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9c1700, 9, 2,
0x7f90f2438f80), fd_no=1
Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
[tcp_read.c:296]: tcp_read_data(): EOF on 0x7f90f2438f80, FD 9
Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
[tcp_read.c:1291]: tcp_read_req(): tcp_read_req: EOF
Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
[io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9c1700, 9, -1, 0x10)
fd_no=2 called
Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
[tcp_read.c:1434]: release_tcpconn(): releasing con 0x7f90f2438f80, state
-1, fd=9, id=30
Apr 15 11:11:42 vps793907 kamailio[23122]: 10(23159) DEBUG: 
[tcp_read.c:1435]: release_tcpconn():  extra_data 0x7f90f2432b40
Apr 15 11:11:42 vps793907 kamailio[23122]: 13(23167) DEBUG: 
[tcp_main.c:3331]: handle_tcp_child(): handle_tcp_child: reader response=
7f90f2438f80, -1 from 1
Apr 15 11:11:42 vps793907 kamailio[23122]: 13(23167) DEBUG: tls
[tls_server.c:604]: tls_h_close(): Closing SSL connection 0x7f90f2432b40

2.- With TCPDUMP:

11:13:09.311797 IP SBC_IP .1024 > SBC_IP .eu.sip-tls: Flags [S], seq
261244614, win 64240, options [mss 1440,nop,wscale 8,nop,nop,sackOK],
length 0
11:13:09.311898 IP  SBC_IP .eu.sip-tls > 52.114.76.76.1024: Flags [S.], seq
812357247, ack 261244615, win 29200, options [mss
1460,nop,nop,sackOK,nop,wscale 7], length 0
11:13:09.340358 IP 52.114.76.76.1024 >  SBC_IP .eu.sip-tls: Flags [.], ack
1, win 2053, length 0
11:13:09.340560 IP 52.114.76.76.1024 > SBC_IP .eu.sip-tls: Flags [P.], seq
1:187, ack 1, win 2053, length 186
11:13:09.340578 IP SBC_IP .eu.sip-tls > 52.114.76.76.1024: Flags [.], ack
187, win 237, length 0
11:13:09.341361 IP SBC_IP .eu.sip-tls > 52.114.76.76.1024: Flags [P.], seq
1:1469, ack 187, win 237, length 1468
11:13:09.369606 IP 52.114.76.76.1024 > SBC_IP .eu.sip-tls: Flags [.], ack
1469, win 2053, length 0
11:13:12.451498 IP 52.114.7.24.1216 > SBC_IP .eu.sip-tls: Flags [S], seq
309084204, win 64240, options [mss 1440,nop,wscale 8,nop,nop,sackOK],
length 0
11:13:12.451587 IP SBC_IP .eu.sip-tls > 52.114.7.24.1216: Flags [S.], seq
3275066862, ack 309084205, win 29200, options [mss
1460,nop,nop,sackOK,nop,wscale 7], length 0
11:13:12.707119 IP 52.114.7.24.1216 > SBC_IP .eu.sip-tls: Flags [.], ack 1,
win 2053, length 0
11:13:12.707311 IP 52.114.7.24.1216 > SBC_IP .eu.sip-tls: Flags [P.], seq
1:187, ack 1, win 2053, length 186
11:13:12.707345 IP SBC_IP .eu.sip-tls > 52.114.7.24.1216: Flags [.], ack
187, win 237, length 0
11:13:12.708273 IP SBC_IP .eu.sip-tls > 52.114.7.24.1216: Flags [P.], seq
1:1469, ack 187, win 237, length 1468
11:13:12.965101 IP 52.114.7.24.1216 > SBC_IP .eu.sip-tls: Flags [.], ack
1469, win 2053, length 0
11:13:12.965156 IP 52.114.7.24.1216 > SBC_IP .eu.sip-tls: Flags [F.], seq
187, ack

Re: [SR-Users] kamailio as SBC for Teams

2020-04-10 Thread Ovidiu Sas

The FQDN must be in the Contact of the OPTIONS request that is used for the
trunk keep alive. No need to mess up with the Contact header for in dialog
requests/replies.
However, the FQDN must be in the Record-Route header facing MS for in
dialog requests/replies.

Regards,
Ovidiu Sas

On Fri, Apr 10, 2020 at 12:59 Karsten Horsmann  wrote:

> Hi,
>
> Like in Hennings howto described if the front facing Kamailio used the
> FQDN names in contact and so one it works.
>
> And the "must be an certified sbc" is an marketing foo and for support
> cases they can say "go-to your sbc vendor" imho.
>
> I had this setup up and running.
>
> Kind regards
> Karsten Horsmann
>
> Sergiu Pojoga  schrieb am Fr., 10. Apr. 2020, 18:27:
>
>> Contact:
>> 
>>
>> Again, MS says it expects FQDN in Contact.
>>
>> If you are re-writing the Contact received from
>> ENDPOINT_BEHIND_KAMAILIO_IP, then I suggest you don't, it's sufficient to
>> have FQDN in RR. This isn't a "[certified] SBC", if it was like MS says -
>> it shouldn't work at all with a proxy like Kamailio.
>>
>> On Fri, Apr 10, 2020 at 12:00 PM Sergiu Pojoga  wrote:
>>
>>> You're likely referring to this:
>>>
>>> *Priority 1. Top-level Record-Route. If the top-level Record-Route
>>> contains the FQDN name or IP, the FQDN name or IP is used to make the
>>> outbound in-dialog connection.*
>>>
>>> Like with many Microsoft products, nobody knows precisely what they
>>> expect. To make matters worse - they don't reply back suggesting what's
>>> wrong, no tools on their side to troubleshoot.
>>>
>>> Regardless, why do you have 3 RRs of Kamailio? Fix the RRs, try again,
>>> or don't, it's up to you.
>>>
>>> Good luck.
>>>
>>> --Sergiu
>>>
>>>
>>> On Fri, Apr 10, 2020 at 11:42 AM Aidar Kamalov 
>>> wrote:
>>>
 I thought they look only at first RR field?

 пт, 10 апр. 2020 г. в 17:03, Sergiu Pojoga :

> You have too many RR of Kamailio, x1 FQDN, x3 IP. Why?
>
> IMO, you should have only 2 of Kamailio, if you're doing transport
> conversion. Both FQDNs + ";r2=on". MS clearly says FQDN everywhere, no IP,
> especially RR
>
> On Fri, Apr 10, 2020 at 7:06 AM Aidar Kamalov 
> wrote:
>
>> Thanks for the answer, I have disabled forse_rport() for Teams side,
>> responses now going to address in Via header, but it is not resolved my
>> issue, no ACK from Teams :(
>>
>> чт, 9 апр. 2020 г. в 18:22, Sergiu Pojoga :
>>
>>> Hi Aydar,
>>>
>>> Request from MS proxy has  VIA: SIP/2.0/TLS 52.114.7.24:5061,
>>> that's where your reply should go. You're sending to
>>> 52.114.7.24:1024 instead?
>>>
>>> Also, looks like you're missing "r2=on" on the other RR, only one
>>> has it.
>>>
>>> Cheers,
>>>
>>> On Thu, Apr 9, 2020 at 11:09 AM Aidar Kamalov <
>>> aidar.kama...@gmail.com> wrote:
>>>
 Hello,

 I read https://skalatan.de/en/blog/kamailio-sbc-teams and trying
 to use kamailio for teams.
 But I faced that MS not responding ACK to my 200OK. Somethin is
 wrong, but I don't know what. I call from teams to kamailio.
 Can you help me please

 This is initial INVITE from Teams:
 2020/04/09 22:55:17.346092 52.114.7.24:1024 -> KAMAILIO_IP:5061
 INVITE sip:+x@MY_KAMAILIO_FQDN:5061;user=phone;transport=tls
 SIP/2.0
 FROM: Aidar Kamalov>>> ;user=phone>;tag=de28a5b5333b451a97312097f91f5564
 TO: 
 CSEQ: 1 INVITE
 CALL-ID: 3d5ad3cdd01457be94d127fa20478cf1
 MAX-FORWARDS: 70
 VIA: SIP/2.0/TLS 52.114.7.24:5061;branch=z9hG4bKdb903e2c
 RECORD-ROUTE: >>> ;transport=tls;lr>
 CONTACT: >>> ;x-i=903eeaac-b19e-43a0-8e75-bb222049922a;x-c=3d5ad3cdd01457be94d127fa20478cf1/d/8/d3d2c2e3f3c14f88bb2fe843b4bc70e4>
 CONTENT-LENGTH: 2426
 USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.4.4.3 i.ASEA.5
 CONTENT-TYPE: application/sdp
 ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY

 v=0
 o=- 0 0 IN IP4 52.114.252.146
 s=session
 c=IN IP4 52.114.252.146
 b=CT:5
 t=0 0
 m=audio 52939 RTP/SAVP 104 9 111 18 0 8 103 97 13 118 119 101
 a=rtcp:52925
 a=ice-ufrag:rKBm
 a=ice-pwd:BkjUnkfIvYV5pjteSteevL1O
 a=rtcp-mux
 a=candidate:4 1 UDP 184547839 52.114.252.146 52939 typ relay raddr
 31.13.144.55 rport 57780
 a=candidate:4 2 UDP 184547326 52.114.252.146 52925 typ relay raddr
 31.13.144.55 rport 57781
 a=candidate:1 1 tcp-act 2121006590 100.78.247.179 1024 typ host
 a=candidate:1 2 tcp-act 2121006590 100.78.247.179 1024 typ host
 a=candidate:2 1 UDP 2130705919 100.78.247.179 39182 typ host
 a=candidate:2 2 UDP 2130705406 100.78.247.179 39183 typ host
 a=candidate:3 1 UDP 1694497791 31.13.144.55 57780 typ srflx raddr
 100.78.247.179 rport

Re: [SR-Users] kamailio as SBC for Teams

2020-04-10 Thread Karsten Horsmann

Hi,

Like in Hennings howto described if the front facing Kamailio used the FQDN
names in contact and so one it works.

And the "must be an certified sbc" is an marketing foo and for support
cases they can say "go-to your sbc vendor" imho.

I had this setup up and running.

Kind regards
Karsten Horsmann

Sergiu Pojoga  schrieb am Fr., 10. Apr. 2020, 18:27:

> Contact:
> 
>
> Again, MS says it expects FQDN in Contact.
>
> If you are re-writing the Contact received from
> ENDPOINT_BEHIND_KAMAILIO_IP, then I suggest you don't, it's sufficient to
> have FQDN in RR. This isn't a "[certified] SBC", if it was like MS says -
> it shouldn't work at all with a proxy like Kamailio.
>
> On Fri, Apr 10, 2020 at 12:00 PM Sergiu Pojoga  wrote:
>
>> You're likely referring to this:
>>
>> *Priority 1. Top-level Record-Route. If the top-level Record-Route
>> contains the FQDN name or IP, the FQDN name or IP is used to make the
>> outbound in-dialog connection.*
>>
>> Like with many Microsoft products, nobody knows precisely what they
>> expect. To make matters worse - they don't reply back suggesting what's
>> wrong, no tools on their side to troubleshoot.
>>
>> Regardless, why do you have 3 RRs of Kamailio? Fix the RRs, try again, or
>> don't, it's up to you.
>>
>> Good luck.
>>
>> --Sergiu
>>
>>
>> On Fri, Apr 10, 2020 at 11:42 AM Aidar Kamalov 
>> wrote:
>>
>>> I thought they look only at first RR field?
>>>
>>> пт, 10 апр. 2020 г. в 17:03, Sergiu Pojoga :
>>>
 You have too many RR of Kamailio, x1 FQDN, x3 IP. Why?

 IMO, you should have only 2 of Kamailio, if you're doing transport
 conversion. Both FQDNs + ";r2=on". MS clearly says FQDN everywhere, no IP,
 especially RR

 On Fri, Apr 10, 2020 at 7:06 AM Aidar Kamalov 
 wrote:

> Thanks for the answer, I have disabled forse_rport() for Teams side,
> responses now going to address in Via header, but it is not resolved my
> issue, no ACK from Teams :(
>
> чт, 9 апр. 2020 г. в 18:22, Sergiu Pojoga :
>
>> Hi Aydar,
>>
>> Request from MS proxy has  VIA: SIP/2.0/TLS 52.114.7.24:5061, that's
>> where your reply should go. You're sending to 52.114.7.24:1024
>> instead?
>>
>> Also, looks like you're missing "r2=on" on the other RR, only one has
>> it.
>>
>> Cheers,
>>
>> On Thu, Apr 9, 2020 at 11:09 AM Aidar Kamalov <
>> aidar.kama...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> I read https://skalatan.de/en/blog/kamailio-sbc-teams and trying to
>>> use kamailio for teams.
>>> But I faced that MS not responding ACK to my 200OK. Somethin is
>>> wrong, but I don't know what. I call from teams to kamailio.
>>> Can you help me please
>>>
>>> This is initial INVITE from Teams:
>>> 2020/04/09 22:55:17.346092 52.114.7.24:1024 -> KAMAILIO_IP:5061
>>> INVITE sip:+x@MY_KAMAILIO_FQDN:5061;user=phone;transport=tls
>>> SIP/2.0
>>> FROM: Aidar Kamalov>> ;user=phone>;tag=de28a5b5333b451a97312097f91f5564
>>> TO: 
>>> CSEQ: 1 INVITE
>>> CALL-ID: 3d5ad3cdd01457be94d127fa20478cf1
>>> MAX-FORWARDS: 70
>>> VIA: SIP/2.0/TLS 52.114.7.24:5061;branch=z9hG4bKdb903e2c
>>> RECORD-ROUTE: >> ;transport=tls;lr>
>>> CONTACT: >> ;x-i=903eeaac-b19e-43a0-8e75-bb222049922a;x-c=3d5ad3cdd01457be94d127fa20478cf1/d/8/d3d2c2e3f3c14f88bb2fe843b4bc70e4>
>>> CONTENT-LENGTH: 2426
>>> USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.4.4.3 i.ASEA.5
>>> CONTENT-TYPE: application/sdp
>>> ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY
>>>
>>> v=0
>>> o=- 0 0 IN IP4 52.114.252.146
>>> s=session
>>> c=IN IP4 52.114.252.146
>>> b=CT:5
>>> t=0 0
>>> m=audio 52939 RTP/SAVP 104 9 111 18 0 8 103 97 13 118 119 101
>>> a=rtcp:52925
>>> a=ice-ufrag:rKBm
>>> a=ice-pwd:BkjUnkfIvYV5pjteSteevL1O
>>> a=rtcp-mux
>>> a=candidate:4 1 UDP 184547839 52.114.252.146 52939 typ relay raddr
>>> 31.13.144.55 rport 57780
>>> a=candidate:4 2 UDP 184547326 52.114.252.146 52925 typ relay raddr
>>> 31.13.144.55 rport 57781
>>> a=candidate:1 1 tcp-act 2121006590 100.78.247.179 1024 typ host
>>> a=candidate:1 2 tcp-act 2121006590 100.78.247.179 1024 typ host
>>> a=candidate:2 1 UDP 2130705919 100.78.247.179 39182 typ host
>>> a=candidate:2 2 UDP 2130705406 100.78.247.179 39183 typ host
>>> a=candidate:3 1 UDP 1694497791 31.13.144.55 57780 typ srflx raddr
>>> 100.78.247.179 rport 39182
>>> a=candidate:3 2 UDP 1694497278 31.13.144.55 57781 typ srflx raddr
>>> 100.78.247.179 rport 39183
>>> a=candidate:5 1 tcp-act 1684796926 31.13.144.55 9761 typ srflx raddr
>>> 100.78.247.179 rport 41775
>>> a=candidate:5 2 tcp-act 1684796926 31.13.144.55 9761 typ srflx raddr
>>> 100.78.247.179 rport 41775
>>> a=candidate:6 1 tcp-pass 174453758 52.114.252.130 59925 typ relay
>>> raddr 31.13.144.55 rport 9761
>>> a=candidate:6 2

Re: [SR-Users] kamailio as SBC for Teams

2020-04-10 Thread Sergiu Pojoga

Contact:


Again, MS says it expects FQDN in Contact.

If you are re-writing the Contact received from
ENDPOINT_BEHIND_KAMAILIO_IP, then I suggest you don't, it's sufficient to
have FQDN in RR. This isn't a "[certified] SBC", if it was like MS says -
it shouldn't work at all with a proxy like Kamailio.

On Fri, Apr 10, 2020 at 12:00 PM Sergiu Pojoga  wrote:

> You're likely referring to this:
>
> *Priority 1. Top-level Record-Route. If the top-level Record-Route
> contains the FQDN name or IP, the FQDN name or IP is used to make the
> outbound in-dialog connection.*
>
> Like with many Microsoft products, nobody knows precisely what they
> expect. To make matters worse - they don't reply back suggesting what's
> wrong, no tools on their side to troubleshoot.
>
> Regardless, why do you have 3 RRs of Kamailio? Fix the RRs, try again, or
> don't, it's up to you.
>
> Good luck.
>
> --Sergiu
>
>
> On Fri, Apr 10, 2020 at 11:42 AM Aidar Kamalov 
> wrote:
>
>> I thought they look only at first RR field?
>>
>> пт, 10 апр. 2020 г. в 17:03, Sergiu Pojoga :
>>
>>> You have too many RR of Kamailio, x1 FQDN, x3 IP. Why?
>>>
>>> IMO, you should have only 2 of Kamailio, if you're doing transport
>>> conversion. Both FQDNs + ";r2=on". MS clearly says FQDN everywhere, no IP,
>>> especially RR
>>>
>>> On Fri, Apr 10, 2020 at 7:06 AM Aidar Kamalov 
>>> wrote:
>>>
 Thanks for the answer, I have disabled forse_rport() for Teams side,
 responses now going to address in Via header, but it is not resolved my
 issue, no ACK from Teams :(

 чт, 9 апр. 2020 г. в 18:22, Sergiu Pojoga :

> Hi Aydar,
>
> Request from MS proxy has  VIA: SIP/2.0/TLS 52.114.7.24:5061, that's
> where your reply should go. You're sending to 52.114.7.24:1024
> instead?
>
> Also, looks like you're missing "r2=on" on the other RR, only one has
> it.
>
> Cheers,
>
> On Thu, Apr 9, 2020 at 11:09 AM Aidar Kamalov 
> wrote:
>
>> Hello,
>>
>> I read https://skalatan.de/en/blog/kamailio-sbc-teams and trying to
>> use kamailio for teams.
>> But I faced that MS not responding ACK to my 200OK. Somethin is
>> wrong, but I don't know what. I call from teams to kamailio.
>> Can you help me please
>>
>> This is initial INVITE from Teams:
>> 2020/04/09 22:55:17.346092 52.114.7.24:1024 -> KAMAILIO_IP:5061
>> INVITE sip:+x@MY_KAMAILIO_FQDN:5061;user=phone;transport=tls
>> SIP/2.0
>> FROM: Aidar Kamalov> ;user=phone>;tag=de28a5b5333b451a97312097f91f5564
>> TO: 
>> CSEQ: 1 INVITE
>> CALL-ID: 3d5ad3cdd01457be94d127fa20478cf1
>> MAX-FORWARDS: 70
>> VIA: SIP/2.0/TLS 52.114.7.24:5061;branch=z9hG4bKdb903e2c
>> RECORD-ROUTE: > ;transport=tls;lr>
>> CONTACT: > ;x-i=903eeaac-b19e-43a0-8e75-bb222049922a;x-c=3d5ad3cdd01457be94d127fa20478cf1/d/8/d3d2c2e3f3c14f88bb2fe843b4bc70e4>
>> CONTENT-LENGTH: 2426
>> USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.4.4.3 i.ASEA.5
>> CONTENT-TYPE: application/sdp
>> ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY
>>
>> v=0
>> o=- 0 0 IN IP4 52.114.252.146
>> s=session
>> c=IN IP4 52.114.252.146
>> b=CT:5
>> t=0 0
>> m=audio 52939 RTP/SAVP 104 9 111 18 0 8 103 97 13 118 119 101
>> a=rtcp:52925
>> a=ice-ufrag:rKBm
>> a=ice-pwd:BkjUnkfIvYV5pjteSteevL1O
>> a=rtcp-mux
>> a=candidate:4 1 UDP 184547839 52.114.252.146 52939 typ relay raddr
>> 31.13.144.55 rport 57780
>> a=candidate:4 2 UDP 184547326 52.114.252.146 52925 typ relay raddr
>> 31.13.144.55 rport 57781
>> a=candidate:1 1 tcp-act 2121006590 100.78.247.179 1024 typ host
>> a=candidate:1 2 tcp-act 2121006590 100.78.247.179 1024 typ host
>> a=candidate:2 1 UDP 2130705919 100.78.247.179 39182 typ host
>> a=candidate:2 2 UDP 2130705406 100.78.247.179 39183 typ host
>> a=candidate:3 1 UDP 1694497791 31.13.144.55 57780 typ srflx raddr
>> 100.78.247.179 rport 39182
>> a=candidate:3 2 UDP 1694497278 31.13.144.55 57781 typ srflx raddr
>> 100.78.247.179 rport 39183
>> a=candidate:5 1 tcp-act 1684796926 31.13.144.55 9761 typ srflx raddr
>> 100.78.247.179 rport 41775
>> a=candidate:5 2 tcp-act 1684796926 31.13.144.55 9761 typ srflx raddr
>> 100.78.247.179 rport 41775
>> a=candidate:6 1 tcp-pass 174453758 52.114.252.130 59925 typ relay
>> raddr 31.13.144.55 rport 9761
>> a=candidate:6 2 tcp-pass 174453758 52.114.252.130 59925 typ relay
>> raddr 31.13.144.55 rport 9761
>> a=candidate:7 1 tcp-act 174846462 52.114.252.130 59925 typ relay
>> raddr 31.13.144.55 rport 9761
>> a=candidate:7 2 tcp-act 174846462 52.114.252.130 59925 typ relay
>> raddr 31.13.144.55 rport 9761
>> a=x-candidate-info:4 network-type=WWAN
>> a=x-candidate-info:1 network-type=WWAN
>> a=x-candidate-info:2 network-type=WWAN
>> a=x-candidate-info:3 network-type=WWAN
>> a=x-candidate-info:5

Re: [SR-Users] kamailio as SBC for Teams

2020-04-10 Thread Sergiu Pojoga

You're likely referring to this:

*Priority 1. Top-level Record-Route. If the top-level Record-Route contains
the FQDN name or IP, the FQDN name or IP is used to make the outbound
in-dialog connection.*

Like with many Microsoft products, nobody knows precisely what they expect.
To make matters worse - they don't reply back suggesting what's wrong, no
tools on their side to troubleshoot.

Regardless, why do you have 3 RRs of Kamailio? Fix the RRs, try again, or
don't, it's up to you.

Good luck.

--Sergiu


On Fri, Apr 10, 2020 at 11:42 AM Aidar Kamalov 
wrote:

> I thought they look only at first RR field?
>
> пт, 10 апр. 2020 г. в 17:03, Sergiu Pojoga :
>
>> You have too many RR of Kamailio, x1 FQDN, x3 IP. Why?
>>
>> IMO, you should have only 2 of Kamailio, if you're doing transport
>> conversion. Both FQDNs + ";r2=on". MS clearly says FQDN everywhere, no IP,
>> especially RR
>>
>> On Fri, Apr 10, 2020 at 7:06 AM Aidar Kamalov 
>> wrote:
>>
>>> Thanks for the answer, I have disabled forse_rport() for Teams side,
>>> responses now going to address in Via header, but it is not resolved my
>>> issue, no ACK from Teams :(
>>>
>>> чт, 9 апр. 2020 г. в 18:22, Sergiu Pojoga :
>>>
 Hi Aydar,

 Request from MS proxy has  VIA: SIP/2.0/TLS 52.114.7.24:5061, that's
 where your reply should go. You're sending to 52.114.7.24:1024 instead?

 Also, looks like you're missing "r2=on" on the other RR, only one has
 it.

 Cheers,

 On Thu, Apr 9, 2020 at 11:09 AM Aidar Kamalov 
 wrote:

> Hello,
>
> I read https://skalatan.de/en/blog/kamailio-sbc-teams and trying to
> use kamailio for teams.
> But I faced that MS not responding ACK to my 200OK. Somethin is wrong,
> but I don't know what. I call from teams to kamailio.
> Can you help me please
>
> This is initial INVITE from Teams:
> 2020/04/09 22:55:17.346092 52.114.7.24:1024 -> KAMAILIO_IP:5061
> INVITE sip:+x@MY_KAMAILIO_FQDN:5061;user=phone;transport=tls
> SIP/2.0
> FROM: Aidar Kamalov ;user=phone>;tag=de28a5b5333b451a97312097f91f5564
> TO: 
> CSEQ: 1 INVITE
> CALL-ID: 3d5ad3cdd01457be94d127fa20478cf1
> MAX-FORWARDS: 70
> VIA: SIP/2.0/TLS 52.114.7.24:5061;branch=z9hG4bKdb903e2c
> RECORD-ROUTE:  ;transport=tls;lr>
> CONTACT:  ;x-i=903eeaac-b19e-43a0-8e75-bb222049922a;x-c=3d5ad3cdd01457be94d127fa20478cf1/d/8/d3d2c2e3f3c14f88bb2fe843b4bc70e4>
> CONTENT-LENGTH: 2426
> USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.4.4.3 i.ASEA.5
> CONTENT-TYPE: application/sdp
> ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY
>
> v=0
> o=- 0 0 IN IP4 52.114.252.146
> s=session
> c=IN IP4 52.114.252.146
> b=CT:5
> t=0 0
> m=audio 52939 RTP/SAVP 104 9 111 18 0 8 103 97 13 118 119 101
> a=rtcp:52925
> a=ice-ufrag:rKBm
> a=ice-pwd:BkjUnkfIvYV5pjteSteevL1O
> a=rtcp-mux
> a=candidate:4 1 UDP 184547839 52.114.252.146 52939 typ relay raddr
> 31.13.144.55 rport 57780
> a=candidate:4 2 UDP 184547326 52.114.252.146 52925 typ relay raddr
> 31.13.144.55 rport 57781
> a=candidate:1 1 tcp-act 2121006590 100.78.247.179 1024 typ host
> a=candidate:1 2 tcp-act 2121006590 100.78.247.179 1024 typ host
> a=candidate:2 1 UDP 2130705919 100.78.247.179 39182 typ host
> a=candidate:2 2 UDP 2130705406 100.78.247.179 39183 typ host
> a=candidate:3 1 UDP 1694497791 31.13.144.55 57780 typ srflx raddr
> 100.78.247.179 rport 39182
> a=candidate:3 2 UDP 1694497278 31.13.144.55 57781 typ srflx raddr
> 100.78.247.179 rport 39183
> a=candidate:5 1 tcp-act 1684796926 31.13.144.55 9761 typ srflx raddr
> 100.78.247.179 rport 41775
> a=candidate:5 2 tcp-act 1684796926 31.13.144.55 9761 typ srflx raddr
> 100.78.247.179 rport 41775
> a=candidate:6 1 tcp-pass 174453758 52.114.252.130 59925 typ relay
> raddr 31.13.144.55 rport 9761
> a=candidate:6 2 tcp-pass 174453758 52.114.252.130 59925 typ relay
> raddr 31.13.144.55 rport 9761
> a=candidate:7 1 tcp-act 174846462 52.114.252.130 59925 typ relay raddr
> 31.13.144.55 rport 9761
> a=candidate:7 2 tcp-act 174846462 52.114.252.130 59925 typ relay raddr
> 31.13.144.55 rport 9761
> a=x-candidate-info:4 network-type=WWAN
> a=x-candidate-info:1 network-type=WWAN
> a=x-candidate-info:2 network-type=WWAN
> a=x-candidate-info:3 network-type=WWAN
> a=x-candidate-info:5 network-type=WWAN
> a=x-candidate-info:6 network-type=WWAN
> a=x-candidate-info:7 network-type=WWAN
> a=crypto:1 AES_CM_128_HMAC_SHA1_32
> inline:DY3r3DWRojJm94CJQ83OAavmlRCwPf5ciRxHCT40|2^31
> a=crypto:2 AES_CM_128_HMAC_SHA1_80
> inline:DY3r3DWRojJm94CJQ83OAavmlRCwPf5ciRxHCT40|2^31
> a=crypto:3 AES_CM_128_HMAC_SHA1_80
> inline:DY3r3DWRojJm94CJQ83OAavmlRCwPf5ciRxHCT40|2^31|1:1
> a=rtpmap:104 SILK/16000
> a=fmtp:104 useinbandfec=1; usedtx=0
> a=rtpmap:9

Re: [SR-Users] kamailio as SBC for Teams

2020-04-10 Thread Aidar Kamalov

I thought they look only at first RR field?

пт, 10 апр. 2020 г. в 17:03, Sergiu Pojoga :

> You have too many RR of Kamailio, x1 FQDN, x3 IP. Why?
>
> IMO, you should have only 2 of Kamailio, if you're doing transport
> conversion. Both FQDNs + ";r2=on". MS clearly says FQDN everywhere, no IP,
> especially RR
>
> On Fri, Apr 10, 2020 at 7:06 AM Aidar Kamalov 
> wrote:
>
>> Thanks for the answer, I have disabled forse_rport() for Teams side,
>> responses now going to address in Via header, but it is not resolved my
>> issue, no ACK from Teams :(
>>
>> чт, 9 апр. 2020 г. в 18:22, Sergiu Pojoga :
>>
>>> Hi Aydar,
>>>
>>> Request from MS proxy has  VIA: SIP/2.0/TLS 52.114.7.24:5061, that's
>>> where your reply should go. You're sending to 52.114.7.24:1024 instead?
>>>
>>> Also, looks like you're missing "r2=on" on the other RR, only one has it.
>>>
>>> Cheers,
>>>
>>> On Thu, Apr 9, 2020 at 11:09 AM Aidar Kamalov 
>>> wrote:
>>>
 Hello,

 I read https://skalatan.de/en/blog/kamailio-sbc-teams and trying to
 use kamailio for teams.
 But I faced that MS not responding ACK to my 200OK. Somethin is wrong,
 but I don't know what. I call from teams to kamailio.
 Can you help me please

 This is initial INVITE from Teams:
 2020/04/09 22:55:17.346092 52.114.7.24:1024 -> KAMAILIO_IP:5061
 INVITE sip:+x@MY_KAMAILIO_FQDN:5061;user=phone;transport=tls
 SIP/2.0
 FROM: Aidar Kamalov>>> ;user=phone>;tag=de28a5b5333b451a97312097f91f5564
 TO: 
 CSEQ: 1 INVITE
 CALL-ID: 3d5ad3cdd01457be94d127fa20478cf1
 MAX-FORWARDS: 70
 VIA: SIP/2.0/TLS 52.114.7.24:5061;branch=z9hG4bKdb903e2c
 RECORD-ROUTE: >>> ;transport=tls;lr>
 CONTACT: >>> ;x-i=903eeaac-b19e-43a0-8e75-bb222049922a;x-c=3d5ad3cdd01457be94d127fa20478cf1/d/8/d3d2c2e3f3c14f88bb2fe843b4bc70e4>
 CONTENT-LENGTH: 2426
 USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.4.4.3 i.ASEA.5
 CONTENT-TYPE: application/sdp
 ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY

 v=0
 o=- 0 0 IN IP4 52.114.252.146
 s=session
 c=IN IP4 52.114.252.146
 b=CT:5
 t=0 0
 m=audio 52939 RTP/SAVP 104 9 111 18 0 8 103 97 13 118 119 101
 a=rtcp:52925
 a=ice-ufrag:rKBm
 a=ice-pwd:BkjUnkfIvYV5pjteSteevL1O
 a=rtcp-mux
 a=candidate:4 1 UDP 184547839 52.114.252.146 52939 typ relay raddr
 31.13.144.55 rport 57780
 a=candidate:4 2 UDP 184547326 52.114.252.146 52925 typ relay raddr
 31.13.144.55 rport 57781
 a=candidate:1 1 tcp-act 2121006590 100.78.247.179 1024 typ host
 a=candidate:1 2 tcp-act 2121006590 100.78.247.179 1024 typ host
 a=candidate:2 1 UDP 2130705919 100.78.247.179 39182 typ host
 a=candidate:2 2 UDP 2130705406 100.78.247.179 39183 typ host
 a=candidate:3 1 UDP 1694497791 31.13.144.55 57780 typ srflx raddr
 100.78.247.179 rport 39182
 a=candidate:3 2 UDP 1694497278 31.13.144.55 57781 typ srflx raddr
 100.78.247.179 rport 39183
 a=candidate:5 1 tcp-act 1684796926 31.13.144.55 9761 typ srflx raddr
 100.78.247.179 rport 41775
 a=candidate:5 2 tcp-act 1684796926 31.13.144.55 9761 typ srflx raddr
 100.78.247.179 rport 41775
 a=candidate:6 1 tcp-pass 174453758 52.114.252.130 59925 typ relay raddr
 31.13.144.55 rport 9761
 a=candidate:6 2 tcp-pass 174453758 52.114.252.130 59925 typ relay raddr
 31.13.144.55 rport 9761
 a=candidate:7 1 tcp-act 174846462 52.114.252.130 59925 typ relay raddr
 31.13.144.55 rport 9761
 a=candidate:7 2 tcp-act 174846462 52.114.252.130 59925 typ relay raddr
 31.13.144.55 rport 9761
 a=x-candidate-info:4 network-type=WWAN
 a=x-candidate-info:1 network-type=WWAN
 a=x-candidate-info:2 network-type=WWAN
 a=x-candidate-info:3 network-type=WWAN
 a=x-candidate-info:5 network-type=WWAN
 a=x-candidate-info:6 network-type=WWAN
 a=x-candidate-info:7 network-type=WWAN
 a=crypto:1 AES_CM_128_HMAC_SHA1_32
 inline:DY3r3DWRojJm94CJQ83OAavmlRCwPf5ciRxHCT40|2^31
 a=crypto:2 AES_CM_128_HMAC_SHA1_80
 inline:DY3r3DWRojJm94CJQ83OAavmlRCwPf5ciRxHCT40|2^31
 a=crypto:3 AES_CM_128_HMAC_SHA1_80
 inline:DY3r3DWRojJm94CJQ83OAavmlRCwPf5ciRxHCT40|2^31|1:1
 a=rtpmap:104 SILK/16000
 a=fmtp:104 useinbandfec=1; usedtx=0
 a=rtpmap:9 G722/8000
 a=rtpmap:111 SIREN/16000
 a=fmtp:111 bitrate=16000
 a=rtpmap:18 G729/8000
 a=rtpmap:0 PCMU/8000
 a=rtpmap:8 PCMA/8000
 a=rtpmap:103 SILK/8000
 a=fmtp:103 useinbandfec=1; usedtx=0
 a=rtpmap:97 RED/8000
 a=rtpmap:13 CN/8000
 a=rtpmap:118 CN/16000
 a=rtpmap:119 CN/24000
 a=rtpmap:101 telephone-event/8000
 a=fmtp:101 0-16
 a=ptime:20
 a=maxptime:200



 and my 200OK to MS is:

 2020/04/09 22:55:19.976427 KAMAILIO_IP:5061 -> 52.114.7.24:1024
 SIP/2.0 200 OK
 Record-Route:
 
 Record-Route:
 
 Via: SIP/2.0/TLS 52.114.7.24:5061;rport=1024;branch=z9hG4bKdb903e2c

Re: [SR-Users] kamailio as SBC for Teams

2020-04-10 Thread Sergiu Pojoga

You have too many RR of Kamailio, x1 FQDN, x3 IP. Why?

IMO, you should have only 2 of Kamailio, if you're doing transport
conversion. Both FQDNs + ";r2=on". MS clearly says FQDN everywhere, no IP,
especially RR

On Fri, Apr 10, 2020 at 7:06 AM Aidar Kamalov 
wrote:

> Thanks for the answer, I have disabled forse_rport() for Teams side,
> responses now going to address in Via header, but it is not resolved my
> issue, no ACK from Teams :(
>
> чт, 9 апр. 2020 г. в 18:22, Sergiu Pojoga :
>
>> Hi Aydar,
>>
>> Request from MS proxy has  VIA: SIP/2.0/TLS 52.114.7.24:5061, that's
>> where your reply should go. You're sending to 52.114.7.24:1024 instead?
>>
>> Also, looks like you're missing "r2=on" on the other RR, only one has it.
>>
>> Cheers,
>>
>> On Thu, Apr 9, 2020 at 11:09 AM Aidar Kamalov 
>> wrote:
>>
>>> Hello,
>>>
>>> I read https://skalatan.de/en/blog/kamailio-sbc-teams and trying to use
>>> kamailio for teams.
>>> But I faced that MS not responding ACK to my 200OK. Somethin is wrong,
>>> but I don't know what. I call from teams to kamailio.
>>> Can you help me please
>>>
>>> This is initial INVITE from Teams:
>>> 2020/04/09 22:55:17.346092 52.114.7.24:1024 -> KAMAILIO_IP:5061
>>> INVITE sip:+x@MY_KAMAILIO_FQDN:5061;user=phone;transport=tls
>>> SIP/2.0
>>> FROM: Aidar Kamalov>> ;user=phone>;tag=de28a5b5333b451a97312097f91f5564
>>> TO: 
>>> CSEQ: 1 INVITE
>>> CALL-ID: 3d5ad3cdd01457be94d127fa20478cf1
>>> MAX-FORWARDS: 70
>>> VIA: SIP/2.0/TLS 52.114.7.24:5061;branch=z9hG4bKdb903e2c
>>> RECORD-ROUTE: >> ;transport=tls;lr>
>>> CONTACT: >> ;x-i=903eeaac-b19e-43a0-8e75-bb222049922a;x-c=3d5ad3cdd01457be94d127fa20478cf1/d/8/d3d2c2e3f3c14f88bb2fe843b4bc70e4>
>>> CONTENT-LENGTH: 2426
>>> USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.4.4.3 i.ASEA.5
>>> CONTENT-TYPE: application/sdp
>>> ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY
>>>
>>> v=0
>>> o=- 0 0 IN IP4 52.114.252.146
>>> s=session
>>> c=IN IP4 52.114.252.146
>>> b=CT:5
>>> t=0 0
>>> m=audio 52939 RTP/SAVP 104 9 111 18 0 8 103 97 13 118 119 101
>>> a=rtcp:52925
>>> a=ice-ufrag:rKBm
>>> a=ice-pwd:BkjUnkfIvYV5pjteSteevL1O
>>> a=rtcp-mux
>>> a=candidate:4 1 UDP 184547839 52.114.252.146 52939 typ relay raddr
>>> 31.13.144.55 rport 57780
>>> a=candidate:4 2 UDP 184547326 52.114.252.146 52925 typ relay raddr
>>> 31.13.144.55 rport 57781
>>> a=candidate:1 1 tcp-act 2121006590 100.78.247.179 1024 typ host
>>> a=candidate:1 2 tcp-act 2121006590 100.78.247.179 1024 typ host
>>> a=candidate:2 1 UDP 2130705919 100.78.247.179 39182 typ host
>>> a=candidate:2 2 UDP 2130705406 100.78.247.179 39183 typ host
>>> a=candidate:3 1 UDP 1694497791 31.13.144.55 57780 typ srflx raddr
>>> 100.78.247.179 rport 39182
>>> a=candidate:3 2 UDP 1694497278 31.13.144.55 57781 typ srflx raddr
>>> 100.78.247.179 rport 39183
>>> a=candidate:5 1 tcp-act 1684796926 31.13.144.55 9761 typ srflx raddr
>>> 100.78.247.179 rport 41775
>>> a=candidate:5 2 tcp-act 1684796926 31.13.144.55 9761 typ srflx raddr
>>> 100.78.247.179 rport 41775
>>> a=candidate:6 1 tcp-pass 174453758 52.114.252.130 59925 typ relay raddr
>>> 31.13.144.55 rport 9761
>>> a=candidate:6 2 tcp-pass 174453758 52.114.252.130 59925 typ relay raddr
>>> 31.13.144.55 rport 9761
>>> a=candidate:7 1 tcp-act 174846462 52.114.252.130 59925 typ relay raddr
>>> 31.13.144.55 rport 9761
>>> a=candidate:7 2 tcp-act 174846462 52.114.252.130 59925 typ relay raddr
>>> 31.13.144.55 rport 9761
>>> a=x-candidate-info:4 network-type=WWAN
>>> a=x-candidate-info:1 network-type=WWAN
>>> a=x-candidate-info:2 network-type=WWAN
>>> a=x-candidate-info:3 network-type=WWAN
>>> a=x-candidate-info:5 network-type=WWAN
>>> a=x-candidate-info:6 network-type=WWAN
>>> a=x-candidate-info:7 network-type=WWAN
>>> a=crypto:1 AES_CM_128_HMAC_SHA1_32
>>> inline:DY3r3DWRojJm94CJQ83OAavmlRCwPf5ciRxHCT40|2^31
>>> a=crypto:2 AES_CM_128_HMAC_SHA1_80
>>> inline:DY3r3DWRojJm94CJQ83OAavmlRCwPf5ciRxHCT40|2^31
>>> a=crypto:3 AES_CM_128_HMAC_SHA1_80
>>> inline:DY3r3DWRojJm94CJQ83OAavmlRCwPf5ciRxHCT40|2^31|1:1
>>> a=rtpmap:104 SILK/16000
>>> a=fmtp:104 useinbandfec=1; usedtx=0
>>> a=rtpmap:9 G722/8000
>>> a=rtpmap:111 SIREN/16000
>>> a=fmtp:111 bitrate=16000
>>> a=rtpmap:18 G729/8000
>>> a=rtpmap:0 PCMU/8000
>>> a=rtpmap:8 PCMA/8000
>>> a=rtpmap:103 SILK/8000
>>> a=fmtp:103 useinbandfec=1; usedtx=0
>>> a=rtpmap:97 RED/8000
>>> a=rtpmap:13 CN/8000
>>> a=rtpmap:118 CN/16000
>>> a=rtpmap:119 CN/24000
>>> a=rtpmap:101 telephone-event/8000
>>> a=fmtp:101 0-16
>>> a=ptime:20
>>> a=maxptime:200
>>>
>>>
>>>
>>> and my 200OK to MS is:
>>>
>>> 2020/04/09 22:55:19.976427 KAMAILIO_IP:5061 -> 52.114.7.24:1024
>>> SIP/2.0 200 OK
>>> Record-Route:
>>> 
>>> Record-Route:
>>> 
>>> Via: SIP/2.0/TLS 52.114.7.24:5061;rport=1024;branch=z9hG4bKdb903e2c
>>> Record-Route:
>>> 
>>> Record-Route:
>>> 
>>> Record-Route:
>>> 
>>> Record-Route:
>>> 
>>> Record-Route: >> ;transport=tls;lr>
>>> To: >> :5061;user=phone>;tag=3795432917-393759697
>>> From: >>

Re: [SR-Users] kamailio as SBC for Teams

2020-04-10 Thread Aidar Kamalov

Thanks for the answer, I have disabled forse_rport() for Teams side,
responses now going to address in Via header, but it is not resolved my
issue, no ACK from Teams :(

чт, 9 апр. 2020 г. в 18:22, Sergiu Pojoga :

> Hi Aydar,
>
> Request from MS proxy has  VIA: SIP/2.0/TLS 52.114.7.24:5061, that's
> where your reply should go. You're sending to 52.114.7.24:1024 instead?
>
> Also, looks like you're missing "r2=on" on the other RR, only one has it.
>
> Cheers,
>
> On Thu, Apr 9, 2020 at 11:09 AM Aidar Kamalov 
> wrote:
>
>> Hello,
>>
>> I read https://skalatan.de/en/blog/kamailio-sbc-teams and trying to use
>> kamailio for teams.
>> But I faced that MS not responding ACK to my 200OK. Somethin is wrong,
>> but I don't know what. I call from teams to kamailio.
>> Can you help me please
>>
>> This is initial INVITE from Teams:
>> 2020/04/09 22:55:17.346092 52.114.7.24:1024 -> KAMAILIO_IP:5061
>> INVITE sip:+x@MY_KAMAILIO_FQDN:5061;user=phone;transport=tls
>> SIP/2.0
>> FROM: Aidar Kamalov> ;user=phone>;tag=de28a5b5333b451a97312097f91f5564
>> TO: 
>> CSEQ: 1 INVITE
>> CALL-ID: 3d5ad3cdd01457be94d127fa20478cf1
>> MAX-FORWARDS: 70
>> VIA: SIP/2.0/TLS 52.114.7.24:5061;branch=z9hG4bKdb903e2c
>> RECORD-ROUTE: > ;transport=tls;lr>
>> CONTACT: > ;x-i=903eeaac-b19e-43a0-8e75-bb222049922a;x-c=3d5ad3cdd01457be94d127fa20478cf1/d/8/d3d2c2e3f3c14f88bb2fe843b4bc70e4>
>> CONTENT-LENGTH: 2426
>> USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.4.4.3 i.ASEA.5
>> CONTENT-TYPE: application/sdp
>> ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY
>>
>> v=0
>> o=- 0 0 IN IP4 52.114.252.146
>> s=session
>> c=IN IP4 52.114.252.146
>> b=CT:5
>> t=0 0
>> m=audio 52939 RTP/SAVP 104 9 111 18 0 8 103 97 13 118 119 101
>> a=rtcp:52925
>> a=ice-ufrag:rKBm
>> a=ice-pwd:BkjUnkfIvYV5pjteSteevL1O
>> a=rtcp-mux
>> a=candidate:4 1 UDP 184547839 52.114.252.146 52939 typ relay raddr
>> 31.13.144.55 rport 57780
>> a=candidate:4 2 UDP 184547326 52.114.252.146 52925 typ relay raddr
>> 31.13.144.55 rport 57781
>> a=candidate:1 1 tcp-act 2121006590 100.78.247.179 1024 typ host
>> a=candidate:1 2 tcp-act 2121006590 100.78.247.179 1024 typ host
>> a=candidate:2 1 UDP 2130705919 100.78.247.179 39182 typ host
>> a=candidate:2 2 UDP 2130705406 100.78.247.179 39183 typ host
>> a=candidate:3 1 UDP 1694497791 31.13.144.55 57780 typ srflx raddr
>> 100.78.247.179 rport 39182
>> a=candidate:3 2 UDP 1694497278 31.13.144.55 57781 typ srflx raddr
>> 100.78.247.179 rport 39183
>> a=candidate:5 1 tcp-act 1684796926 31.13.144.55 9761 typ srflx raddr
>> 100.78.247.179 rport 41775
>> a=candidate:5 2 tcp-act 1684796926 31.13.144.55 9761 typ srflx raddr
>> 100.78.247.179 rport 41775
>> a=candidate:6 1 tcp-pass 174453758 52.114.252.130 59925 typ relay raddr
>> 31.13.144.55 rport 9761
>> a=candidate:6 2 tcp-pass 174453758 52.114.252.130 59925 typ relay raddr
>> 31.13.144.55 rport 9761
>> a=candidate:7 1 tcp-act 174846462 52.114.252.130 59925 typ relay raddr
>> 31.13.144.55 rport 9761
>> a=candidate:7 2 tcp-act 174846462 52.114.252.130 59925 typ relay raddr
>> 31.13.144.55 rport 9761
>> a=x-candidate-info:4 network-type=WWAN
>> a=x-candidate-info:1 network-type=WWAN
>> a=x-candidate-info:2 network-type=WWAN
>> a=x-candidate-info:3 network-type=WWAN
>> a=x-candidate-info:5 network-type=WWAN
>> a=x-candidate-info:6 network-type=WWAN
>> a=x-candidate-info:7 network-type=WWAN
>> a=crypto:1 AES_CM_128_HMAC_SHA1_32
>> inline:DY3r3DWRojJm94CJQ83OAavmlRCwPf5ciRxHCT40|2^31
>> a=crypto:2 AES_CM_128_HMAC_SHA1_80
>> inline:DY3r3DWRojJm94CJQ83OAavmlRCwPf5ciRxHCT40|2^31
>> a=crypto:3 AES_CM_128_HMAC_SHA1_80
>> inline:DY3r3DWRojJm94CJQ83OAavmlRCwPf5ciRxHCT40|2^31|1:1
>> a=rtpmap:104 SILK/16000
>> a=fmtp:104 useinbandfec=1; usedtx=0
>> a=rtpmap:9 G722/8000
>> a=rtpmap:111 SIREN/16000
>> a=fmtp:111 bitrate=16000
>> a=rtpmap:18 G729/8000
>> a=rtpmap:0 PCMU/8000
>> a=rtpmap:8 PCMA/8000
>> a=rtpmap:103 SILK/8000
>> a=fmtp:103 useinbandfec=1; usedtx=0
>> a=rtpmap:97 RED/8000
>> a=rtpmap:13 CN/8000
>> a=rtpmap:118 CN/16000
>> a=rtpmap:119 CN/24000
>> a=rtpmap:101 telephone-event/8000
>> a=fmtp:101 0-16
>> a=ptime:20
>> a=maxptime:200
>>
>>
>>
>> and my 200OK to MS is:
>>
>> 2020/04/09 22:55:19.976427 KAMAILIO_IP:5061 -> 52.114.7.24:1024
>> SIP/2.0 200 OK
>> Record-Route:
>> 
>> Record-Route:
>> 
>> Via: SIP/2.0/TLS 52.114.7.24:5061;rport=1024;branch=z9hG4bKdb903e2c
>> Record-Route:
>> 
>> Record-Route:
>> 
>> Record-Route:
>> 
>> Record-Route:
>> 
>> Record-Route: > ;transport=tls;lr>
>> To: > :5061;user=phone>;tag=3795432917-393759697
>> From: > ;user=phone>;tag=de28a5b5333b451a97312097f91f5564
>> Call-ID: 3d5ad3cdd01457be94d127fa20478cf1
>> CSeq: 1 INVITE
>> Allow:
>> PUBLISH,MESSAGE,UPDATE,PRACK,SUBSCRIBE,REFER,INFO,NOTIFY,REGISTER,OPTIONS,BYE,INVITE,ACK,CANCEL
>> Content-Type: application/sdp
>> Accept: application/sdp
>> Content-Length: 282
>> User-Agent: MY_DOMAIN
>> Contact:
>> 
>>
>> v=0
>> o=ETPI-MSX1 0 0 IN IP4 KAMAILIO_IP
>> s=sip call
>> c=IN IP4 KAMAILIO_IP
>> t=0 0
>> m=audio

Re: [SR-Users] kamailio as SBC for Teams

2020-04-09 Thread Sergiu Pojoga

Hi Aydar,

Request from MS proxy has  VIA: SIP/2.0/TLS 52.114.7.24:5061, that's where
your reply should go. You're sending to 52.114.7.24:1024 instead?

Also, looks like you're missing "r2=on" on the other RR, only one has it.

Cheers,

On Thu, Apr 9, 2020 at 11:09 AM Aidar Kamalov 
wrote:

> Hello,
>
> I read https://skalatan.de/en/blog/kamailio-sbc-teams and trying to use
> kamailio for teams.
> But I faced that MS not responding ACK to my 200OK. Somethin is wrong, but
> I don't know what. I call from teams to kamailio.
> Can you help me please
>
> This is initial INVITE from Teams:
> 2020/04/09 22:55:17.346092 52.114.7.24:1024 -> KAMAILIO_IP:5061
> INVITE sip:+x@MY_KAMAILIO_FQDN:5061;user=phone;transport=tls
> SIP/2.0
> FROM: Aidar Kamalov ;user=phone>;tag=de28a5b5333b451a97312097f91f5564
> TO: 
> CSEQ: 1 INVITE
> CALL-ID: 3d5ad3cdd01457be94d127fa20478cf1
> MAX-FORWARDS: 70
> VIA: SIP/2.0/TLS 52.114.7.24:5061;branch=z9hG4bKdb903e2c
> RECORD-ROUTE:  ;transport=tls;lr>
> CONTACT:  ;x-i=903eeaac-b19e-43a0-8e75-bb222049922a;x-c=3d5ad3cdd01457be94d127fa20478cf1/d/8/d3d2c2e3f3c14f88bb2fe843b4bc70e4>
> CONTENT-LENGTH: 2426
> USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.4.4.3 i.ASEA.5
> CONTENT-TYPE: application/sdp
> ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY
>
> v=0
> o=- 0 0 IN IP4 52.114.252.146
> s=session
> c=IN IP4 52.114.252.146
> b=CT:5
> t=0 0
> m=audio 52939 RTP/SAVP 104 9 111 18 0 8 103 97 13 118 119 101
> a=rtcp:52925
> a=ice-ufrag:rKBm
> a=ice-pwd:BkjUnkfIvYV5pjteSteevL1O
> a=rtcp-mux
> a=candidate:4 1 UDP 184547839 52.114.252.146 52939 typ relay raddr
> 31.13.144.55 rport 57780
> a=candidate:4 2 UDP 184547326 52.114.252.146 52925 typ relay raddr
> 31.13.144.55 rport 57781
> a=candidate:1 1 tcp-act 2121006590 100.78.247.179 1024 typ host
> a=candidate:1 2 tcp-act 2121006590 100.78.247.179 1024 typ host
> a=candidate:2 1 UDP 2130705919 100.78.247.179 39182 typ host
> a=candidate:2 2 UDP 2130705406 100.78.247.179 39183 typ host
> a=candidate:3 1 UDP 1694497791 31.13.144.55 57780 typ srflx raddr
> 100.78.247.179 rport 39182
> a=candidate:3 2 UDP 1694497278 31.13.144.55 57781 typ srflx raddr
> 100.78.247.179 rport 39183
> a=candidate:5 1 tcp-act 1684796926 31.13.144.55 9761 typ srflx raddr
> 100.78.247.179 rport 41775
> a=candidate:5 2 tcp-act 1684796926 31.13.144.55 9761 typ srflx raddr
> 100.78.247.179 rport 41775
> a=candidate:6 1 tcp-pass 174453758 52.114.252.130 59925 typ relay raddr
> 31.13.144.55 rport 9761
> a=candidate:6 2 tcp-pass 174453758 52.114.252.130 59925 typ relay raddr
> 31.13.144.55 rport 9761
> a=candidate:7 1 tcp-act 174846462 52.114.252.130 59925 typ relay raddr
> 31.13.144.55 rport 9761
> a=candidate:7 2 tcp-act 174846462 52.114.252.130 59925 typ relay raddr
> 31.13.144.55 rport 9761
> a=x-candidate-info:4 network-type=WWAN
> a=x-candidate-info:1 network-type=WWAN
> a=x-candidate-info:2 network-type=WWAN
> a=x-candidate-info:3 network-type=WWAN
> a=x-candidate-info:5 network-type=WWAN
> a=x-candidate-info:6 network-type=WWAN
> a=x-candidate-info:7 network-type=WWAN
> a=crypto:1 AES_CM_128_HMAC_SHA1_32
> inline:DY3r3DWRojJm94CJQ83OAavmlRCwPf5ciRxHCT40|2^31
> a=crypto:2 AES_CM_128_HMAC_SHA1_80
> inline:DY3r3DWRojJm94CJQ83OAavmlRCwPf5ciRxHCT40|2^31
> a=crypto:3 AES_CM_128_HMAC_SHA1_80
> inline:DY3r3DWRojJm94CJQ83OAavmlRCwPf5ciRxHCT40|2^31|1:1
> a=rtpmap:104 SILK/16000
> a=fmtp:104 useinbandfec=1; usedtx=0
> a=rtpmap:9 G722/8000
> a=rtpmap:111 SIREN/16000
> a=fmtp:111 bitrate=16000
> a=rtpmap:18 G729/8000
> a=rtpmap:0 PCMU/8000
> a=rtpmap:8 PCMA/8000
> a=rtpmap:103 SILK/8000
> a=fmtp:103 useinbandfec=1; usedtx=0
> a=rtpmap:97 RED/8000
> a=rtpmap:13 CN/8000
> a=rtpmap:118 CN/16000
> a=rtpmap:119 CN/24000
> a=rtpmap:101 telephone-event/8000
> a=fmtp:101 0-16
> a=ptime:20
> a=maxptime:200
>
>
>
> and my 200OK to MS is:
>
> 2020/04/09 22:55:19.976427 KAMAILIO_IP:5061 -> 52.114.7.24:1024
> SIP/2.0 200 OK
> Record-Route:
> 
> Record-Route:
> 
> Via: SIP/2.0/TLS 52.114.7.24:5061;rport=1024;branch=z9hG4bKdb903e2c
> Record-Route:
> 
> Record-Route:
> 
> Record-Route:
> 
> Record-Route:
> 
> Record-Route:  ;transport=tls;lr>
> To:  :5061;user=phone>;tag=3795432917-393759697
> From:  ;user=phone>;tag=de28a5b5333b451a97312097f91f5564
> Call-ID: 3d5ad3cdd01457be94d127fa20478cf1
> CSeq: 1 INVITE
> Allow:
> PUBLISH,MESSAGE,UPDATE,PRACK,SUBSCRIBE,REFER,INFO,NOTIFY,REGISTER,OPTIONS,BYE,INVITE,ACK,CANCEL
> Content-Type: application/sdp
> Accept: application/sdp
> Content-Length: 282
> User-Agent: MY_DOMAIN
> Contact:
> 
>
> v=0
> o=ETPI-MSX1 0 0 IN IP4 KAMAILIO_IP
> s=sip call
> c=IN IP4 KAMAILIO_IP
> t=0 0
> m=audio 12176 RTP/SAVP 8
> b=AS:64
> a=maxptime:20
> a=rtpmap:8 PCMA/8000
> a=sendrecv
> a=rtcp:12177
> a=crypto:1 AES_CM_128_HMAC_SHA1_32
> inline:03ZmcR+CxxB7k7C8QvWBgseYq7cH7py7VxqfLM8j
> a=ptime:20
>
>
> --
> Aydar A. Kamalov
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
>

[SR-Users] kamailio as SBC for Teams

2020-04-09 Thread Aidar Kamalov

Hello,

I read https://skalatan.de/en/blog/kamailio-sbc-teams and trying to use
kamailio for teams.
But I faced that MS not responding ACK to my 200OK. Somethin is wrong, but
I don't know what. I call from teams to kamailio.
Can you help me please

This is initial INVITE from Teams:
2020/04/09 22:55:17.346092 52.114.7.24:1024 -> KAMAILIO_IP:5061
INVITE sip:+x@MY_KAMAILIO_FQDN:5061;user=phone;transport=tls SIP/2.0
FROM: Aidar Kamalov;tag=de28a5b5333b451a97312097f91f5564
TO: 
CSEQ: 1 INVITE
CALL-ID: 3d5ad3cdd01457be94d127fa20478cf1
MAX-FORWARDS: 70
VIA: SIP/2.0/TLS 52.114.7.24:5061;branch=z9hG4bKdb903e2c
RECORD-ROUTE: 
CONTACT: 
CONTENT-LENGTH: 2426
USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.4.4.3 i.ASEA.5
CONTENT-TYPE: application/sdp
ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY

v=0
o=- 0 0 IN IP4 52.114.252.146
s=session
c=IN IP4 52.114.252.146
b=CT:5
t=0 0
m=audio 52939 RTP/SAVP 104 9 111 18 0 8 103 97 13 118 119 101
a=rtcp:52925
a=ice-ufrag:rKBm
a=ice-pwd:BkjUnkfIvYV5pjteSteevL1O
a=rtcp-mux
a=candidate:4 1 UDP 184547839 52.114.252.146 52939 typ relay raddr
31.13.144.55 rport 57780
a=candidate:4 2 UDP 184547326 52.114.252.146 52925 typ relay raddr
31.13.144.55 rport 57781
a=candidate:1 1 tcp-act 2121006590 100.78.247.179 1024 typ host
a=candidate:1 2 tcp-act 2121006590 100.78.247.179 1024 typ host
a=candidate:2 1 UDP 2130705919 100.78.247.179 39182 typ host
a=candidate:2 2 UDP 2130705406 100.78.247.179 39183 typ host
a=candidate:3 1 UDP 1694497791 31.13.144.55 57780 typ srflx raddr
100.78.247.179 rport 39182
a=candidate:3 2 UDP 1694497278 31.13.144.55 57781 typ srflx raddr
100.78.247.179 rport 39183
a=candidate:5 1 tcp-act 1684796926 31.13.144.55 9761 typ srflx raddr
100.78.247.179 rport 41775
a=candidate:5 2 tcp-act 1684796926 31.13.144.55 9761 typ srflx raddr
100.78.247.179 rport 41775
a=candidate:6 1 tcp-pass 174453758 52.114.252.130 59925 typ relay raddr
31.13.144.55 rport 9761
a=candidate:6 2 tcp-pass 174453758 52.114.252.130 59925 typ relay raddr
31.13.144.55 rport 9761
a=candidate:7 1 tcp-act 174846462 52.114.252.130 59925 typ relay raddr
31.13.144.55 rport 9761
a=candidate:7 2 tcp-act 174846462 52.114.252.130 59925 typ relay raddr
31.13.144.55 rport 9761
a=x-candidate-info:4 network-type=WWAN
a=x-candidate-info:1 network-type=WWAN
a=x-candidate-info:2 network-type=WWAN
a=x-candidate-info:3 network-type=WWAN
a=x-candidate-info:5 network-type=WWAN
a=x-candidate-info:6 network-type=WWAN
a=x-candidate-info:7 network-type=WWAN
a=crypto:1 AES_CM_128_HMAC_SHA1_32
inline:DY3r3DWRojJm94CJQ83OAavmlRCwPf5ciRxHCT40|2^31
a=crypto:2 AES_CM_128_HMAC_SHA1_80
inline:DY3r3DWRojJm94CJQ83OAavmlRCwPf5ciRxHCT40|2^31
a=crypto:3 AES_CM_128_HMAC_SHA1_80
inline:DY3r3DWRojJm94CJQ83OAavmlRCwPf5ciRxHCT40|2^31|1:1
a=rtpmap:104 SILK/16000
a=fmtp:104 useinbandfec=1; usedtx=0
a=rtpmap:9 G722/8000
a=rtpmap:111 SIREN/16000
a=fmtp:111 bitrate=16000
a=rtpmap:18 G729/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:103 SILK/8000
a=fmtp:103 useinbandfec=1; usedtx=0
a=rtpmap:97 RED/8000
a=rtpmap:13 CN/8000
a=rtpmap:118 CN/16000
a=rtpmap:119 CN/24000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=maxptime:200



and my 200OK to MS is:

2020/04/09 22:55:19.976427 KAMAILIO_IP:5061 -> 52.114.7.24:1024
SIP/2.0 200 OK
Record-Route:

Record-Route:

Via: SIP/2.0/TLS 52.114.7.24:5061;rport=1024;branch=z9hG4bKdb903e2c
Record-Route:

Record-Route:

Record-Route:

Record-Route:

Record-Route: 
To: ;tag=3795432917-393759697
From: ;tag=de28a5b5333b451a97312097f91f5564
Call-ID: 3d5ad3cdd01457be94d127fa20478cf1
CSeq: 1 INVITE
Allow:
PUBLISH,MESSAGE,UPDATE,PRACK,SUBSCRIBE,REFER,INFO,NOTIFY,REGISTER,OPTIONS,BYE,INVITE,ACK,CANCEL
Content-Type: application/sdp
Accept: application/sdp
Content-Length: 282
User-Agent: MY_DOMAIN
Contact:


v=0
o=ETPI-MSX1 0 0 IN IP4 KAMAILIO_IP
s=sip call
c=IN IP4 KAMAILIO_IP
t=0 0
m=audio 12176 RTP/SAVP 8
b=AS:64
a=maxptime:20
a=rtpmap:8 PCMA/8000
a=sendrecv
a=rtcp:12177
a=crypto:1 AES_CM_128_HMAC_SHA1_32
inline:03ZmcR+CxxB7k7C8QvWBgseYq7cH7py7VxqfLM8j
a=ptime:20


-- 
Aydar A. Kamalov
___
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 SBC for Microsoft Teams

2019-11-29 Thread Henning Westerholt

Hello Stefan,

it is certainly possible to get a certification for an open source software 
(server). Usually the work that needs to be done is related to documentation, 
testing and probably some packaging.

So far I did not looked into it that much. I think it is probably something 
that is more interesting from a commercial point of view and not in an open 
source project context.

Cheers,

Henning

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

From: sr-users  On Behalf Of Stefan
Sent: Friday, November 29, 2019 10:55 AM
To: Kamailio (SER) - Users Mailing List 
Cc: sr-...@lists.kamailio.org
Subject: Re: [SR-Users] Kamailio as SBC for Microsoft Teams

Hi list

Sorry for coming back to this older thread.
First: Thank you Henning for your blog post.

Does anyone know what is needed to get Kamailio listed on the certified SBC's 
at microsoft?
Is there already a plan to get Kamailio on this list?
https://docs.microsoft.com/en-us/microsoftteams/direct-routing-border-controllers

Thank you and regards
Stefan

Am 28.10.19 um 17:21 schrieb Henning Westerholt:
Hello,

I have created a "How-To" blog post on using Kamailio as "session border 
controller" for Microsoft Teams Direct Routing:

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

You can this way use all the existing possibilities that Kamailio provide to 
interact with MS Teams as well.

Best regards,

Henning

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




___

Kamailio (SER) - Users Mailing List

sr-users@lists.kamailio.org<mailto: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 as SBC for Microsoft Teams

2019-11-29 Thread Julien Chavanton

Hi, I know they have a few customisations to SIP and RTP.

Nothing  concerning from what I know.

One example the SDP RTCP address, I do not have the RFC on top of my head.

But the certification is probably only needed for them yo list you as a
certified equipment, etc.

On Fri, Nov 29, 2019, 01:56 Stefan  wrote:

> Hi list
>
> Sorry for coming back to this older thread.
> First: Thank you Henning for your blog post.
>
> Does anyone know what is needed to get Kamailio listed on the certified
> SBC's at microsoft?
> Is there already a plan to get Kamailio on this list?
>
> https://docs.microsoft.com/en-us/microsoftteams/direct-routing-border-controllers
>
> Thank you and regards
> Stefan
>
>
> Am 28.10.19 um 17:21 schrieb Henning Westerholt:
>
> Hello,
>
>
>
> I have created a “How-To” blog post on using Kamailio as “session border
> controller” for Microsoft Teams Direct Routing:
>
>
>
> https://skalatan.de/de/blog/kamailio-sbc-teams
>
>
>
> You can this way use all the existing possibilities that Kamailio provide
> to interact with MS Teams as well.
>
>
>
> Best regards,
>
>
>
> Henning
>
>
>
> --
>
> Henning Westerholt - https://skalatan.de/blog/
>
> Kamailio services - https://skalatan.de/services
>
>
>
> ___
> Kamailio (SER) - Users Mailing 
> Listsr-users@lists.kamailio.orghttps://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
>
___
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 SBC for Microsoft Teams

2019-11-29 Thread Lợi Đặng

Hi, I think it's not needed/able to get kamailio listed as certified SBC by
Microsoft because the configuration is raw and flexible.
The `How-to` is just about the SIP stuffs fulfilling Microsoft's
requirements for the connectivity.
Your request should be valid with some GUI project that wrapping the
kamailio, not with the kamailio itself.

rgds,
Loi Dang Thanh
Phone : +84. 774.735.448
Email : loi.dangth...@gmail.com


On Fri, Nov 29, 2019 at 4:55 PM Stefan  wrote:

> Hi list
>
> Sorry for coming back to this older thread.
> First: Thank you Henning for your blog post.
>
> Does anyone know what is needed to get Kamailio listed on the certified
> SBC's at microsoft?
> Is there already a plan to get Kamailio on this list?
>
> https://docs.microsoft.com/en-us/microsoftteams/direct-routing-border-controllers
>
> Thank you and regards
> Stefan
>
>
> Am 28.10.19 um 17:21 schrieb Henning Westerholt:
>
> Hello,
>
>
>
> I have created a “How-To” blog post on using Kamailio as “session border
> controller” for Microsoft Teams Direct Routing:
>
>
>
> https://skalatan.de/de/blog/kamailio-sbc-teams
>
>
>
> You can this way use all the existing possibilities that Kamailio provide
> to interact with MS Teams as well.
>
>
>
> Best regards,
>
>
>
> Henning
>
>
>
> --
>
> Henning Westerholt - https://skalatan.de/blog/
>
> Kamailio services - https://skalatan.de/services
>
>
>
> ___
> Kamailio (SER) - Users Mailing 
> Listsr-users@lists.kamailio.orghttps://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
>
___
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 SBC for Microsoft Teams

2019-11-29 Thread Stefan


Hi list

Sorry for coming back to this older thread.
First: Thank you Henning for your blog post.

Does anyone know what is needed to get Kamailio listed on the certified 
SBC's at microsoft?

Is there already a plan to get Kamailio on this list?
https://docs.microsoft.com/en-us/microsoftteams/direct-routing-border-controllers

Thank you and regards
Stefan


Am 28.10.19 um 17:21 schrieb Henning Westerholt:


Hello,

I have created a “How-To” blog post on using Kamailio as “session 
border controller” for Microsoft Teams Direct Routing:


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

You can this way use all the existing possibilities that Kamailio 
provide to interact with MS Teams as well.


Best regards,

Henning

--

Henning Westerholt - https://skalatan.de/blog/

Kamailio services - https://skalatan.de/services


___
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 as SBC for Microsoft Teams

2019-10-30 Thread Henning Westerholt

Great addition, thanks Karsten!

Am 30.10.19 um 08:08 schrieb Karsten Horsmann:
Hi Henning,

nice to see that howto. Thanks.

Maybe interesting for the list - i try to verify the ms-teams calls with tls 
and use the permission module functions as "helper":

# account only INVITEs
if (is_method("INVITE")) {
setflag(FLT_ACC); # do accounting

xlog("L_INFO", "---> tls_peer_subject 
<$tls_peer_subject> tls_peer_subject_cn <$tls_peer_subject_cn> 
tls_peer_verified <$tls_peer_verified> tls_peer_server_name 
<$tls_peer_server_name> \n");
xlog("L_INFO", "---> $Ri:$Rp src_user=$fU 
src_domain=$fd src_ip=$si dst_ouser=$tU dst_user=$rU dst_domain=$rd\n");


if($tls_peer_verified == -1) {
xlog("L_INFO", "tls_peer_subject_cn 
$tls_peer_subject_cn is NOT verfied!\n");
return;
}
$var(dns) = $tls_peer_subject_cn;
$var(group) = allow_address_group($var(dns), $Rp);
xlog("L_INFO", "---> allow_address_group var(group) 
$var(group) var(dns) $var(dns) Rp $Rp\n");
if ($var(group) == -1) {
xlog("L_INFO", "Trunk is not activate for registrar 
DNS_GROUP:[$var(dns)], Source: [$si], Destination: [$Ri] Port:[$Rp]\n");
return;
}
}


Oct 30 07:55:46 sbc1 /usr/sbin/kamailio[2689]: INFO: {1 1 INVITE 
34b77c805b475a39a669b03544f87fae}

Re: [SR-Users] Kamailio as SBC for Microsoft Teams

2019-10-30 Thread Karsten Horsmann

Hi Henning,

nice to see that howto. Thanks.

Maybe interesting for the list - i try to verify the ms-teams calls with
tls and use the permission module functions as "helper":

# account only INVITEs
if (is_method("INVITE")) {
setflag(FLT_ACC); # do accounting

xlog("L_INFO", "---> tls_peer_subject
<$tls_peer_subject> tls_peer_subject_cn <$tls_peer_subject_cn>
tls_peer_verified <$tls_peer_verified> tls_peer_server_name
<$tls_peer_server_name> \n");
xlog("L_INFO", "---> $Ri:$Rp src_user=$fU
src_domain=$fd src_ip=$si dst_ouser=$tU dst_user=$rU dst_domain=$rd\n");


if($tls_peer_verified == -1) {
xlog("L_INFO", "tls_peer_subject_cn
$tls_peer_subject_cn is NOT verfied!\n");
return;
}
$var(dns) = $tls_peer_subject_cn;
$var(group) = allow_address_group($var(dns), $Rp);
xlog("L_INFO", "---> allow_address_group var(group)
$var(group) var(dns) $var(dns) Rp $Rp\n");
if ($var(group) == -1) {
xlog("L_INFO", "Trunk is not activate for registrar
DNS_GROUP:[$var(dns)], Source: [$si], Destination: [$Ri] Port:[$Rp]\n");
return;
}
}


Oct 30 07:55:46 sbc1 /usr/sbin/kamailio[2689]: INFO: {1 1 INVITE
34b77c805b475a39a669b03544f87fae}

Re: [SR-Users] Kamailio as SBC for Microsoft Teams

2019-10-29 Thread Henning Westerholt

Hello Rhys,

thanks. About the presence integration question - according to my research 
currently the only possibility would be to use the existing Skype APIs and then 
use this (per interop-mode) also in MS Teams.

Microsoft announced the availability of a API to set the presence status also 
for Teams, this is now scheduled for Q1 2020. There are other limitations which 
also needs to be solved from MS and they are also scheduled for Q1 2020.

Feel free to contact me directly if you are interested in this topics.

Cheers,

Henning

Am 29.10.19 um 08:54 schrieb Rhys Hanrahan:

Hi Henning,


This is a great article, thanks for sharing. I'm wondering if you've 
experimented with the possibility of integration of presence/dialog information 
with teams as well?


Pretty much every integration guide I've seen on MS's UC solutions, including 
the previous ones (Lync, Communicator, SFB ) always seem limited to integrating 
calling via trunks. To me, the integration is not complete unless you can 
integrate presence things like:


  *   If a user is on the phone then their status should be "busy" on Teams. 
When off call, set back to Available.
  *   If a user is on a call in teams, our PBX should consider their PBX 
extension as "in use".


Not sure it's possible, because I haven't seen anything of the sort being done 
yet, but I'm curious if this is something you looked into at all?

Thanks.
Rhys.

On Tue, Oct 29, 2019 at 3:22 AM Henning Westerholt 
mailto:h...@skalatan.de>> wrote:
Hello,

I have created a “How-To” blog post on using Kamailio as “session border 
controller” for Microsoft Teams Direct Routing:

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

You can this way use all the existing possibilities that Kamailio provide to 
interact with MS Teams as well.

Best regards,

Henning

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

___
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


--
Kamailio Merchandising - https://skalatan.de/merchandising/
Kamailio services - https://skalatan.de/services
Henning Westerholt - https://skalatan.de/blog/
___
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 SBC for Microsoft Teams

2019-10-29 Thread Lợi Đặng

Pretty nice article.
Thanks in advance.

rgds,
Loi Dang Thanh
Phone : +84. 774.735.448
Email : loi.dangth...@gmail.com


On Tue, Oct 29, 2019 at 2:55 PM Rhys Hanrahan 
wrote:

> Hi Henning,
>
>
> This is a great article, thanks for sharing. I'm wondering if you've
> experimented with the possibility of integration of presence/dialog
> information with teams as well?
>
>
> Pretty much every integration guide I've seen on MS's UC solutions,
> including the previous ones (Lync, Communicator, SFB ) always seem limited
> to integrating calling via trunks. To me, the integration is not complete
> unless you can integrate presence things like:
>
>
>
>- If a user is on the phone then their status should be "busy" on
>Teams. When off call, set back to Available.
>- If a user is on a call in teams, our PBX should consider their PBX
>extension as "in use".
>
>
> Not sure it's possible, because I haven't seen anything of the sort being
> done yet, but I'm curious if this is something you looked into at all?
>
> Thanks.
> Rhys.
>
> On Tue, Oct 29, 2019 at 3:22 AM Henning Westerholt  wrote:
>
>> Hello,
>>
>>
>>
>> I have created a “How-To” blog post on using Kamailio as “session border
>> controller” for Microsoft Teams Direct Routing:
>>
>>
>>
>> https://skalatan.de/de/blog/kamailio-sbc-teams
>>
>>
>>
>> You can this way use all the existing possibilities that Kamailio provide
>> to interact with MS Teams as well.
>>
>>
>>
>> Best regards,
>>
>>
>>
>> Henning
>>
>>
>>
>> --
>>
>> Henning Westerholt - https://skalatan.de/blog/
>>
>> Kamailio services - https://skalatan.de/services
>>
>>
>> ___
>> 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
>
___
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 SBC for Microsoft Teams

2019-10-29 Thread Rhys Hanrahan

Hi Henning,

This is a great article, thanks for sharing. I'm wondering if you've
experimented with the possibility of integration of presence/dialog
information with teams as well?

Pretty much every integration guide I've seen on MS's UC solutions,
including the previous ones (Lync, Communicator, SFB ) always seem limited
to integrating calling via trunks. To me, the integration is not complete
unless you can integrate presence things like:

   - If a user is on the phone then their status should be "busy" on Teams.
   When off call, set back to Available.
   - If a user is on a call in teams, our PBX should consider their PBX
   extension as "in use".

Not sure it's possible, because I haven't seen anything of the sort being
done yet, but I'm curious if this is something you looked into at all?

Thanks.
Rhys.

On Tue, Oct 29, 2019 at 3:22 AM Henning Westerholt  wrote:

> Hello,
>
>
>
> I have created a “How-To” blog post on using Kamailio as “session border
> controller” for Microsoft Teams Direct Routing:
>
>
>
> https://skalatan.de/de/blog/kamailio-sbc-teams
>
>
>
> You can this way use all the existing possibilities that Kamailio provide
> to interact with MS Teams as well.
>
>
>
> Best regards,
>
>
>
> Henning
>
>
>
> --
>
> Henning Westerholt - https://skalatan.de/blog/
>
> Kamailio services - https://skalatan.de/services
>
>
> ___
> 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 as SBC for Microsoft Teams

2019-10-28 Thread Henning Westerholt

Hi Daniel,

thanks you – already added. 

Cheers,

Henning

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

From: Daniel-Constantin Mierla 
Sent: Monday, October 28, 2019 6:59 PM
To: Kamailio (SER) - Users Mailing List ; Henning 
Westerholt 
Subject: Re: [SR-Users] Kamailio as SBC for Microsoft Teams


Hello,

thanks for sharing! This can be added as a news article on kamailio.org, over 
the time can be found easier there than in the mailing list archive...

Cheers,
Daniel
On 28.10.19 17:21, Henning Westerholt wrote:
Hello,

I have created a “How-To” blog post on using Kamailio as “session border 
controller” for Microsoft Teams Direct Routing:

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

You can this way use all the existing possibilities that Kamailio provide to 
interact with MS Teams as well.

Best regards,

Henning

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




___

Kamailio (SER) - Users Mailing List

sr-users@lists.kamailio.org<mailto:sr-users@lists.kamailio.org>

https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

--

Daniel-Constantin Mierla -- www.asipto.com<http://www.asipto.com>

www.twitter.com/miconda<http://www.twitter.com/miconda> -- 
www.linkedin.com/in/miconda<http://www.linkedin.com/in/miconda>

Kamailio Advanced Training, Oct 21-23, 2019, Berlin, Germany -- 
https://asipto.com/u/kat
___
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 SBC for Microsoft Teams

2019-10-28 Thread Daniel-Constantin Mierla

Hello,

thanks for sharing! This can be added as a news article on kamailio.org,
over the time can be found easier there than in the mailing list archive...

Cheers,
Daniel

On 28.10.19 17:21, Henning Westerholt wrote:
>
> Hello,
>
>  
>
> I have created a “How-To” blog post on using Kamailio as “session
> border controller” for Microsoft Teams Direct Routing:
>
>  
>
> https://skalatan.de/de/blog/kamailio-sbc-teams
>
>  
>
> You can this way use all the existing possibilities that Kamailio
> provide to interact with MS Teams as well.
>
>  
>
> Best regards,
>
>  
>
> Henning
>
>  
>
> -- 
>
> Henning Westerholt - https://skalatan.de/blog/
>
> Kamailio services - https://skalatan.de/services
>
>  
>
>
> ___
> 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 Advanced Training, Oct 21-23, 2019, Berlin, Germany -- 
https://asipto.com/u/kat

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

[SR-Users] Kamailio as SBC for Microsoft Teams

2019-10-28 Thread Henning Westerholt

Hello,

I have created a "How-To" blog post on using Kamailio as "session border 
controller" for Microsoft Teams Direct Routing:

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

You can this way use all the existing possibilities that Kamailio provide to 
interact with MS Teams as well.

Best regards,

Henning

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

___
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 SBC

2018-10-25 Thread Ellad Yatsko

uthorized Kamailio retransmits it to User - this is
>>> an intermediate step, no action needed
>>>    - User repeats steps on Registration with the Nonce
>>>    - on receiving OK [from Asterisk] for the memorized dialog Kamailio
>>> retransmits OK to User and composes User Location
>>>    - on receiving NOT FOUND, FORBIDDEN, etc Kamailio retransmits SIP
>>> answer to User and after several unsuccessful attempts blocks User IP
>>>    - Fail2Ban completes the rest - inserts new rule
>>> Every time Kamailio retransmit SIP packet to the User from Asterisk it
>>> HIDES topology (IP/UDP headers and all SIP-related Info from SIP
>>> Packets). User should know just about Kamailio as about its counterpart.
>>>
>>> How to track SIP REGISTER related messages inside Kamailio?
>>>
>>> TO: Yu Boot - is it "standalone" implementation? How do you think? :-)
>>>
>>> Kind regards,
>>> Ellad
>>>
>>>
>>> 22.10.2018 20:16, Yu Boot пишет:
>>>> I can help you with cfg, if you 're ready to implement standalone
>>>> softswitch on your Kamailio :)
>>>>
>>>>
>>>> 22.10.2018 17:21, Ellad Yatsko пишет:
>>>>> May you help?.. :-)
>>>>>
>>>>> Kind regards,
>>>>> Ellad
>>>>>
>>>>> 22.10.2018 17:12, Alex Balashov пишет:
>>>>>> I did not say that my article represents a complete answer to every
>>>>>> part
>>>>>> of every one of your questions, at every level of abstraction and
>>>>>> specificity. Just that it might be helpful. :-)
>>>>>>
>>>>>> On Mon, Oct 22, 2018 at 04:40:03PM +0300, Ellad Yatsko wrote:
>>>>>>
>>>>>>> Dear Alex,
>>>>>>>
>>>>>>> your article is just "general words". :-) There is a couple of
>>>>>>> questions:
>>>>>>>
>>>>>>>    - can my "vision" be completed?
>>>>>>>    - how can it be implemented?
>>>>>>>
>>>>>>> The major problem as I see is to modify algorithm so Kamailio will
>>>>>>> not check
>>>>>>> database but will lean on answers of its upstream to generate
>>>>>>> UL. It should not BALANCE, just forward SIP traffic, ANALYZE
>>>>>>> answers of
>>>>>>> Upstream
>>>>>>> SIP-Server, make decision about attacks and PROXY RTP. It should be
>>>>>>> more
>>>>>>> clear
>>>>>>> definition what I would like to achieve.
>>>>>>>
>>>>>>> I could be confused about exact terminology of "Session Border
>>>>>>> Controller".
>>>>>>> But I'd like to implement FRAUD/BruteForce protection of my
>>>>>>> Asterisk using
>>>>>>> Kamailio (in the middle) because I heard it highly effective in the
>>>>>>> point
>>>>>>> of view of heavy loads. Asterisk might not bear a "tons" of SIP
>>>>>>> requests
>>>>>>> (dialogs).
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Kind regards,
>>>>>>> Ellad
>>>>>>>
>>>>>>>
>>>>>>> 22.10.2018 12:07, Alex Balashov пишет:
>>>>>>>> I hate to plug my own articles, but in this case it might help:
>>>>>>>>
>>>>>>>> http://www.evaristesys.com/blog/kamailio-as-an-sbc-five-years-on/
>>>>>>>>
>>>>>>>> -- 
>>>>>>>> Sent from mobile. Apologies for brevity and errors.
>>>>>>>>
>>>>>>>> -Original Message-
>>>>>>>> From: Ellad Yatsko 
>>>>>>>> To: sr-users@lists.kamailio.org
>>>>>>>> Sent: Mon, 22 Oct 2018 3:28 AM
>>>>>>>> Subject: [SR-Users] Kamailio as SBC
>>>>>>>>
>>>>>>>> Hello!
>>>>>>>>
>>>>>>>> I'd like to implement the following diagram:
>>>>>>>>
>>>>>>>>   Users  -> Internet -> Kamailio -> Asterisk
>>>>>>>>
>>>>

Re: [SR-Users] Kamailio as SBC

2018-10-25 Thread Ellad Yatsko

its OK to User and composes User Location
>>    - on receiving NOT FOUND, FORBIDDEN, etc Kamailio retransmits SIP
>> answer to User and after several unsuccessful attempts blocks User IP
>>    - Fail2Ban completes the rest - inserts new rule
>> Every time Kamailio retransmit SIP packet to the User from Asterisk it
>> HIDES topology (IP/UDP headers and all SIP-related Info from SIP
>> Packets). User should know just about Kamailio as about its counterpart.
>>
>> How to track SIP REGISTER related messages inside Kamailio?
>>
>> TO: Yu Boot - is it "standalone" implementation? How do you think? :-)
>>
>> Kind regards,
>> Ellad
>>
>>
>> 22.10.2018 20:16, Yu Boot пишет:
>>> I can help you with cfg, if you 're ready to implement standalone
>>> softswitch on your Kamailio :)
>>>
>>>
>>> 22.10.2018 17:21, Ellad Yatsko пишет:
>>>> May you help?.. :-)
>>>>
>>>> Kind regards,
>>>> Ellad
>>>>
>>>> 22.10.2018 17:12, Alex Balashov пишет:
>>>>> I did not say that my article represents a complete answer to every
>>>>> part
>>>>> of every one of your questions, at every level of abstraction and
>>>>> specificity. Just that it might be helpful. :-)
>>>>>
>>>>> On Mon, Oct 22, 2018 at 04:40:03PM +0300, Ellad Yatsko wrote:
>>>>>
>>>>>> Dear Alex,
>>>>>>
>>>>>> your article is just "general words". :-) There is a couple of
>>>>>> questions:
>>>>>>
>>>>>>    - can my "vision" be completed?
>>>>>>    - how can it be implemented?
>>>>>>
>>>>>> The major problem as I see is to modify algorithm so Kamailio will
>>>>>> not check
>>>>>> database but will lean on answers of its upstream to generate
>>>>>> UL. It should not BALANCE, just forward SIP traffic, ANALYZE
>>>>>> answers of
>>>>>> Upstream
>>>>>> SIP-Server, make decision about attacks and PROXY RTP. It should be
>>>>>> more
>>>>>> clear
>>>>>> definition what I would like to achieve.
>>>>>>
>>>>>> I could be confused about exact terminology of "Session Border
>>>>>> Controller".
>>>>>> But I'd like to implement FRAUD/BruteForce protection of my
>>>>>> Asterisk using
>>>>>> Kamailio (in the middle) because I heard it highly effective in the
>>>>>> point
>>>>>> of view of heavy loads. Asterisk might not bear a "tons" of SIP
>>>>>> requests
>>>>>> (dialogs).
>>>>>>
>>>>>>
>>>>>>
>>>>>> Kind regards,
>>>>>> Ellad
>>>>>>
>>>>>>
>>>>>> 22.10.2018 12:07, Alex Balashov пишет:
>>>>>>> I hate to plug my own articles, but in this case it might help:
>>>>>>>
>>>>>>> http://www.evaristesys.com/blog/kamailio-as-an-sbc-five-years-on/
>>>>>>>
>>>>>>> -- 
>>>>>>> Sent from mobile. Apologies for brevity and errors.
>>>>>>>
>>>>>>> -Original Message-
>>>>>>> From: Ellad Yatsko 
>>>>>>> To: sr-users@lists.kamailio.org
>>>>>>> Sent: Mon, 22 Oct 2018 3:28 AM
>>>>>>> Subject: [SR-Users] Kamailio as SBC
>>>>>>>
>>>>>>> Hello!
>>>>>>>
>>>>>>> I'd like to implement the following diagram:
>>>>>>>
>>>>>>>   Users  -> Internet -> Kamailio -> Asterisk
>>>>>>>
>>>>>>> 1. Kamailio has no own users, it just re-writes headers and re-send
>>>>>>> REGISTER messages to Asterisk where usres are located.
>>>>>>>
>>>>>>> 2. Depending on Astersisk's answers Kamailio either form UL (using
>>>>>>> original IP from the first, original REGISTER from Users) or
>>>>>>> translates
>>>>>>> Asterisk's answer back to Users. If it is error (e.g.
>>>>>>> forbidden/notfound) Kamailio blocks User's IP (for instance using
>>>>>>> pike
>&

Re: [SR-Users] Kamailio as SBC

2018-10-23 Thread David Villasmil

; >
> > 22.10.2018 20:16, Yu Boot пишет:
> > > I can help you with cfg, if you 're ready to implement standalone
> > > softswitch on your Kamailio :)
> > >
> > >
> > > 22.10.2018 17:21, Ellad Yatsko пишет:
> > >> May you help?.. :-)
> > >>
> > >> Kind regards,
> > >> Ellad
> > >>
> > >> 22.10.2018 17:12, Alex Balashov пишет:
> > >>> I did not say that my article represents a complete answer to every
> > >>> part
> > >>> of every one of your questions, at every level of abstraction and
> > >>> specificity. Just that it might be helpful. :-)
> > >>>
> > >>> On Mon, Oct 22, 2018 at 04:40:03PM +0300, Ellad Yatsko wrote:
> > >>>
> > >>>> Dear Alex,
> > >>>>
> > >>>> your article is just "general words". :-) There is a couple of
> > >>>> questions:
> > >>>>
> > >>>>- can my "vision" be completed?
> > >>>>- how can it be implemented?
> > >>>>
> > >>>> The major problem as I see is to modify algorithm so Kamailio will
> > >>>> not check
> > >>>> database but will lean on answers of its upstream to generate
> > >>>> UL. It should not BALANCE, just forward SIP traffic, ANALYZE
> > >>>> answers of
> > >>>> Upstream
> > >>>> SIP-Server, make decision about attacks and PROXY RTP. It should be
> > >>>> more
> > >>>> clear
> > >>>> definition what I would like to achieve.
> > >>>>
> > >>>> I could be confused about exact terminology of "Session Border
> > >>>> Controller".
> > >>>> But I'd like to implement FRAUD/BruteForce protection of my
> > >>>> Asterisk using
> > >>>> Kamailio (in the middle) because I heard it highly effective in the
> > >>>> point
> > >>>> of view of heavy loads. Asterisk might not bear a "tons" of SIP
> > >>>> requests
> > >>>> (dialogs).
> > >>>>
> > >>>>
> > >>>>
> > >>>> Kind regards,
> > >>>> Ellad
> > >>>>
> > >>>>
> > >>>> 22.10.2018 12:07, Alex Balashov пишет:
> > >>>>> I hate to plug my own articles, but in this case it might help:
> > >>>>>
> > >>>>> http://www.evaristesys.com/blog/kamailio-as-an-sbc-five-years-on/
> > >>>>>
> > >>>>> --
> > >>>>> Sent from mobile. Apologies for brevity and errors.
> > >>>>>
> > >>>>> -Original Message-
> > >>>>> From: Ellad Yatsko 
> > >>>>> To: sr-users@lists.kamailio.org
> > >>>>> Sent: Mon, 22 Oct 2018 3:28 AM
> > >>>>> Subject: [SR-Users] Kamailio as SBC
> > >>>>>
> > >>>>> Hello!
> > >>>>>
> > >>>>> I'd like to implement the following diagram:
> > >>>>>
> > >>>>>   Users  -> Internet -> Kamailio -> Asterisk
> > >>>>>
> > >>>>> 1. Kamailio has no own users, it just re-writes headers and re-send
> > >>>>> REGISTER messages to Asterisk where usres are located.
> > >>>>>
> > >>>>> 2. Depending on Astersisk's answers Kamailio either form UL (using
> > >>>>> original IP from the first, original REGISTER from Users) or
> > >>>>> translates
> > >>>>> Asterisk's answer back to Users. If it is error (e.g.
> > >>>>> forbidden/notfound) Kamailio blocks User's IP (for instance using
> > >>>>> pike
> > >>>>> module) and Fail2Ban adds affected IP into IPSet's List to block
> > >>>>> it by
> > >>>>> IPTables Permanently.
> > >>>>>
> > >>>>> 3. INVITEs are translated to Asterisk as to the only Upstream
> > >>>>> SIP-Server. And again Errors from Asterisk are processed in the
> > >>>>> same way
> > >>>>> as Bad REGISTERs. Pike in conjunction with IPSet/IPTables block
> > >>&g

Re: [SR-Users] Kamailio as SBC

2018-10-23 Thread Alex Balashov

; specificity. Just that it might be helpful. :-)
> >>>
> >>> On Mon, Oct 22, 2018 at 04:40:03PM +0300, Ellad Yatsko wrote:
> >>>
> >>>> Dear Alex,
> >>>>
> >>>> your article is just "general words". :-) There is a couple of
> >>>> questions:
> >>>>
> >>>>    - can my "vision" be completed?
> >>>>    - how can it be implemented?
> >>>>
> >>>> The major problem as I see is to modify algorithm so Kamailio will
> >>>> not check
> >>>> database but will lean on answers of its upstream to generate
> >>>> UL. It should not BALANCE, just forward SIP traffic, ANALYZE
> >>>> answers of
> >>>> Upstream
> >>>> SIP-Server, make decision about attacks and PROXY RTP. It should be
> >>>> more
> >>>> clear
> >>>> definition what I would like to achieve.
> >>>>
> >>>> I could be confused about exact terminology of "Session Border
> >>>> Controller".
> >>>> But I'd like to implement FRAUD/BruteForce protection of my
> >>>> Asterisk using
> >>>> Kamailio (in the middle) because I heard it highly effective in the
> >>>> point
> >>>> of view of heavy loads. Asterisk might not bear a "tons" of SIP
> >>>> requests
> >>>> (dialogs).
> >>>>
> >>>>
> >>>>
> >>>> Kind regards,
> >>>> Ellad
> >>>>
> >>>>
> >>>> 22.10.2018 12:07, Alex Balashov пишет:
> >>>>> I hate to plug my own articles, but in this case it might help:
> >>>>>
> >>>>> http://www.evaristesys.com/blog/kamailio-as-an-sbc-five-years-on/
> >>>>>
> >>>>> -- 
> >>>>> Sent from mobile. Apologies for brevity and errors.
> >>>>>
> >>>>> -Original Message-
> >>>>> From: Ellad Yatsko 
> >>>>> To: sr-users@lists.kamailio.org
> >>>>> Sent: Mon, 22 Oct 2018 3:28 AM
> >>>>> Subject: [SR-Users] Kamailio as SBC
> >>>>>
> >>>>> Hello!
> >>>>>
> >>>>> I'd like to implement the following diagram:
> >>>>>
> >>>>>   Users  -> Internet -> Kamailio -> Asterisk
> >>>>>
> >>>>> 1. Kamailio has no own users, it just re-writes headers and re-send
> >>>>> REGISTER messages to Asterisk where usres are located.
> >>>>>
> >>>>> 2. Depending on Astersisk's answers Kamailio either form UL (using
> >>>>> original IP from the first, original REGISTER from Users) or
> >>>>> translates
> >>>>> Asterisk's answer back to Users. If it is error (e.g.
> >>>>> forbidden/notfound) Kamailio blocks User's IP (for instance using
> >>>>> pike
> >>>>> module) and Fail2Ban adds affected IP into IPSet's List to block
> >>>>> it by
> >>>>> IPTables Permanently.
> >>>>>
> >>>>> 3. INVITEs are translated to Asterisk as to the only Upstream
> >>>>> SIP-Server. And again Errors from Asterisk are processed in the
> >>>>> same way
> >>>>> as Bad REGISTERs. Pike in conjunction with IPSet/IPTables block
> >>>>> affected
> >>>>> IPs.
> >>>>>
> >>>>> 4. Astersisk sees all registrations from Internet user as they are
> >>>>> directly behind Kamailio. Kamailio rewirtes headers twice: from
> >>>>> Users to
> >>>>> Asterisk and from Asterisk to Users - this allows to hide topology
> >>>>> from
> >>>>> users (they deal ONLY with Kamailio) and block non-static IPs on the
> >>>>> Asterisk's side.
> >>>>>
> >>>>> Is this possible?
> >>>>>
> >>>>> Kind regards,
> >>>>> Ellad Yatsko
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> ___
> >>>>> 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
> >>>>
> >>>> ___
> >>>> 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
> >
> >
> > ___
> > 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

-- 
Alex Balashov | Principal | Evariste Systems LLC

Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) 
Web: http://www.evaristesys.com/, http://www.csrpswitch.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 SBC

2018-10-23 Thread Ellad Yatsko

Ok. Let's divide overall task onto several little steps.

I. How to implement the following:
   - when Kamailio receives REGISTER from user in the Internet
   - Kamailio rewrites IP/UDP headers - it acts with Asterisk on behalf
of User, Asterisk should know just Kamailio IP (add "Via"?)
   - Kamailio remembers [somehow] this dialog (how?) and
   - retransmits REGISTER to Asterisk
   - on receiving Unauthorized Kamailio retransmits it to User - this is
an intermediate step, no action needed
   - User repeats steps on Registration with the Nonce
   - on receiving OK [from Asterisk] for the memorized dialog Kamailio
retransmits OK to User and composes User Location
   - on receiving NOT FOUND, FORBIDDEN, etc Kamailio retransmits SIP
answer to User and after several unsuccessful attempts blocks User IP
   - Fail2Ban completes the rest - inserts new rule
Every time Kamailio retransmit SIP packet to the User from Asterisk it
HIDES topology (IP/UDP headers and all SIP-related Info from SIP
Packets). User should know just about Kamailio as about its counterpart.

How to track SIP REGISTER related messages inside Kamailio?

TO: Yu Boot - is it "standalone" implementation? How do you think? :-)

Kind regards,
Ellad


22.10.2018 20:16, Yu Boot пишет:
> I can help you with cfg, if you 're ready to implement standalone
> softswitch on your Kamailio :)
>
>
> 22.10.2018 17:21, Ellad Yatsko пишет:
>> May you help?.. :-)
>>
>> Kind regards,
>> Ellad
>>
>> 22.10.2018 17:12, Alex Balashov пишет:
>>> I did not say that my article represents a complete answer to every
>>> part
>>> of every one of your questions, at every level of abstraction and
>>> specificity. Just that it might be helpful. :-)
>>>
>>> On Mon, Oct 22, 2018 at 04:40:03PM +0300, Ellad Yatsko wrote:
>>>
>>>> Dear Alex,
>>>>
>>>> your article is just "general words". :-) There is a couple of
>>>> questions:
>>>>
>>>>    - can my "vision" be completed?
>>>>    - how can it be implemented?
>>>>
>>>> The major problem as I see is to modify algorithm so Kamailio will
>>>> not check
>>>> database but will lean on answers of its upstream to generate
>>>> UL. It should not BALANCE, just forward SIP traffic, ANALYZE
>>>> answers of
>>>> Upstream
>>>> SIP-Server, make decision about attacks and PROXY RTP. It should be
>>>> more
>>>> clear
>>>> definition what I would like to achieve.
>>>>
>>>> I could be confused about exact terminology of "Session Border
>>>> Controller".
>>>> But I'd like to implement FRAUD/BruteForce protection of my
>>>> Asterisk using
>>>> Kamailio (in the middle) because I heard it highly effective in the
>>>> point
>>>> of view of heavy loads. Asterisk might not bear a "tons" of SIP
>>>> requests
>>>> (dialogs).
>>>>
>>>>
>>>>
>>>> Kind regards,
>>>> Ellad
>>>>
>>>>
>>>> 22.10.2018 12:07, Alex Balashov пишет:
>>>>> I hate to plug my own articles, but in this case it might help:
>>>>>
>>>>> http://www.evaristesys.com/blog/kamailio-as-an-sbc-five-years-on/
>>>>>
>>>>> -- 
>>>>> Sent from mobile. Apologies for brevity and errors.
>>>>>
>>>>> -Original Message-
>>>>> From: Ellad Yatsko 
>>>>> To: sr-users@lists.kamailio.org
>>>>> Sent: Mon, 22 Oct 2018 3:28 AM
>>>>> Subject: [SR-Users] Kamailio as SBC
>>>>>
>>>>> Hello!
>>>>>
>>>>> I'd like to implement the following diagram:
>>>>>
>>>>>   Users  -> Internet -> Kamailio -> Asterisk
>>>>>
>>>>> 1. Kamailio has no own users, it just re-writes headers and re-send
>>>>> REGISTER messages to Asterisk where usres are located.
>>>>>
>>>>> 2. Depending on Astersisk's answers Kamailio either form UL (using
>>>>> original IP from the first, original REGISTER from Users) or
>>>>> translates
>>>>> Asterisk's answer back to Users. If it is error (e.g.
>>>>> forbidden/notfound) Kamailio blocks User's IP (for instance using
>>>>> pike
>>>>> module) and Fail2Ban adds affected IP into IPSet's List to block
>>>>> it by
>>>>> IPTables Permanently.

Re: [SR-Users] Kamailio as SBC

2018-10-22 Thread Yu Boot

I can help you with cfg, if you 're ready to implement standalone 
softswitch on your Kamailio :)



22.10.2018 17:21, Ellad Yatsko пишет:

May you help?.. :-)

Kind regards,
Ellad

22.10.2018 17:12, Alex Balashov пишет:

I did not say that my article represents a complete answer to every part
of every one of your questions, at every level of abstraction and
specificity. Just that it might be helpful. :-)

On Mon, Oct 22, 2018 at 04:40:03PM +0300, Ellad Yatsko wrote:


Dear Alex,

your article is just "general words". :-) There is a couple of questions:

   - can my "vision" be completed?
   - how can it be implemented?

The major problem as I see is to modify algorithm so Kamailio will not check
database but will lean on answers of its upstream to generate
UL. It should not BALANCE, just forward SIP traffic, ANALYZE answers of
Upstream
SIP-Server, make decision about attacks and PROXY RTP. It should be more
clear
definition what I would like to achieve.

I could be confused about exact terminology of "Session Border Controller".
But I'd like to implement FRAUD/BruteForce protection of my Asterisk using
Kamailio (in the middle) because I heard it highly effective in the point
of view of heavy loads. Asterisk might not bear a "tons" of SIP requests
(dialogs).



Kind regards,
Ellad


22.10.2018 12:07, Alex Balashov пишет:

I hate to plug my own articles, but in this case it might help:

http://www.evaristesys.com/blog/kamailio-as-an-sbc-five-years-on/

--
Sent from mobile. Apologies for brevity and errors.

-Original Message-
From: Ellad Yatsko 
To: sr-users@lists.kamailio.org
Sent: Mon, 22 Oct 2018 3:28 AM
Subject: [SR-Users] Kamailio as SBC

Hello!

I'd like to implement the following diagram:

  Users  -> Internet -> Kamailio -> Asterisk

1. Kamailio has no own users, it just re-writes headers and re-send
REGISTER messages to Asterisk where usres are located.

2. Depending on Astersisk's answers Kamailio either form UL (using
original IP from the first, original REGISTER from Users) or translates
Asterisk's answer back to Users. If it is error (e.g.
forbidden/notfound) Kamailio blocks User's IP (for instance using pike
module) and Fail2Ban adds affected IP into IPSet's List to block it by
IPTables Permanently.

3. INVITEs are translated to Asterisk as to the only Upstream
SIP-Server. And again Errors from Asterisk are processed in the same way
as Bad REGISTERs. Pike in conjunction with IPSet/IPTables block affected
IPs.

4. Astersisk sees all registrations from Internet user as they are
directly behind Kamailio. Kamailio rewirtes headers twice: from Users to
Asterisk and from Asterisk to Users - this allows to hide topology from
users (they deal ONLY with Kamailio) and block non-static IPs on the
Asterisk's side.

Is this possible?

Kind regards,
Ellad Yatsko





___
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


___
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



___
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 SBC

2018-10-22 Thread John Petrini

You may want to look at the pipelimit module for rate limiting as well.

___
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 SBC

2018-10-22 Thread Fred Posner


On 10/22/18 10:21 AM, Ellad Yatsko wrote:

May you help?.. :-)

Kind regards,
Ellad



Not sure if you're looking for someone to do the work for you, in which 
case, I'd recommend the business list.


The concepts you're looking for here are covered in a variety of modules 
that you can integrate together to provide a solution to your needs:


HTABLE
DMQ
PERMISSIONS
UAC
PIKE

The beauty of this software is to look at the modules, understand the 
components, and then integrate it as you desire into a custom solution.


--fred

___
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 SBC

2018-10-22 Thread Ellad Yatsko

May you help?.. :-)

Kind regards,
Ellad

22.10.2018 17:12, Alex Balashov пишет:
> I did not say that my article represents a complete answer to every part
> of every one of your questions, at every level of abstraction and
> specificity. Just that it might be helpful. :-)
>
> On Mon, Oct 22, 2018 at 04:40:03PM +0300, Ellad Yatsko wrote:
>
>> Dear Alex,
>>
>> your article is just "general words". :-) There is a couple of questions:
>>
>>   - can my "vision" be completed?
>>   - how can it be implemented?
>>
>> The major problem as I see is to modify algorithm so Kamailio will not check
>> database but will lean on answers of its upstream to generate
>> UL. It should not BALANCE, just forward SIP traffic, ANALYZE answers of
>> Upstream
>> SIP-Server, make decision about attacks and PROXY RTP. It should be more
>> clear
>> definition what I would like to achieve.
>>
>> I could be confused about exact terminology of "Session Border Controller".
>> But I'd like to implement FRAUD/BruteForce protection of my Asterisk using
>> Kamailio (in the middle) because I heard it highly effective in the point
>> of view of heavy loads. Asterisk might not bear a "tons" of SIP requests
>> (dialogs).
>>
>>
>>
>> Kind regards,
>> Ellad
>>
>>
>> 22.10.2018 12:07, Alex Balashov пишет:
>>> I hate to plug my own articles, but in this case it might help:
>>>
>>> http://www.evaristesys.com/blog/kamailio-as-an-sbc-five-years-on/
>>>
>>> --
>>> Sent from mobile. Apologies for brevity and errors. 
>>>
>>> -Original Message-
>>> From: Ellad Yatsko 
>>> To: sr-users@lists.kamailio.org
>>> Sent: Mon, 22 Oct 2018 3:28 AM
>>> Subject: [SR-Users] Kamailio as SBC
>>>
>>> Hello!
>>>
>>> I'd like to implement the following diagram:
>>>
>>>  Users  -> Internet -> Kamailio -> Asterisk
>>>
>>> 1. Kamailio has no own users, it just re-writes headers and re-send
>>> REGISTER messages to Asterisk where usres are located.
>>>
>>> 2. Depending on Astersisk's answers Kamailio either form UL (using
>>> original IP from the first, original REGISTER from Users) or translates
>>> Asterisk's answer back to Users. If it is error (e.g.
>>> forbidden/notfound) Kamailio blocks User's IP (for instance using pike
>>> module) and Fail2Ban adds affected IP into IPSet's List to block it by
>>> IPTables Permanently.
>>>
>>> 3. INVITEs are translated to Asterisk as to the only Upstream
>>> SIP-Server. And again Errors from Asterisk are processed in the same way
>>> as Bad REGISTERs. Pike in conjunction with IPSet/IPTables block affected
>>> IPs.
>>>
>>> 4. Astersisk sees all registrations from Internet user as they are
>>> directly behind Kamailio. Kamailio rewirtes headers twice: from Users to
>>> Asterisk and from Asterisk to Users - this allows to hide topology from
>>> users (they deal ONLY with Kamailio) and block non-static IPs on the
>>> Asterisk's side.
>>>
>>> Is this possible?
>>>
>>> Kind regards,
>>> Ellad Yatsko
>>>
>>>
>>>
>>>
>>>
>>> ___
>>> 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
>>
>>
>> ___
>> 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 as SBC

2018-10-22 Thread Alex Balashov

I did not say that my article represents a complete answer to every part
of every one of your questions, at every level of abstraction and
specificity. Just that it might be helpful. :-)

On Mon, Oct 22, 2018 at 04:40:03PM +0300, Ellad Yatsko wrote:

> Dear Alex,
> 
> your article is just "general words". :-) There is a couple of questions:
> 
>   - can my "vision" be completed?
>   - how can it be implemented?
> 
> The major problem as I see is to modify algorithm so Kamailio will not check
> database but will lean on answers of its upstream to generate
> UL. It should not BALANCE, just forward SIP traffic, ANALYZE answers of
> Upstream
> SIP-Server, make decision about attacks and PROXY RTP. It should be more
> clear
> definition what I would like to achieve.
> 
> I could be confused about exact terminology of "Session Border Controller".
> But I'd like to implement FRAUD/BruteForce protection of my Asterisk using
> Kamailio (in the middle) because I heard it highly effective in the point
> of view of heavy loads. Asterisk might not bear a "tons" of SIP requests
> (dialogs).
> 
> 
> 
> Kind regards,
> Ellad
> 
> 
> 22.10.2018 12:07, Alex Balashov пишет:
> > I hate to plug my own articles, but in this case it might help:
> >
> > http://www.evaristesys.com/blog/kamailio-as-an-sbc-five-years-on/
> >
> > --
> > Sent from mobile. Apologies for brevity and errors. 
> >
> > -Original Message-
> > From: Ellad Yatsko 
> > To: sr-users@lists.kamailio.org
> > Sent: Mon, 22 Oct 2018 3:28 AM
> > Subject: [SR-Users] Kamailio as SBC
> >
> > Hello!
> >
> > I'd like to implement the following diagram:
> >
> >  Users  -> Internet -> Kamailio -> Asterisk
> >
> > 1. Kamailio has no own users, it just re-writes headers and re-send
> > REGISTER messages to Asterisk where usres are located.
> >
> > 2. Depending on Astersisk's answers Kamailio either form UL (using
> > original IP from the first, original REGISTER from Users) or translates
> > Asterisk's answer back to Users. If it is error (e.g.
> > forbidden/notfound) Kamailio blocks User's IP (for instance using pike
> > module) and Fail2Ban adds affected IP into IPSet's List to block it by
> > IPTables Permanently.
> >
> > 3. INVITEs are translated to Asterisk as to the only Upstream
> > SIP-Server. And again Errors from Asterisk are processed in the same way
> > as Bad REGISTERs. Pike in conjunction with IPSet/IPTables block affected
> > IPs.
> >
> > 4. Astersisk sees all registrations from Internet user as they are
> > directly behind Kamailio. Kamailio rewirtes headers twice: from Users to
> > Asterisk and from Asterisk to Users - this allows to hide topology from
> > users (they deal ONLY with Kamailio) and block non-static IPs on the
> > Asterisk's side.
> >
> > Is this possible?
> >
> > Kind regards,
> > Ellad Yatsko
> >
> >
> >
> >
> >
> > ___
> > 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
> 
> 
> 
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Alex Balashov | Principal | Evariste Systems LLC

Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) 
Web: http://www.evaristesys.com/, http://www.csrpswitch.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 SBC

2018-10-22 Thread Ellad Yatsko

Dear Alex,

your article is just "general words". :-) There is a couple of questions:

  - can my "vision" be completed?
  - how can it be implemented?

The major problem as I see is to modify algorithm so Kamailio will not check
database but will lean on answers of its upstream to generate
UL. It should not BALANCE, just forward SIP traffic, ANALYZE answers of
Upstream
SIP-Server, make decision about attacks and PROXY RTP. It should be more
clear
definition what I would like to achieve.

I could be confused about exact terminology of "Session Border Controller".
But I'd like to implement FRAUD/BruteForce protection of my Asterisk using
Kamailio (in the middle) because I heard it highly effective in the point
of view of heavy loads. Asterisk might not bear a "tons" of SIP requests
(dialogs).



Kind regards,
Ellad


22.10.2018 12:07, Alex Balashov пишет:
> I hate to plug my own articles, but in this case it might help:
>
> http://www.evaristesys.com/blog/kamailio-as-an-sbc-five-years-on/
>
> --
> Sent from mobile. Apologies for brevity and errors. 
>
> -Original Message-
> From: Ellad Yatsko 
> To: sr-users@lists.kamailio.org
> Sent: Mon, 22 Oct 2018 3:28 AM
> Subject: [SR-Users] Kamailio as SBC
>
> Hello!
>
> I'd like to implement the following diagram:
>
>  Users  -> Internet -> Kamailio -> Asterisk
>
> 1. Kamailio has no own users, it just re-writes headers and re-send
> REGISTER messages to Asterisk where usres are located.
>
> 2. Depending on Astersisk's answers Kamailio either form UL (using
> original IP from the first, original REGISTER from Users) or translates
> Asterisk's answer back to Users. If it is error (e.g.
> forbidden/notfound) Kamailio blocks User's IP (for instance using pike
> module) and Fail2Ban adds affected IP into IPSet's List to block it by
> IPTables Permanently.
>
> 3. INVITEs are translated to Asterisk as to the only Upstream
> SIP-Server. And again Errors from Asterisk are processed in the same way
> as Bad REGISTERs. Pike in conjunction with IPSet/IPTables block affected
> IPs.
>
> 4. Astersisk sees all registrations from Internet user as they are
> directly behind Kamailio. Kamailio rewirtes headers twice: from Users to
> Asterisk and from Asterisk to Users - this allows to hide topology from
> users (they deal ONLY with Kamailio) and block non-static IPs on the
> Asterisk's side.
>
> Is this possible?
>
> Kind regards,
> Ellad Yatsko
>
>
>
>
>
> ___
> 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



___
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 SBC

2018-10-22 Thread Alex Balashov

I hate to plug my own articles, but in this case it might help:

http://www.evaristesys.com/blog/kamailio-as-an-sbc-five-years-on/

--
Sent from mobile. Apologies for brevity and errors. 

-Original Message-
From: Ellad Yatsko 
To: sr-users@lists.kamailio.org
Sent: Mon, 22 Oct 2018 3:28 AM
Subject: [SR-Users] Kamailio as SBC

Hello!

I'd like to implement the following diagram:

 Users  -> Internet -> Kamailio -> Asterisk

1. Kamailio has no own users, it just re-writes headers and re-send
REGISTER messages to Asterisk where usres are located.

2. Depending on Astersisk's answers Kamailio either form UL (using
original IP from the first, original REGISTER from Users) or translates
Asterisk's answer back to Users. If it is error (e.g.
forbidden/notfound) Kamailio blocks User's IP (for instance using pike
module) and Fail2Ban adds affected IP into IPSet's List to block it by
IPTables Permanently.

3. INVITEs are translated to Asterisk as to the only Upstream
SIP-Server. And again Errors from Asterisk are processed in the same way
as Bad REGISTERs. Pike in conjunction with IPSet/IPTables block affected
IPs.

4. Astersisk sees all registrations from Internet user as they are
directly behind Kamailio. Kamailio rewirtes headers twice: from Users to
Asterisk and from Asterisk to Users - this allows to hide topology from
users (they deal ONLY with Kamailio) and block non-static IPs on the
Asterisk's side.

Is this possible?

Kind regards,
Ellad Yatsko

___
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

[SR-Users] Kamailio as SBC

2018-10-22 Thread Ellad Yatsko

Hello!

I'd like to implement the following diagram:

 Users  -> Internet -> Kamailio -> Asterisk

1. Kamailio has no own users, it just re-writes headers and re-send
REGISTER messages to Asterisk where usres are located.

2. Depending on Astersisk's answers Kamailio either form UL (using
original IP from the first, original REGISTER from Users) or translates
Asterisk's answer back to Users. If it is error (e.g.
forbidden/notfound) Kamailio blocks User's IP (for instance using pike
module) and Fail2Ban adds affected IP into IPSet's List to block it by
IPTables Permanently.

3. INVITEs are translated to Asterisk as to the only Upstream
SIP-Server. And again Errors from Asterisk are processed in the same way
as Bad REGISTERs. Pike in conjunction with IPSet/IPTables block affected
IPs.

4. Astersisk sees all registrations from Internet user as they are
directly behind Kamailio. Kamailio rewirtes headers twice: from Users to
Asterisk and from Asterisk to Users - this allows to hide topology from
users (they deal ONLY with Kamailio) and block non-static IPs on the
Asterisk's side.

Is this possible?

Kind regards,
Ellad Yatsko





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

50 matches

Mail list logo