Hello,
i am experiencing problems with 3CX using SEMS in combination with Kamailio as
Authentication Proxy.
If i connect the 3CX with SEMS there is a problem in transmitting RTP audio to
3CX, which is behind a natted firewall.
The firewall is not a problem. It is already tested with a soft client and also
in combination with Kamailio and Asterisk as B2BUA.
Everything worked fine with asterisk as Media Server.
I guess the problem is, when using tcpdump to analyze the RTP Packages, that
SEMs will send the packages to the internal
ip address of 3CX.
So finally using wireshark on the windows server, none of the packages will
arrive.
This is the extract of the tcpdump, where sems is running at.
I replaced the exernal ip with "EXTERNALIP". Here you can see the internal ip
address of the 3cx:
10:54:17.349118 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 200)
EXTERNALIP.28272 > 10.10.150.80.7022: UDP, length 172
10:54:17.369092 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 200)
EXTERNALIP.28272 > 10.10.150.80.7022: UDP, length 172
10:54:17.389113 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 200)
EXTERNALIP.28272 > 10.10.150.80.7022: UDP, length 172
When using asterisk, instead of the internal ip, there you can see the firewall
ip, which works clean.
Do you think it's a problem with kamailio or 3cx itself or is there a way to
figure out, what's the problem why sems
wants to send the packages to the internal ip of 3cx?
With kind regards
Daniel Vukicevic
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
