4 Jun
2007
4 Jun
'07
2:20 p.m.
Hi,
The config is the mediaproxy-template from
http://www.sipwise.com/wizard/ , so it's really just very basic.
The odd thing is, that when using rtpproxy instead of mediaproxy, it
works as expected. Something must be wrong with my mediaproxy setup, but
there isn't much to do wrong, and I also get a correct answer from
mediaproxy for the lookup:
proxydispatcher[26619]: forwarding to mediaproxy on
/var/run/mediaproxy.sock: got: '84.19.176.11 30002'
I'm running out of ideas. To sum it up: rtpproxy works in this setup,
mediaproxy doesn't. I haven't seen this before, and I've set up quite a
lot of such setups :o)
Andreas
Lesley Liu wrote:
Hi,
Could you attach all packets or openser.cfg?
Regards,
Lesley
2007/6/4, Andreas Granig <agranig(a)sipwise.com
<mailto:agranig@sipwise.com>>:
Hi,
Maybe you can check the contact of INVITE from
sip proxy to callee.
Try fix_contact () for INVITE.
The contact is fixed for INVITE. Also, replies are routed according to
the Via-Header, so this isn't the issue.
What I've found out in the meanwhile is, that it's the use_media_proxy()
in the reply-route which causes the problem. If I comment this line,
the
200-OK is routed without problems (but there's one-way-audio,
obviously). Any hints in that direction?
Regards,
Andreas