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

2020-04-16 Thread Sergiu Pojoga 
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 you know how to
> adjust the config to use record_route_preset(), just as explained in
> the tutorial. There is also an example of an INVITE that has the right
> Record-Route headers in the tutorial.
>
> You can choose to use the FQDN for the Record-Route header facing MS
> and the IP for the Record-Route header facing the carrier or use the
> FQDN for both Record-Route headers (just like in the tutorialexample).
> Alternatively, one can try to advertise the FQDN in the listen
> directive in the config and then the Record-Route headers should be
> populated automatically.
>
> Regards,
> Ovidiu Sas
>
> On Thu, Apr 16, 2020 at 10:50 AM sip user  wrote:
> >
> > 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

Re: [SR-Users] Announcing SaraPhone, SIP WebRTC Open Source business phone

2020-04-16 Thread Giovanni Maruzzelli 
On Thu, Apr 16, 2020 at 5:52 PM Daniel-Constantin Mierla 
wrote:

> Thanks for sharing!
>
> Does it support video as well, I see only voice being mentioned.
>
> Ciao Daniel!

Nope, it does not support video, only voice.

I have a separate project for videocalls, videoconferences, chat,
collaboration, etc, very full featured too, I hope to publish it in
September!

Have a nice day,
-giovanni


> Cheers,
> Daniel
> On 16.04.20 17:38, Giovanni Maruzzelli wrote:
>
> My fellow VoIPers,
>
> I am pleased to announce the early availability of:
>
> SaraPhone
> --
>
> SaraPhone is a bare bone SIP WebRTC voice phone, complete with most
> features real companies want to use in real world: HotDesking, Redial,
> BLFs, MWI, DND, PhoneBook, Hold, Transfer, Mute, Attended Transfer,
> Notifications, running on all Browsers both on Desktop and SmartPhone.
>
> SaraPhone is fully integrated with FusionPBX, the full-featured domain
> based multi-tenant PBX and voice switch for FreeSwitch.
>
> Based on SIP.js, SaraPhone works with all WebRTC compliant SIP proxies,
> gateways, and servers (Asterisk, Kamailio, OpenSIPS, etc).
>
> Initial author is Giovanni Maruzzelli, and SaraPhone gets its name from
> Giovanni's wife, Sara Hosseini.
>
> In addition to providing all of the usual DeskPhone functionality,
> SaraPhone got:
>
>- Desktop Notification for Incoming Calls
>- Live MWI update
>- Real Time BLFs status update
>- BLF click to call
>- Caller Name and Number Display
>- Call Error Cause Display
>- AutoAnswer
>- Network Disconnect Reload
>- Show and Set Caller-ID (incoming-outbound)
>
>
> You an find it in GitHub ( https://github.com/gmaruzz/saraphone ).
>
> Anyone interested can play with it :).
>
> Have fun,
> giovanni
>
>
> --
> Sincerely,
>
> Giovanni Maruzzelli
> OpenTelecom.IT
> cell: +39 347 266 56 18
>
>
> ___
> Kamailio (SER) - Users Mailing 
> Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
> --
> Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- 
> www.linkedin.com/in/miconda
>
>

-- 
Sincerely,

Giovanni Maruzzelli
OpenTelecom.IT
cell: +39 347 266 56 18
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Announcing SaraPhone, SIP WebRTC Open Source business phone

2020-04-16 Thread Daniel-Constantin Mierla 
Thanks for sharing!

Does it support video as well, I see only voice being mentioned.

Cheers,
Daniel

On 16.04.20 17:38, Giovanni Maruzzelli wrote:
> My fellow VoIPers,
>
> I am pleased to announce the early availability of:
>
> SaraPhone
> --
>
> SaraPhone is a bare bone SIP WebRTC voice phone, complete with most
> features real companies want to use in real world: HotDesking, Redial,
> BLFs, MWI, DND, PhoneBook, Hold, Transfer, Mute, Attended Transfer,
> Notifications, running on all Browsers both on Desktop and SmartPhone.
>
> SaraPhone is fully integrated with FusionPBX, the full-featured domain
> based multi-tenant PBX and voice switch for FreeSwitch.
>
> Based on SIP.js, SaraPhone works with all WebRTC compliant SIP
> proxies, gateways, and servers (Asterisk, Kamailio, OpenSIPS, etc).
>
> Initial author is Giovanni Maruzzelli, and SaraPhone gets its name
> from Giovanni's wife, Sara Hosseini.
>
> In addition to providing all of the usual DeskPhone functionality,
> SaraPhone got:
>
>   * Desktop Notification for Incoming Calls
>   * Live MWI update
>   * Real Time BLFs status update
>   * BLF click to call
>   * Caller Name and Number Display
>   * Call Error Cause Display
>   * AutoAnswer
>   * Network Disconnect Reload
>   * Show and Set Caller-ID (incoming-outbound)
>
>
> You an find it in GitHub ( https://github.com/gmaruzz/saraphone ).
>
> Anyone interested can play with it :).
>
> Have fun,
> giovanni
>
>
> -- 
> Sincerely,
>
> Giovanni Maruzzelli
> OpenTelecom.IT
> cell: +39 347 266 56 18
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

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

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

