-
Hi there, I'm experimenting with libresbc and I have the following setup: Public-IP (User) ---> firewall/NAT (with 1 to 1 NAT to libresbc private address, 94.156.34.168 < - > 10.80.80.12) ---> Private IP (kamailio) ---> Loopback IP (freeswitch) ----> Private IP (freeswitch) ----> Private IP (core). with 3 netalias address spaces and 3 sipprofiles: inbound (10.80.80.12:5060) --> access_service (localhost:5060 to localhost:5080) --> core (127.0.0.1:5080) --> outbound (10.80.80.12:5090) (configuration is very similar to what is described here) but with a firewall in front. On the libresbc I have enabled Access control. SIP signaling traffic is going without a problem. The issues is with RTP and I think I know why it is not flowing but I'm not sure is it a bug or configuration issue :-) RTP address and port are advertised in the SIP/SDP packets. I have inbound netalias which sets libresbc to listen to his internal address and advertise his public address. I use this netalias as rtp_address in the core sipprofile, but as you can see in the picture it uses the 'listen' address in the SDP packets, not the 'advertise' as I was expecting. I'm expecting in the SDP packets to see libresbc public IP address. When I access the libresbc from a client behind the firewall in the same IP subnet as libresbc the audio is working 100%. Of course I can expose libresbc directly in the Internet and this will solve the issue but I prefer to keep it behind a firewall. Any idea/suggestions will be great :) inbound netalias:
core_netalias:
core sipprofile:
netstat -tulpen
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
Hi @bilbobg
|
Beta Was this translation helpful? Give feedback.
-
this will be fixed by #55 |
Beta Was this translation helpful? Give feedback.
this will be fixed by #55