[SIP Beyond VoIP] Sylkserver Setup without a SIP proxy

Valentin Kleibel valentin at vrvis.at
Thu Mar 26 13:20:39 CET 2020


Hi,

thanks for your suggestions.
We still get disonnects every minute.
The conference feature is anabled, but I'm not sure if it is configured 
correctly... Is there a way to enable a trace log for the conference 
application?

going through some logs i found some errors i don't really understand...

main log:

Mar 26 10:16:07 XX sylk-server[7786]: ERROR    [webrtcgateway] 
[videoroom berylspiderarrow5 at videoconference.XX.at] chatroom session for 
4fb16b9eff5c4b17 at guest.XX.at failed: user request

/var/log/sylkserver/notification_trace.log:

2020-03-26 11:46:54.136407 Notification name=SIPInvitationChangedState 
sender=<sipsimple.core._core.Invitation object at 0x7f791e63d590> 
data=NotificationData(originator='local', body=None, code=403, 
disconnect_reason='Forbidden', state='disconnected', headers={'Via': 
[FrozenViaHeader('UDP', '<PUBLIC_IP>', 5060, frozendict({'received': 
'PUBLIC_IP', 'rport': 5060, 'branch': 
'z9hG4bKPj7ee59365-a339-4296-a219-d2b99d2af582'}))], 'From': 
FrozenFromHeader(FrozenSIPURI('guest.XX.at', 'a8e2666a7a1f4ea8', None, 
None, False, frozendict({}), frozendict({})), u'vali', 
frozendict({'tag': 'd671f511-df74-4409-b0e5-77f73acb5653'})), 'Server': 
FrozenHeader('Server', 'SylkServer-5.5.0'), 'To': 
FrozenToHeader(FrozenSIPURI('conference.XX.at', 'patternracerweed5', 
None, None, False, frozendict({}), frozendict({})), None, 
frozendict({'tag': 'e51628fa-4a37-4dda-b91c-50e6ac1c315e'})), 'CSeq': 
(31, 'INVITE'), 'Call-ID': FrozenHeader('Call-ID', 
'baddf641-c998-484b-acdc-734d50b0e91f')}, reason='Forbidden', 
prev_state='disconnecting')

/var/log/sylkserver/core_trace.log:

2020-03-26 11:46:54.100 tsx0x7f7920320 ..Sending Request msg 
INVITE/cseq=31 (tdta0x7f7
92031e740) in state Null
2020-03-26 11:46:54.100  sip_resolve.c ...Target '<PUBLIC_IP>:0' 
type=Unspecified resol
ved to '<PUBLIC_IP>:5060' type=UDP (UDP transport)
2020-03-26 11:46:54.100 tsx0x7f7920320 ...State changed from Null to 
Calling, event=TX
_MSG
2020-03-26 11:46:54.100 dlg0x7f792031d ....Transaction tsx0x7f79203207a8 
state changed to Calling
2020-03-26 11:46:54.100 sip_endpoint.c Processing incoming message: 
Request msg INVITE/cseq=31 (rdata0x7f7924137388)
2020-03-26 11:46:54.101 tsx0x7f792417a ..Transaction created for Request 
msg INVITE/cseq=31 (rdata0x7f7924137388)
2020-03-26 11:46:54.101 tsx0x7f792417a .Incoming Request msg 
INVITE/cseq=31 (rdata0x7f7924137388) in state Null
2020-03-26 11:46:54.101 tsx0x7f792417a ..State changed from Null to 
Trying, event=RX_MSG
2020-03-26 11:46:54.101 dlg0x7f792417a ...Transaction tsx0x7f792417ae78 
state changed to Trying
2020-03-26 11:46:54.101 dlg0x7f792417a .UAS dialog created
2020-03-26 11:46:54.101 dlg0x7f792417a .Module mod-invite added as 
dialog usage, data=0x7f79241892a8
2020-03-26 11:46:54.101 dlg0x7f792417a ..Session count inc to 3 by 
mod-invite
2020-03-26 11:46:54.101 inv0x7f792417a .UAS invite session created for 
dialog dlg0x7f792417a668
2020-03-26 11:46:54.101       endpoint ..Response msg 100/INVITE/cseq=31 
(tdta0x7f7924189f20) created
2020-03-26 11:46:54.101 dlg0x7f792417a ..Initial answer Response msg 
100/INVITE/cseq=31 (tdta0x7f7924189f20)
2020-03-26 11:46:54.115 inv0x7f792417a .Sending Response msg 
100/INVITE/cseq=31 (tdta0x7f7924189f20)
2020-03-26 11:46:54.115 dlg0x7f792417a ..Sending Response msg 
100/INVITE/cseq=31 (tdta0x7f7924189f20)
2020-03-26 11:46:54.115 tsx0x7f792417a ..Sending Response msg 
100/INVITE/cseq=31 (tdta0x7f7924189f20) in state Trying
2020-03-26 11:46:54.115 tsx0x7f792417a ...State changed from Trying to 
Proceeding, event=TX_MSG
2020-03-26 11:46:54.115 dlg0x7f792417a ....Transaction tsx0x7f792417ae78 
state changed to Proceeding
2020-03-26 11:46:54.116 inv0x7f792417a .Sending Response msg 
403/INVITE/cseq=31 (tdta0x7f7924189f20)
2020-03-26 11:46:54.116 dlg0x7f792417a ..Sending Response msg 
403/INVITE/cseq=31 (tdta0x7f7924189f20)
2020-03-26 11:46:54.116 tsx0x7f792417a ..Sending Response msg 
403/INVITE/cseq=31 (tdta0x7f7924189f20) in state Proceeding
2020-03-26 11:46:54.116 tsx0x7f792417a ...State changed from Proceeding 
to Completed, event=TX_MSG
2020-03-26 11:46:54.116 dlg0x7f792417a ....Transaction tsx0x7f792417ae78 
state changed to Completed

