Hello,
Yes. The log is for sems with mo profile.
I used SEMS as sbc applications in my network. Let me paste my
configurations below:
#sems.conf
interfaces=intern,extern
sip_ip_intern=192.168.18.20
sip_port_intern=5060
media_ip_intern=192.168.18.20
rtp_low_port_intern=2000
rtp_high_po
Hello,
if nobody here can provide an hit, maybe you should report the issue to
the sems project:
- https://github.com/sems-server/sems/issues
Cheers,
Daniel
On 24.01.18 12:17, Mojtaba wrote:
> Hello,
> I have a problem today, It's strange for me.
> Suppose we have this senario:
> uac1---
Hello,
Mojtaba wrote on 24.01.2018 12:17:
> Hello,
> I have a problem today, It's strange for me.
> Suppose we have this senario:
> uac1--->SEMS(mo profile)--->Kamailio>SEMS(mt
> profile)-->uac2
>
> In above topology, we have two interfaces(intern,extern) for SEMS, and
> j
Hello,
I have a problem today, It's strange for me.
Suppose we have this senario:
uac1--->SEMS(mo profile)--->Kamailio>SEMS(mt
profile)-->uac2
In above topology, we have two interfaces(intern,extern) for SEMS, and
just used as SBC (sbc application).
if i used port=5060 as e