[SR-Users] Announcing SaraPhone, SIP WebRTC Open Source business phone

2020-04-16 Thread Giovanni Maruzzelli 
My fellow VoIPers,

I am pleased to announce the early availability of:

SaraPhone
--

SaraPhone is a bare bone SIP WebRTC voice phone, complete with most
features real companies want to use in real world: HotDesking, Redial,
BLFs, MWI, DND, PhoneBook, Hold, Transfer, Mute, Attended Transfer,
Notifications, running on all Browsers both on Desktop and SmartPhone.

SaraPhone is fully integrated with FusionPBX, the full-featured domain
based multi-tenant PBX and voice switch for FreeSwitch.

Based on SIP.js, SaraPhone works with all WebRTC compliant SIP proxies,
gateways, and servers (Asterisk, Kamailip, OpenSIPS, etc).

Initial author is Giovanni Maruzzelli, and SaraPhone gets its name from
Giovanni's wife, Sara Hosseini.

In addition to providing all of the usual DeskPhone functionality,
SaraPhone got:

   - Desktop Notification for Incoming Calls
   - Live MWI update
   - Real Time BLFs status update
   - BLF click to call
   - Caller Name and Number Display
   - Call Error Cause Display
   - AutoAnswer
   - Network Disconnect Reload
   - Show and Set Caller-ID (incoming-outbound)


You an find it in GitHub ( https://github.com/gmaruzz/saraphone ).

Anyone interested can play with it :).

Have fun,
giovanni


-- 
Sincerely,

Giovanni Maruzzelli
OpenTelecom.IT
cell: +39 347 266 56 18
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

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

2020-04-16 Thread Ovidiu Sas 
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 you know how to
adjust the config to use record_route_preset(), just as explained in
the tutorial. There is also an example of an INVITE that has the right
Record-Route headers in the tutorial.

You can choose to use the FQDN for the Record-Route header facing MS
and the IP for the Record-Route header facing the carrier or use the
FQDN for both Record-Route headers (just like in the tutorialexample).
Alternatively, one can try to advertise the FQDN in the listen
directive in the config and then the Record-Route headers should be
populated automatically.

Regards,
Ovidiu Sas

On Thu, Apr 16, 2020 at 10:50 AM sip user  wrote:
>
> 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 
>> 
>> Отправлено: 16 апреля 2020

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

2020-04-16 Thread sip user 
Hi Nasida.. Thanks for answerd to me...

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

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

I don't see any different.

I know that the module is loaded because I see:

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

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

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

Any more thing that i can test or do??

Thanks

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

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

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

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



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

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

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

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

1.- In syslog:

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

2.- With TCPDUMP:

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

Re: [SR-Users] kamailio integration with MS teams.

2020-04-16 Thread Nasida Yuriy 

Thanks for the answer Sergiu, Ovidiu

I don't know your setup but I use kamailio as load balancer with FS nodes 
(instead of kamailio's media proxy).
That is why I have FS node IP in the contact header of 200 OK message which go 
to MS teams (it's outbound call from MS to kam).
Like we all know MS doesn't like IP address at all (in contact and 
record-route). Thus I have to replace (at kamailio) FS node IP to fqdn of trunk 
I use with MS.
Also I had to comment record_route() for invites from MS.
You mentioned that I should not change contact header but... really MS ignore 
my 200 OK for all other cases.
Also you mentioned that you have record route header in 200 OK, but again - MS 
do not ignore 200 OK only in case I have only one record route header which was 
in initial INVITE from MS.
You said it is working for you. Not sure why really. May be you use kamalio 
rtpproxy and that is why have correct contact at once.
As for record route header - I have no ideas why MS doesn't ignore several 
record route headter in 200 OK for your case.

With my changes i got ACK from MS. And also got voice call but obviously it is 
dopped in ~30 sec because kamialio do not know destination for ACK from MS (it 
has kamailio FQDN in URI)

Normally with my setup, 200 OK keeps ip address of FS node and MS should send 
ACK to kamilio IP but with FS IP address in URI. We all know that MS do not 
respect RFC and can not do so. They just said in docs  (we do not support sip 
proxy).

So... Now I should to think how re-direct such ACK to FS node. Should be 
possible to all this begin to be more and more complicated.

Any advice are welcome!


От: sr-users  от имени Sergiu Pojoga 

Отправлено: 15 апреля 2020 г. 5:36
Кому: Kamailio (SER) - Users Mailing List 
Тема: Re: [SR-Users] kamailio integration with MS teams.

Also, you might want to check out this discussion from just a few days ago with 
a fellow comrade about a similar MS Teams problem:

https://lists.kamailio.org/pipermail/sr-users/2020-April/108868.html

On Tue, Apr 14, 2020 at 4:23 PM Sergiu Pojoga 
mailto:pojo...@gmail.com>> wrote:
Well... most likely you didn't fix it, at least not properly. There's no such 
requirement to have a single RR in the 200 OK, especially only the one from the 
sender's original invite.
By this logic, Kamailio can't insert it's own RR to keep itself in the call's 
path. I can assure you that's not the case in reality.

On Tue, Apr 14, 2020 at 3:12 PM Nasida Yuriy 
mailto:nas...@live.ru>> wrote:
Yes, sure, need to fix Record-Route. The question was how exactly :)
Well.  I just fixed it by the way. 200 OK had to have only one record-route 
(which MS sent in initial invite). Otherwise MS ignore it without any response.