Thanks for your fast response,

Valentin


On 25/03/2020 17.02, Tijmen de Mes wrote:
> Hi,
> 
> I see that my mail client did a weird thing with the conference domain in the text. Naturally it should be without the http, as it is not at all http, but sip :)
> 
> Best regards,
> 
> Tijmen de Mes
>> AG Projects
> 
> 
>> Op 25 mrt. 2020, om 16:55 heeft Tijmen de Mes <tijmen at ag-projects.com> het volgende geschreven:
>>
>> Hi,
>>
>> Thanks for the kind words about SylkServer/Sylk-webrtc.
>>
>> I suspect is has to do with the chat feature that was added. For this, the webrtc application connects to the ‘normal’ conference application.
>>
>> Is the conference application in SylkServer enabled? If it is not, you probably need to enable it and make it available on conference.yourdomain.at. It is probably also a good idea to limit access to the conference application by adding some firewall rules. The only service that will connect to it will be SylkServer itself.
>>
>> Best regards,
>>
>> Tijmen de Mes
>>>> AG Projects
>>> Op 25 mrt. 2020, om 16:18 heeft Valentin Kleibel <valentin at vrvis.at> het volgende geschreven:
>>>
>>> Hello,
>>>
>>> Thanks for creating such a cool piece of software. Out of all open source video conferencing systems we tested we prefer sylkserver and sylk-webrtc.
>>> We're interested in using sylkserver with webrtc support for audio- and videoconferencing and want to run our setup without sip connectivity.
>>> We also want to use authentication for our users and let them send invite links, but we don't want that everyone can open video conferences on our server.
>>>
>>> Up to now we've managed to run sylkserver and sylk-webrtc on our server and create anonymous video conferences that worked well for some time.
>>> But after about a minute one participant will disconnect and reconnect, while sylkserver logs 403 forbidden sip messages.
>>>
>>> 2020-03-25 13:20:43.557495 Packet 29 OUTGOING UDP XX:5060 -> XX:5060      │·
>>> SIP/2.0 403 Forbidden                      │·
>>> Via: SIP/2.0/UDP XX:5060;rport=5060;received=XX;branch=z9hG4bKPje736ed98-ad2e-│·
>>> 46ce-9f38-872120a72df2                      │·
>>> Call-ID: ad5a3d35-1e58-4b98-913f-c4bd0a8686db                      │·
>>> From: "dfsd" <sip:f6bf3e2e54874047 at guest.XX.at>;tag=62855d40-b9f1-4828-9a9b-8592bf830c│·
>>> 51                      │·
>>> To: <sip:riverringereater6 at conference.XX.at>;tag=f0569ead-2caf-43fa-ad4e-43cfa261fbbe │·
>>> CSeq: 5860 INVITE                      │·
>>> Server: SylkServer-5.5.0                      │·
>>> Content-Length:  0
>>>
>>> what is going wrong here? is such a setup even possible?
>>>
>>> Thanks for your help,
>>> Valentin
>>> _______________________________________________
>>> SIPBeyondVoIP mailing list
>>> SIPBeyondVoIP at lists.ag-projects.com
>>> https://lists.ag-projects.com/mailman/listinfo/sipbeyondvoip
>>
>> _______________________________________________
>> SIPBeyondVoIP mailing list
>> SIPBeyondVoIP at lists.ag-projects.com
>> https://lists.ag-projects.com/mailman/listinfo/sipbeyondvoip
> 
> _______________________________________________
> SIPBeyondVoIP mailing list
> SIPBeyondVoIP at lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/sipbeyondvoip
> 


More information about the SIPBeyondVoIP mailing list