Hello to all!
I need a little help with our ser installation (ser-2.0.0-rc1). Due some network restrictions, we need to force every call to pass trought rtpproxy. Could someone point me to the right place where to force it? Please an example based on our config would be really helpful, but in two scenarios: 1. ALL CALLS trought rtpproxy 2. ONLY CALLS from a given network trought rtpproxy We are in doubt on what choose between the two solutions. Having both examples could me help to implement the needs faster :)
Thank's a lot for your help!
Simon
No help at all? It would be a good start point a doc to read concern this aspect. Of course, an example based on the conf could me help a lot better.
Thank's to all!
Simon
Il 06/05/2011 10:40, Simone Felici ha scritto:
Hello to all!
I need a little help with our ser installation (ser-2.0.0-rc1). Due some network restrictions, we need to force every call to pass trought rtpproxy. Could someone point me to the right place where to force it? Please an example based on our config would be really helpful, but in two scenarios:
- ALL CALLS trought rtpproxy
- ONLY CALLS from a given network trought rtpproxy
We are in doubt on what choose between the two solutions. Having both examples could me help to implement the needs faster :)
Thank's a lot for your help!
Simon
Hi,
did you look at the manuals? You must simply issue a rtpproxy_offer/_answer to engage the RTPProxy from your route/reply_route, as described in the manual: http://www.kamailio.org/docs/modules/devel/modules/rtpproxy.html#id3056341
Carsten
2011/5/9 Simone Felici s.felici@mclink.eu:
No help at all? It would be a good start point a doc to read concern this aspect. Of course, an example based on the conf could me help a lot better.
Thank's to all!
Simon
Il 06/05/2011 10:40, Simone Felici ha scritto:
Hello to all!
I need a little help with our ser installation (ser-2.0.0-rc1). Due some network restrictions, we need to force every call to pass trought rtpproxy. Could someone point me to the right place where to force it? Please an example based on our config would be really helpful, but in two scenarios:
- ALL CALLS trought rtpproxy
- ONLY CALLS from a given network trought rtpproxy
We are in doubt on what choose between the two solutions. Having both examples could me help to implement the needs faster :)
Thank's a lot for your help!
Simon
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hello,
I'll start from here and set-up a scenario to test it out. Is it compatible with ser-2.0.0-rc1 used by me?
Thank's for the answer.
Simon
Il 09/05/2011 10:28, Carsten Bock ha scritto:
Hi,
did you look at the manuals? You must simply issue a rtpproxy_offer/_answer to engage the RTPProxy from your route/reply_route, as described in the manual: http://www.kamailio.org/docs/modules/devel/modules/rtpproxy.html#id3056341
Carsten
2011/5/9 Simone Felicis.felici@mclink.eu:
No help at all? It would be a good start point a doc to read concern this aspect. Of course, an example based on the conf could me help a lot better.
Thank's to all!
Simon
Il 06/05/2011 10:40, Simone Felici ha scritto:
Hello to all!
I need a little help with our ser installation (ser-2.0.0-rc1). Due some network restrictions, we need to force every call to pass trought rtpproxy. Could someone point me to the right place where to force it? Please an example based on our config would be really helpful, but in two scenarios:
- ALL CALLS trought rtpproxy
- ONLY CALLS from a given network trought rtpproxy
We are in doubt on what choose between the two solutions. Having both examples could me help to implement the needs faster :)
Thank's a lot for your help!
Simon
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hi Simone,
it should be similar for SER 2.0. The commands may be different though, so you probably do one of the following: - upgrade to a more recent SER version - check the readme for your version (should be in modules/nathelper directory)
Carsten
2011/5/9 Simone Felici s.felici@mclink.eu:
Hello,
I'll start from here and set-up a scenario to test it out. Is it compatible with ser-2.0.0-rc1 used by me?
Thank's for the answer.
Simon
Il 09/05/2011 10:28, Carsten Bock ha scritto:
Hi,
did you look at the manuals? You must simply issue a rtpproxy_offer/_answer to engage the RTPProxy from your route/reply_route, as described in the manual: http://www.kamailio.org/docs/modules/devel/modules/rtpproxy.html#id3056341
Carsten
2011/5/9 Simone Felicis.felici@mclink.eu:
No help at all? It would be a good start point a doc to read concern this aspect. Of course, an example based on the conf could me help a lot better.
Thank's to all!
Simon
Il 06/05/2011 10:40, Simone Felici ha scritto:
Hello to all!
I need a little help with our ser installation (ser-2.0.0-rc1). Due some network restrictions, we need to force every call to pass trought rtpproxy. Could someone point me to the right place where to force it? Please an example based on our config would be really helpful, but in two scenarios:
- ALL CALLS trought rtpproxy
- ONLY CALLS from a given network trought rtpproxy
We are in doubt on what choose between the two solutions. Having both examples could me help to implement the needs faster :)
Thank's a lot for your help!
Simon
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Simone Felici Divisione Tecnica: Progettazione e Sviluppo
tel. +39 0461.030.111 fax. +39 0461 030.112 Via Fersina, 23 - 38123 Trento
MC-link S.p.A. Sede Direzionale e Amministrativa Via Carlo Perrier, 9/a - 00157 Roma Sede Legale Via Fersina, 23 - 38123 Trento
Save a tree. Don't print this e-mail unless it's really necessary
Informativa ai sensi del Codice della proprietà industriale e del Codice dei dati personali. Le informazioni contenute in questa e-mail e negli eventuali allegati, possono contenere informazioni confidenziali e coperte da segreto commerciale/industriale. Esse vengono comunicate nei limiti giuridici dei rapporti in essere fra le parti e pertanto nessun ulteriore diritto di proprietà intellettuale o industriale può essere rivendicato dal ricevente. Le informazioni contenute in questa e-mail e negli eventuali allegati sono indirizzate esclusivamente a coloro che figurano come destinatari. Se avete ricevuto per errore questa e-mail siete pregati di informarci (rispedendola al mittente) e di provvedere alla sua rimozione, a non farne utilizzo e a non conservarne alcuna copia.
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hi Carsten,
The upgrade is something I would like to do very! But at the moment there are so many customizations on the structure. Could be maintained, but the work sould be almost long. I search to understand if at least this command is implemented and then look forward. Meanwhile many thank's
Simon
Il 09/05/2011 11:48, Carsten Bock ha scritto:
Hi Simone,
it should be similar for SER 2.0. The commands may be different though, so you probably do one of the following:
- upgrade to a more recent SER version
- check the readme for your version (should be in modules/nathelper directory)
Carsten
-
Carsten Bock -
Simone Felici