Hi Fabio!
Just replace your condition in the reply route with my condition.
No, you don't need to any special commands for the rtpproxy.
Yes I have sample cfg - i already postet is ome time ago - search the archive.
regards, klaus
PS: cc to the list
Fabio Silvestri wrote:
Well, I have done changes on my ser.cfg, but I'm getting same erros when I run ser!
0(12525) ERROR: extract_mediaip: no `c=' in SDP
Klaus Darilion wrote:
Use ethereal and watch the packets traversing your proxy. Additionally, put log(1,"log messages....."); into your ser.cfg and watch them with: tail -f /var/log/messages
Put log statements after each condition and watch if the script behaves as it should.
Klaus
Fábio Silvestri wrote:
Hi!
I have a outbound proxy configured and working very well, but I have a little problem, when both clientes are registered on SER and behind a proxy!
The call's don't work, or the phone rings one time only, and in all cases the return voice, can't be listen.
Klaus, i'm using a script I have founded from you!
Regards.
Klaus Darilion wrote:
After cvs update on rtpproxy, now I'm getting this message when running:
# rtpproxy -2f:
rtpproxy: rtpproxy started, pid 1681 rtpproxy: command syntax error rtpproxy: command syntax error rtpproxy: command syntax error rtpproxy: command syntax error rtpproxy: command syntax error
Fábio Silvestri wrote:
You have to use rtpproxy v20040105 if you're working with 0.8.12 stable.
What do you mean with "both clients behind a proxy"? The clients are registered at different proxies? Then only one proxy has to enable the rtpproxy.
klaus
Fábio Silvestri wrote:
I have this structure!
. One server running SER as REGISTRAR . Another server as Outbound Proxy (running ser and rtpproxy)
Clients are ATA186, registering on first server, and when are inside NAT, using second server as Outbond.
Sometimes, they can't call each other, or the phones rings one time only, or can't rear anything.
Klaus Darilion wrote:
watch the packet flow using ngrep. analyze the INVITE and 200 OK messages if the SDP is rewritten properly (to point to the rtpproxy) watch the RTP stream using a packet sniffer (e.g. ethereal)
look into /var/log/messages and look ofr error and warnings produced by ser.
Klaus
Fábio Silvestri wrote: