Bug 33540 - не запускается профиль internal c дефолтным конфигом.
Summary: не запускается профиль internal c дефолтным конфигом.
Status: CLOSED FIXED
Alias: None
Product: Branch p8
Classification: Distributions
Component: freeswitch-daemon (show other bugs)
Version: не указана
Hardware: all Linux
: P3 normal
Assignee: Andrey Cherepanov
QA Contact: qa-p8@altlinux.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-09 17:57 MSK by Bolshedvorsky Evgeny
Modified: 2018-11-01 11:07 MSK (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bolshedvorsky Evgeny 2017-06-09 17:57:41 MSK
2017-06-09 17:52:07.297444 [ERR] sofia.c:3146 Error Creating SIP UA for profile: internal (sip:mod_sofia@10.10.3.182:5060;transport=udp,tcp) ATTEMPT 2 (RETRY IN 5 SEC)
2017-06-09 17:52:12.297429 [ERR] sofia.c:3146 Error Creating SIP UA for profile: internal (sip:mod_sofia@10.10.3.182:5060;transport=udp,tcp) ATTEMPT 3 (RETRY IN 5 SEC)
2017-06-09 17:52:12.297429 [ERR] sofia.c:3156 Error Creating SIP UA for profile: internal (sip:mod_sofia@10.10.3.182:5060;transport=udp,tcp)
The likely causes for this are:
1) Another application is already listening on the specified address.
2) The IP the profile is attempting to bind to is not local to this system.


Судя по всему, не может сделать bind на ipv4. IP родной, порт 5060 не занят.
Comment 1 Bolshedvorsky Evgeny 2017-06-09 18:12:19 MSK
Дело secure websocket
<param name="wss-binding" value=":7443"/>
Comment 2 Anton Farygin 2018-11-01 11:07:37 MSK
Нужно начать было с генерации ключей. по идее после генерации ключей websocket должен заработать