Hi,
sorry, my message was a bit out of context. Let me explain.
I dont need this yet, but also noticed there is was no support for
register requests. And imho a sbc should be able to handle Register
Requests, e.g. to forward Requests to the Registrar Server on the inside
network. At least this is one of the points described in rfc5853 right?
For example, sbc would be located on the border of two networks and
should be the only SIP entry point to connect from the outside WAN. In
this Scenario a registration to the Proxy and outbound routing to the
SBC might be okay.. But does it really make sense? I would prefer to
keep everything internal and only expose the SBC to the outside.
Best Regards
Max M.
Am 19.07.2011 13:24, schrieb Stefan Sayer:
o Max Mühlbronner on 07/18/2011 11:48 AM:
Hi,
the sbc module currently does not support REGISTER Requests.
sbc1 sems[16839]: [#7f5c74e10700] [onOoDRequest, AmApi.cpp:104] INFO:
sorry, we don't support beginning a new session with a 'REGISTER'
message
So the scenario you mentioned would not be possible out of the box.
The current SBC is okay for inbound/outbound traffic, but handling
Registrations should also be supported? Maybe this is already known
and planned to be supported in the future?
scenario- and feature-wise, what would you like to see there?
- registration caching (take re-register load off registrar if Contact
has not changed)
- NAT traversal (Fix Contact)
- NAT pinging
- ?
I'm not sure this is best implemented in SEMS - it seems like
duplicating proxy features.
Stefan
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
