Hey Stefan, thanks for you answer. I try to make the setup like you said, but the SEMS server in the middle response with 501 Not Implemented if a client is trying to register.
My config is: -----sbc.conf----- profiles=sst_b2b, exin, inex, reg active_profile=$M($RI=>exin), $M($Rn=>inex) -----exin.conf----- REGISTER=>reg # SIP NAT handling: recommended if dealing with far end NATs dlg_nat_handling=yes # destination IP[:port] for outgoing requests next_hop=10.99.250.26:5060 ## RTP relay # enable RTP relaying (bridging): enable_rtprelay=yes -----inex.conf----- enable_reg_lookup=yes Perhaps I do not understand the profile syntax in the right way? Cheers, Kai -----Ursprüngliche Nachricht----- Von: Stefan Sayer [mailto:[email protected]] Gesendet: Freitag, 8. Mai 2015 16:40 An: Ohnacker, Kai [CBC]; [email protected] Betreff: Re: [Sems] SEMS as SBC in front of kamailio Hello Kai, [email protected] wrote on 05/07/2015 03:08 PM: > Hello, > > > > I'm working actually on a project with a kamailio as registrar, > redirect and proxy server. For NATing I want to use SEMS and the > server shall work as a SBC, which forwards all messages (REGISTER, > INVITE etc.) from the external to the internal interface (SEMS work > with 2 interfaces) and vice versa. I configure the external/ internal > IP sockets in the sems.conf and load the required plugins. But what > are the next steps? Perhaps there is somewhere a howto, which guide me > through this process? > > The infrastructure is: Kamailio (private network) ---- Firewall/ NAT > ---- SEMS (DMZ - public network) ---- Firewall ---- internet (public > network) > For INVITEs you will need two profiles, one in each direction (UA->SEMS->Kamailio and Kamailio->SEMS->UA). For REGISTERs coming from the UAs you will need one more profile. The very first Paragraph in doc/Readme.sbc.txt gives some examples for selecting profiles, e.g. on regex; as key you can e.g. use source IP ($si) or also local/received IP ($Ri) or also the interface ($Rf, $Rn or $RI). For the REGISTERs, you need to activate registration caching using enable_reg_caching=yes. For the INVITE-profile towards Kamailio, you need to activate NAT handling (dlg_nat_handling, enable_rtprelay, ...), and set the next hop to Kamailio. For the INVITE profile coming from Kamailio, you need to activate the reg cache lookup, this will set the RURI/next hop from the reg cache. There is quite some more options that can be set in the profiles, I'd recommend to have a look at Readme.sbc.txt. hth Stefan > > > > > Cheers, > > Kai > > > > _______________________________________________ > Sems mailing list > [email protected] > http://lists.iptel.org/mailman/listinfo/sems > _______________________________________________ Sems mailing list [email protected] http://lists.iptel.org/mailman/listinfo/sems
