Re: [SR-Users] Kamailio like SBC with Teams
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
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
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
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
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
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
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
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
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
_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
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
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
; 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
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
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
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
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
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
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
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
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
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
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
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
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
