Hi Bogdan,
Thank you very much for the response. This issue has been solved.
Regards,
Yagishita
> Hi Yagishita,
>
> The error is not related to STUN - I see you configured 127.0.0.1:5060
> as a TCP listening interface, but it seams other application is already
> using it.
>
> Regards,
> Bo
Hi Yagishita,
The error is not related to STUN - I see you configured 127.0.0.1:5060
as a TCP listening interface, but it seams other application is already
using it.
Regards,
Bogdan
Koichi Yagishita wrote:
> Hi Bogdan,
>
> Thank you for your response. The following is output of /var/log/messa
Hi Bogdan,
Thank you for your response. The following is output of /var/log/messages and
ifconfig.
[/var/log/messages]
Jan 16 09:21:41 jrc opensips: WARNING:core:fix_socket_list: could not rev.
resolve 192.168.1.1
Jan 16 09:21:41 jrc opensips: WARNING:core:fix_socket_list: could not rev.
res
Hi Yagishita,
What is the error indicated in the logs
(http://www.opensips.org/Resources/DocsTsStart) ?
Regards,
Bogdan
Koichi Yagishita wrote:
> Dear all,
>
> After configuring the following related to stun in opensips.cfg for my
> opensips1.6.0, start-up of the opensips failed.
> What else s
Dear all,
After configuring the following related to stun in opensips.cfg for my
opensips1.6.0, start-up of the opensips failed.
What else should I configure to work STUN server?
[opensips.cfg]
### Modules Section
loadmodule "stun.so"
# - stun params -
modparam("stun",