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?
Best Regards
Max M.
Am 17.07.2011 13:45, schrieb Hagay Unterman:
Hi,
I would like to implement SEMS as SBC.
User will register against the SBC which will forward the REGISTER to
the PROXY behind it.
After the registration, users (behind NAT) will be able to execute
calls which will go to SEMS which will forward to the PROXY which will
send the message to SEMS which will connect the end side.
The call flow is:
1. User A send REGISTER to SEMS.
2. SEMS pass REGISTER from A to PROXY
3. PROXY answer 200 OK to SEMS with transfer to User A
4. User B send REGISTER to SEMS.
5. SEMS pass REGISTER from A to PROXY
6. PROXY answer 200 OK to SEMS with transfer to User B
Now both user A and B are register in PROXY thgouht SEMS.
7. Now User A initiate call to User B.
8. User A send INVITE B to SEMS which pass the INVITE to PROXY which
send INVITE to SEMS with B details and SEMS send the INVITE to User B.
9. After B answer we will have RTP path between A and B (through SEMS
which is the SBC).
Is it possible?
If yes, can someone guide me to the conf files (Examples)?
Thanks.
A
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