От: sr-users 
mailto:sr-users-boun...@lists.kamailio.org>>
 от имени Ovidiu Sas mailto:o...@voipembedded.com>>
Отправлено: 14 апреля 2020 г. 20:32
Кому: Kamailio (SER) - Users Mailing List 
mailto:sr-users@lists.kamailio.org>>
Тема: Re: [SR-Users] kamailio integration with MS teams.

The instructions are pretty clear in the sense that you need to fix
the Record-Route header.
You don't need to touch the Contact header for in-dialog requests/replies.

Regards,
Ovidiu Sas


On Tue, Apr 14, 2020 at 12:19 PM Nasida Yuriy 
mailto:nas...@live.ru>> wrote:
>
> Hi guys,
>
>
> Do you have some expirience with kamailio integration with MS teams ?
>
>
> I follow the instructon from here
> https://skalatan.de/en/blog/kamailio-sbc-teams
>
> TLS part is configured correctly. I also got OPTIONS pings working between MS 
> teams and kamailio by following of  this instruction. That is very good.
>
>  But... There is issues with outbound calls from MS teams to kamailo.
>
>
> MS side send INVITE, kamailio responds with 180 and 200 OK, but looks like MS 
> ignores us. I know that I probably should use record_route_preset function 
> here to modify Record-Route headers to satisfy MS wishes.
>
> But nothing helps. I also tried to modify contact header in 200 OK like it 
> was done for OPTIONS - no luck.
>
> Anyone has a working example of kamailio files for MS team ?
> Or at least sucessful pcap with them.
>
> I can be wrong but looks like MS doesn't respect RFC at all.
>
>
> Thanks.
>
>
>
>
> Regards,
> Team lead
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users



--
VoIP Embedded, Inc.
http://www.voipembedded.com

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

[SR-Users] Kamailio like SBC with Teams

2020-04-16 Thread sip user 
Hello good morning ... I am new to this list and I was starting to mess
with Kamailio, mainly to set it up as SBC against Teams, in this case.

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

1.- In syslog:

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

2.- With TCPDUMP:

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

Re: [SR-Users] TCP/TLS connection (id: 0) for WebSocket could not be found

2020-04-16 Thread Daniel-Constantin Mierla 
Hello,

did you print the log message just before t_relay()?

Can you also print the tcp and tls connections via rpc? I am not sure if
the websocket keeps a separate list of connections, but tcp/tls should
have the lists used for routing.

It would be better to upgrade to 5.3, because 5.1 is out of maintenance
and if there is still an issue, it is easier to troubleshoot and fix.
Then you can backport locally to 5.1, if you have to run that version on
specific systems.

Cheers,
Daniel

On 16.04.20 05:10, Mack Hendricks wrote:
> Hey Daniel,
>
> It returns:
>
>  [LOCATION] ru: sips:2000@df7jal23ls0d.invalid
> ;rtcweb-breaker=no;transport=wss,
> *nh(u): sip:98.209.240.245:50453;transport=ws*
> *
> *
> This matches the output from
>
> kamcmd ws.dump
>
>
> connections: {
> 29: wss:*98.209.240.245:50453* -> wss:134.122.27.49:4443 (state: OPEN,
>  last used 22s ago, sub-protocol: sip)
> }
> info: {
> wscounter: 1
> truncated: no
> }
> }
>
> I can grade to 5.3 if you think that’s best.
>
>
> *
> *
>
>> On Apr 15, 2020, at 12:11 PM, Daniel-Constantin Mierla
>> mailto:mico...@gmail.com>> wrote:
>>
>> Hello,
>>
>> when id is 0, then the search of the connection is done by target
>> address. For some reason, the destination is not matching the
>> connection. Try to print $nh(u) before relaying to see where it is
>> supposed to be sent.
>>
>> Cheers,
>> Daniel
>>
>> On 15.04.20 16:54, Mack Hendricks wrote:
>>> Hello,
>>>
>>> I’m running kamailio 5.1.10 (x86_64/linux)
>>>
>>> The connection_id in usrloc is -1 for some reason so the id doesn’t
>>> match for sure.  But, I thought that it would match on the received
>>> address of the WS client because the output from ws.dump shows that
>>> the connection address and port matches the received address and
>>> port in usrloc.
>>>
>>> Any suggestions?
>>>
>>>
>>>
>>>
 On Apr 15, 2020, at 10:48 AM, Daniel-Constantin Mierla
 mailto:mico...@gmail.com>> wrote:

 Hello,

 what version of Kamailio do you use?

 That message is printed when the connection is not found by id or
 by destination address.

 Cheers,
 Daniel

 On 15.04.20 07:11, Mack Hendricks wrote:
> Hey All,
>
>
>
> I get this message when trying to route request to a WebSocket client:
>
>
> Apr 15 04:59:37 dSIP060entNightly-0 /usr/sbin/kamailio[22071]:
> DEBUG:  [core/msg_translator.c:1762]: check_boundaries(): no
> multi-part body
> Apr 15 04:59:37 dSIP060entNightly-0 /usr/sbin/kamailio[22071]:
> DEBUG:  [core/msg_translator.c:429]: clen_builder():
> content-length: 651 (651)
> Apr 15 04:59:37 dSIP060entNightly-0 /usr/sbin/kamailio[22071]:
> WARNING:  [core/msg_translator.c:2786]: via_builder():
> *TCP/TLS connection (id: 0) for WebSocket could not be found*
> Apr 15 04:59:37 dSIP060entNightly-0 /usr/sbin/kamailio[22071]:
> ERROR:  [core/msg_translator.c:2002]:
> build_req_buf_from_sip_req(): could not create Via header
> Apr 15 04:59:37 dSIP060entNightly-0 /usr/sbin/kamailio[22071]:
> ERROR: tm [t_fwd.c:476]: prepare_new_uac(): could not build request
> Apr 15 04:59:37 dSIP060entNightly-0 /usr/sbin/kamailio[22071]:
> ERROR: tm [t_fwd.c:1738]: t_forward_nonack(): failure to add branches
> Apr 15 04:59:37 dSIP060entNightly-0 /usr/sbin/kamailio[22071]:
> DEBUG: tm [t_funcs.c:337]: t_relay_to(): t_forward_nonack returned
> error -2 (-2)
> Apr 15 04:59:37 dSIP060entNightly-0 /usr/sbin/kamailio[22071]:
> DEBUG: tm [t_funcs.c:355]: t_relay_to(): -2 error reply generation
> delayed
> Apr 15 04:59:37 dSIP060entNightly-0 /usr/sbin/kamailio[22071]:
> exec: *** cfgtrace:request_route=[RELAY]
> c=[/etc/kamailio/kamailio.cfg] l=1176 a=24 n=sl_reply_error
> Apr 15 04:59:37 dSIP060entNightly-0 /usr/sbin/kamailio[22071]:
> ERROR: sl [sl_funcs.c:362]: sl_reply_error(): stateless error
> reply used: No error (2/SL)
> Apr 15 04:59:37 dSIP060entNightly-0 /usr/sbin/kamailio[22071]:
> exec: *** cfgtrace:request_route=[RELAY]
> c=[/etc/kamailio/kamailio.cfg] l=1178 a=2 n=exit
>
>
>
> Here is what my location table looks like.  It should try to send
> the call to * sip:98.209.240.245:56291;transport=ws*
>
>
> *** 2. row ***
>            id: 124
>          ruid: uloc-5e9685e8-5650-92
>      username: 2000
>        domain: ws-test.com 
>      *contact: sips:2000@df7jal23ls0d.invalid
> ;rtcweb-breaker=no;transport=wss
>      received: sip:98.209.240.245:56291;transport=ws*
>          path: NULL
>       expires: 2020-04-15 05:03:17
>             q: -1.00
>        callid: 7ef0a550-b2b9-24c6-5c3b-8e0c667f5533
>          cseq: 50096
> last_modified: 2020-04-15 04:59:57
>         flags: 0
>        cflags: 524352
>