Hi, Looks like it tries to listen tls on the same port as sip. You may check that tls-sip-port param is set to 5061 on your internal profile? If it does not work, you need to share your profile config and the full debug logs. Best Regards, -- Vallimamod Abdullah SIP Solutions vma@sip.solutions linkedin.com/in/vallimamod .
On 11 Mar 2019, at 22:15, Moshe Rosenberg <moshe.rosenberg@gmail.com> wrote:
this is the error i got when i start it
2019-03-11 09:02:02.359870 [ERR] sofia.c:3228 Error Creating SIP UA for profile: internal (sip:mod_sofia@207.148.17.xx:5060;maddr=207.148.17.84;transport=udp,tcp) ATTEMPT 1 (RETRY IN 5 SEC) 2019-03-11 09:02:07.359880 [ERR] sofia.c:3228 Error Creating SIP UA for profile: internal (sip:mod_sofia@207.148.17.xx:5060;maddr=207.148.17.84;transport=udp,tcp) ATTEMPT 2 (RETRY IN 5 SEC) 2019-03-11 09:02:12.359880 [ERR] sofia.c:3228 Error Creating SIP UA for profile: internal (sip:mod_sofia@207.148.17.xx:5060;maddr=207.148.17.84;transport=udp,tcp) ATTEMPT 3 (RETRY IN 5 SEC) 2019-03-11 09:02:12.359880 [ERR] sofia.c:3238 Error Creating SIP UA for profile: internal (sip:mod_sofia@207.148.17.xx:5060;maddr=207.148.17.84;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.
how ever as soon as i disable TLS the profile will start i checked and i have a valid cert installed and this worked for while with the cert in place
any ideas where alse to look #1