Hello,
you don't need to pass the REGISTER through the SBC, you can directly
send it to the registrar. E.g. if you need NAT ping from the edge
proxy, I would recommend using a separate proxy instance (e.g. using
sip-router), and send the calls through the SBC for RTP relay/topo
hiding/enforcing codecs/SST/CDR/billing etc.
To enable RTP relay, just set enable_rtprelay=yes in the SBC profile,
e.g. see symmetricrtp.sbcprofile.conf
(http://git.sip-router.org/cgi-bin/gitweb.cgi?p=sems;a=blob_plain;f=apps/sbc/etc/symmetricrtp.sbcprofile.conf).
hth
Stefan
o Hagay Unterman on 07/17/2011 01:45 PM:
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
--
frafos.com
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
