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
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
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]:
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
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
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
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
Probably. You can get full pcap files using tcpdump and check TLS
handshakes usign wireshark.
Also it is not really need to check cert on the side of kamailio. You can
set (at least for tests)
verify_certificate = no
require_certificate = no
On Fri, 17 Apr 2020 at 10:02, sip user wrote:
> Hi
Suggest reading Fred's article about configuring Kamailio with Letsencrypt
https://www.fredposner.com/1836/kamailio-tls-and-letsencrypt/
On Fri, Apr 17, 2020 at 3:00 AM sip user wrote:
> Hi Sergiu..
>
> I've made many test and many change...
>
> In tls.cfg I have this:
>
> [server:default]
>
Hi Sergiu..
I've made many test and many change...
In tls.cfg I have this:
[server:default]
method = TLSv1.2
verify_certificate = yes
require_certificate = yes
private_key = /etc/letsencrypt/ssl/cert.key
certificate = /etc/letsencrypt/ssl/cert.crt
ca_list = /etc/letsencrypt/ssl/ca.crt
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
Hi SIP User/anonymous/one-time-visitor/,
Your TLS config isn't correct. The article clearly says
verify/require_certificate must be set to 'yes'
*kamcmd tls.list*
Does it show any 'established' connections with MS proxy?
Good luck,
--Sergiu
On Thu, Apr 16, 2020 at 11:41 AM Ovidiu Sas wrote:
The tutorial is pretty clear:
You need to add the Contact header only for OPTIONS pings.
You need to use the proper Record-Route headers based on the direction
of the call.
There's no out of the box solution because each setup is different.
If you understand how loose routing works in SIP, then
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:
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
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
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
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
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
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,
>
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
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,
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:
>
23 matches
Mail list logo
