Hi all,
I'm new to the list so sorry if this question has already been answered.
I have has a search through all the posts and all the info at iptel.org but alas am still having a problem with my ser.
What I am trying to do is set ser up as an off net solution for our current VOIP/SIP systems.
I have most of it nailed and have thus far found ser very easy to work with the help great. I have now hit a bit of a road block. I am trying to get the rtpproxy working with ser so that ALL rtp streams go through the ser proxy and not from the off net phone directly to the called phone. I have the rtpproxy and it runs fine (so far as I can tell) but when trying to get ser to use it I keep getting an error in the logs about loadmodule and unknown module, the error is: unknown command, missing loadmodule? This is being trigered by the line in the ser.cfg file force_rtp_proxy. I used the example from the voip-info.org so am a little unsure of what I have done wrong. Is there something else I need to do? There is little documentation about rtpproxy...
I am running Debian on a 2.4.21 kernel and have used the ser .deb packeges for the ser install.
Any help would be great.
Thanks, Stephen
----------------------------------------------------------------------------------------------- This message and any attachments contain privileged and confidential information. If you are not the intended recipient of this message, you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immediately via email and then destroy this message and any attachments.
On Oct 24, 2003 at 15:26, Stephen Miles smiles@callplus.co.nz wrote:
Hi all,
[...]
You must load the nathelper module (which implements force_rtp_proxy) - add: loadmodule "/usr/lib/ser/modules/nathelper.so" to your ser.cfg.
Andrei
Hi Andrei,
I have the nathelper module being loaded but am still getting an error. Here is my log, can you shed any light on this for me?
Oct 28 09:52:13 portal ser: loading module /usr/lib/ser/modules/sl.so Oct 28 09:52:13 portal ser: loading module /usr/lib/ser/modules/tm.so Oct 28 09:52:13 portal ser: loading module /usr/lib/ser/modules/rr.so Oct 28 09:52:13 portal ser: loading module /usr/lib/ser/modules/maxfwd.so Oct 28 09:52:13 portal ser: loading module /usr/lib/ser/modules/usrloc.so Oct 28 09:52:13 portal ser: loading module /usr/lib/ser/modules/registrar.so Oct 28 09:52:13 portal ser: loading module /usr/lib/ser/modules/nathelper.so Oct 28 09:52:13 portal ser: set_mod_param_regex: usrloc matches module usrloc Oct 28 09:52:13 portal ser: set_mod_param_regex: found <db_mode> in module usrloc [/usr/lib/ser/modules/usrloc.so] Oct 28 09:52:13 portal ser: set_mod_param_regex: rr matches module rr Oct 28 09:52:13 portal ser: set_mod_param_regex: found <enable_full_lr> in module rr [/usr/lib/ser/modules/rr.so] Oct 28 09:52:13 portal ser: find_export: found <mf_process_maxfwd_header> in module maxfwd_module [/usr/lib/ser/modules/maxfwd.so] Oct 28 09:52:13 portal ser: find_export: found <sl_send_reply> in module sl_module [/usr/lib/ser/modules/sl.so] Oct 28 09:52:13 portal ser: find_export: found <sl_send_reply> in module sl_module [/usr/lib/ser/modules/sl.so] Oct 28 09:52:13 portal ser: find_export: found <record_route> in module rr [/usr/lib/ser/modules/rr.so] Oct 28 09:52:13 portal ser: find_export: found <loose_route> in module rr [/usr/lib/ser/modules/rr.so] Oct 28 09:52:13 portal ser: find_export: found <t_relay> in module tm [/usr/lib/ser/modules/tm.so] Oct 28 09:52:13 portal ser: find_export: found <sl_send_reply> in module sl_module [/usr/lib/ser/modules/sl.so] Oct 28 09:52:13 portal ser: find_export: found <save> in module registrar [/usr/lib/ser/modules/registrar.so] Oct 28 09:52:13 portal ser: find_export: found <record_route> in module rr [/usr/lib/ser/modules/rr.so] Oct 28 09:52:13 portal ser: find_export: <force_rtp_proxy> not found Oct 28 09:52:13 portal ser: find_export: <force_rtp_proxy> not found Oct 28 09:52:13 portal ser: parse error (131,32-33): unknown command, missing loadmodule? Oct 28 09:52:13 portal ser: find_export: found <t_on_reply> in module tm [/usr/lib/ser/modules/tm.so] Oct 28 09:52:13 portal ser: parse error (135,1-14): parse error Oct 28 09:52:13 portal ser: parse error (135,1-14): bad command Oct 28 09:52:13 portal ser: parse error (135,1-14): bad command Oct 28 09:52:13 portal ser: parse error (135,14-15): bad command Oct 28 09:52:13 portal ser: parse error (135,15-16): bad command Oct 28 09:52:13 portal ser: parse error (135,16-17): bad command Oct 28 09:52:13 portal ser: parse error (135,18-19): bad command Oct 28 09:52:13 portal ser: find_export: <force_rtp_proxy> not found Oct 28 09:52:13 portal ser: find_export: <force_rtp_proxy> not found Oct 28 09:52:13 portal ser: parse error (137,32-33): unknown command, missing loadmodule? Oct 28 09:52:13 portal ser: DEBUG: tm_shutdown : start Oct 28 09:52:13 portal ser: DEBUG: tm_shutdown : empting hash table Oct 28 09:52:13 portal ser: DEBUG: tm_shutdown: releasing timers Oct 28 09:52:13 portal ser: DEBUG: tm_shutdown : removing semaphores Oct 28 09:52:13 portal ser: DEBUG: tm_shutdown : done Oct 28 09:52:13 portal ser: shm_mem_destroy Oct 28 09:52:13 portal ser: destroying the shared memory lock
Thanks,
Stephen
Andrei Pelinescu-Onciul wrote:
----------------------------------------------------------------------------------------------- This message and any attachments contain privileged and confidential information. If you are not the intended recipient of this message, you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immediately via email and then destroy this message and any attachments.
Hi Stephen,
it is relativly easy: your config script contains errors in lines 131, 135 and 137. Please check your script at the positions given in the error messages (line, character). If you are not able to find the errors on your own, send your config to us for review.
Regards Nils
On Monday 27 October 2003 21:54, Stephen Miles wrote:
On Oct 28, 2003 at 09:54, Stephen Miles smiles@callplus.co.nz wrote:
Yes, force_rtp_proxy exists only in the nathelper module from ser unstable (cvs HEAD). Sorry I didn't notice the part about using ser debian packages (which implies you use ser stable).
You could try getting ser unstable sources and compiling it, however right now we are doing a lot of changes and the current cvs might be broken. It is probably safer to use a version from 2 weeks ago.
Andrei
Hi Andrei,
I have grabbed the latest cvs version and have compiled it and seems to be running ok. I now get an error 5(3681) ERROR: extract_mediaip: no `c=' in SDP when I try to place a call from a soft phone on my laptop through the ser proxy running on the proxy box. Any ideas?
Also is there a way to get ser to forward/relay registers to another server? We have a SIP server (broadsoft) setup and I need all the register and call info, and calls to be routed from ser to the broadsoft server.
Is it possible to set ser up as just a proxy where it takes the client request and then proxies it to our other sip server?
Any info would be great.
Thanks
Stephen
Andrei Pelinescu-Onciul wrote:
----------------------------------------------------------------------------------------------- This message and any attachments contain privileged and confidential information. If you are not the intended recipient of this message, you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immediately via email and then destroy this message and any attachments.
-
Andrei Pelinescu-Onciul -
Nils Ohlmeier -
Stephen Miles