Hello Yanchong, WangYanchong wrote on 09/10/2014 11:52 AM: > However, when I tried to make a call between phones registered through > sbc(192.168.131.1/192.168.131.128) with active sbc profile use > transparent.sbcprofile.conf. > I always got a 404 error from sems sbc, I can not understand why it > does not relay the invitation request to the kamailio server(which is > the target registrar server with address 192.168.130.126:5060), and > just send out 404 to phones.
I didn't see before that you're using enable_reg_caching=yes on both INVITEs coming from the caller UA as well as when the call comes from kamailio. Thus sems tries to look up an entry in the registration cache with the callee user name (10022) instead of the alias, which of course it doesn't find. What you should do is to create different profiles. For REGISTER requests from the UAs and for messages coming from kamailio, use enable_reg_caching=yes. For other messages from the UAs, use enable_reg_caching=no and next_hop=192.168.130.126:5060. See the examples on selecting the profile with regex maps on top of the Readme.sbc.txt I realize that the configuration for reg cache with the different profiles is not that simple, but I think there should be an example somewhere. Or can someone else on this list can post their complete configuration, so we can add that as example to the doc? Best Regards Stefan _______________________________________________ Sems mailing list [email protected] http://lists.iptel.org/mailman/listinfo/sems
