Hi, it could be nice the possibility of adding headers in OpenSer replies. I
mean replies generated by OpenSer with "t_reply()" or "sl_reply()".
For example it could be cool adding a header:
"Success: User offline, message stored"
when using MSILO before:
if (m_store("$ru"))
t_reply("202", "Accepted"))
AFAIK this is not possible, is it?
If not, maybe I'd report it as feature request, what's your opinion about it?
Thanks.
--
Iñaki Baz Castillo
Actually i have one extra server in our Rack so i wanted to make Mediaproxy in different server then we may get better and more peformance.
Currently MediaProxy is installed in my same Openser Server and it is working well in production.
The Server where we need to install Mediaproxy, it is on same Network of Openser and i can ping well the difference is only that it is in NAT mode it does not have any public IP we only can connect that server through Openser or using some VPN connection
---------------------------------
Never miss a thing. Make Yahoo your homepage.
Hi,
Im trying to test mediaproxy for the first time, I am forcing all traffic through mediaproxy in the openser.cfg (there's
nothing wrong with that in principal is there?). I have one SIP handset hanging directly off OpenSER and another
connected to Asterisk which has a channel configured to OpenSER. I can get the call answered but there is audio
only in one direction and even more strangely I see that mediaproxy has not handled any data at all in the audio stream.
This is what I see from mediaproxy:
Feb 5 21:26:05 server proxydispatcher[13968]: request 75c5e34d0e567d5f1fa22f583ecc7af0(a)10.1.1.1 10.1.1.1:16042:audio 10.1.1.1 10.1.1.1 remote server.domain.net local Asterisk=20PBX info=from:0042*001@10.1.1.1,to:0044208888888@server.domain.net,fromtag:as1a72639d,totag:
Feb 5 21:26:05 server mediaproxy[13965]: request 75c5e34d0e567d5f1fa22f583ecc7af0(a)10.1.1.1 10.1.1.1:16042:audio 10.1.1.1 10.1.1.1 remote server.domain.net local Asterisk=20PBX info=totag:,to:0044208888888@server.domain.net,from:0042*001@10.1.1.1,fromtag:as1a72639d
Feb 5 21:26:05 server mediaproxy[13965]: session 75c5e34d0e567d5f1fa22f583ecc7af0(a)10.1.1.1: started. listening on 10.1.2.2:60006
Feb 5 21:26:05 server mediaproxy[13965]: execution time: 1.49 ms
Feb 5 21:26:05 server proxydispatcher[13968]: forwarding to mediaproxy on /var/run/mediaproxy.sock: got: '10.1.2.2 60006'
Feb 5 21:26:05 server proxydispatcher[13968]: execution time: 5.03 ms
Feb 5 21:26:53 server proxydispatcher[13968]: delete 75c5e34d0e567d5f1fa22f583ecc7af0(a)10.1.1.1 info=
Feb 5 21:26:53 server mediaproxy[13965]: delete 75c5e34d0e567d5f1fa22f583ecc7af0(a)10.1.1.1 info=
Feb 5 21:26:53 server mediaproxy[13965]: session 75c5e34d0e567d5f1fa22f583ecc7af0(a)10.1.1.1: 0/0/0 packets, 0/0/0 bytes (caller/called/relayed)
Feb 5 21:26:53 server mediaproxy[13965]: session 75c5e34d0e567d5f1fa22f583ecc7af0(a)10.1.1.1: ended.
Feb 5 21:26:53 server mediaproxy[13965]: execution time: 0.60 ms
Feb 5 21:26:53 server proxydispatcher[13968]: forwarding to mediaproxy on /var/run/mediaproxy.sock: got: ''
Feb 5 21:26:53 server proxydispatcher[13968]: execution time: 1.51 ms
This "0/0/0 packets, 0/0/0 bytes (caller/called/relayed)" being the part that I dont understand, well it proves its not handling the audio
stream, but other than put a use_media_proxy command in the openser route there isnt anything else I can do to get the data stream
to route via media proxy is there?
My openser route is very simple:
route{
if (!mf_process_maxfwd_header("15")) {
sl_send_reply("483","Too Many Hops");
exit;
};
if (msg:len >= max_len ) {
sl_send_reply("513", "Message too big");
exit;
};
if (method=="OPTIONS") {
exit;
};
if (method=="REGISTER") {
record_route();
if (!save("location")) {
sl_reply_error();
};
exit;
};
if (loose_route()) {
append_hf("P-hint: rr-enforced\r\n");
if(is_method("BYE"))
{ # log it all the time
acc_rad_request("200 ok");
acc_log_request("200 ok");
end_media_session();
}
route(1);
};
if(is_method("INVITE") && !has_totag())
{ # set the acc flags
record_route();
use_media_proxy();
setflag(1);
# setflag(2);
$avp(s:can_uri) = $ru;
};
if (!uri==myself) {
append_hf("P-hint: outbound\r\n");
route(1);
};
if (uri==myself) {
if (!lookup("location")) {
# log to acc as missed call
acc_rad_request("404 Not Found");
acc_log_request("404 Not Found");
sl_send_reply("404", "Not Found");
exit;
};
append_hf("P-hint: usrloc applied\r\n");
};
route(1);
}
# SECTION 5 - SECONDARY ROUTE BLOCKS
route[1] {
if (!t_relay()) {
sl_reply_error();
};
exit;
}
Anyone any ideas what might be going on or how I can investigate the issue further?
thanks for any help! Andy.
Hi All,
I read readme file of Mediaproxy that there is possibility to install mediaproxy on different server than Openser.
I have doubt how i can connect to that server my Mediaproxy server is in NAT mode and the IP is : 192.168.1.77 and my openser server is NO-NAT Mode and IP is : 212.XXX.XXX.XXX
Is there any possibility to communicate to Mediaserver? I tried the following in openser.cfg but i got error "CANNOT CONNECT TO MEDIAPROXY SERVER"
I forced media proxy to use 30001 port to accept remote command.
loadmodule "mediaproxy.so"
modparam("mediaproxy", "mediaproxy_socket", "192.168.1.77:30001")
modparam("mediaproxy", "sip_asymmetrics", "/usr/local/src/sip-server/modules/mediaproxy/config/sip-asymmetric-clients")
modparam("mediaproxy", "rtp_asymmetrics", "/usr/local/src/sip-server/modules/mediaproxy/config/rtp-asymmetric-clients")
modparam("mediaproxy", "natping_interval", 60)
--------
Regard,
---------------------------------
Looking for last minute shopping deals? Find them fast with Yahoo! Search.
Hi Abdul,
looking at the documentation this isnt a valid option:
modparam("mediaproxy", "mediaproxy_socket", "192.168.1.77:30001")Check http://openser.org/docs/modules/1.3.x/mediaproxy.htmlThe mediaproxy docs included with the mediaproxy software gives details of how to configure
remote mediaproxy servers, from my understanding you need to have a local proxydispatcher.sock
socket (defined in openser.cfg) then you need to follow the INSTALL and/or README files included
with mediaproxy to correctly configure your remote mediaproxy servers (and how they are located
by the proxydispatcher)
cheers Andy.
We need someone who can quickly assist us with creating the P-asserted
header on SER. RFC 3325. Configuration.
If there is an expert out there, please contact us with your qualifications
and rates.
Kenneth
Hi...
I am using the SER Presence agent for polling information from the server by sending SUBSCRIBE with expiration = 0 (just fetching the information). However, the server only responds to SUBSCRIBES with a time interval of 5 secondes between them. Is there any timer or parameter I can modify in order to reduce this time.
Thanks
Carlos
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Hi,
I have just downloaded the latest cvs sources of rel_2_0_0.
I compiled and installed it as usually:
make proper
make prefix=/homedir install
after this each time I start ser it breaks down
here my log from console:
Starting SER SIP Proxy: ser
$Listening on
udp: 127.0.0.1 [127.0.0.1]:7060
udp: 192.168.129.38 [192.168.129.38]:7060
tcp: 127.0.0.1 [127.0.0.1]:7060
tcp: 192.168.129.38 [192.168.129.38]:7060
Aliases:
tcp: venom:7060
tcp: venom.touk.pl:7060
tcp: localhost:7060
udp: venom:7060
udp: venom.touk.pl:7060
udp: localhost:7060
*: sip.rd.touk.pl:*
WARNING: no fork mode and more than one listen address found (will use only
the the first one)
0(11117) init_tcp: using epoll_lt as the io watch method (auto detected)
0(11117) Maxfwd module- initializing
0(11117) WARNING: xl_mod_init: more IP 192.168.129.38 not used
0(11117) WARNING: xl_mod_init: more IP 192.168.129.38 not used
0(11117) WARNING: xl_mod_init: more IP 192.168.129.38 not used
0(11117) WARNING: xl_mod_init: more IP 192.168.129.38 not used
0(11117) WARNING: xl_mod_init: more IP 192.168.129.38 not used
0(11117) WARNING: xl_mod_init: more IP 192.168.129.38 not used
0(11117) WARNING: xl_mod_init: more IP 192.168.129.38 not used
0(11117) WARNING: xl_mod_init: more IP 192.168.129.38 not used
0(11117) WARNING: xl_mod_init: more IP 192.168.129.38 not used
0(11117) AVPops - initializing
0(11117) using 'none' subscription authorization for presence!
0(11117) TRACE: qsa_interface.c:55: PA: PA_CONTENT_TYPE: 0x2ba1844692e0
0(11117) INFO: xcap_mod.c:55: xcap module initialization
0(11117) TRACE: virtual_subscription.c:55: RLS: RLS_PRESENCE_INFO:
0x2ba1844692e0
0(11117) TRACE: virtual_subscription.c:63: RLS: RLS_RAW: 0x2ba184479598
0(11117) using 'none' rls-subscription authorization!
0(11117) TRACE: qsa_events.c:331: presence_b2b: b2b_CONTENT_TYPE:
0x2ba1844692e0
0(11117) WARNING: tls: mod_init: tls support is disabled (set enable_tls=1
in the config to enable it)
exec - initializing
ERROR: error -1 while trying to fix configuration
Best regards
tomasz
Hello everyone;
I would like to rewrite the "To" field of all the SIP messages OpenSER
receives in order to make some tests. Such a function exists for the
originating part using rewriteuri or rewritehost, but I could not find
anything for the destination part.
Is it possible ? If yes, does somebody have a clue ? It would be very
helpful.
Thank you very much in advances.
Best Regards,
Skander