nothing special:
RTPproxy: ./rtpproxy -fl 127.0.0.1 -s udp:127.0.0.1:7899 $ ./rtpproxy -v Basic version: 20040107 Extension 20050322: Support for multiple RTP streams and MOH Extension 20060704: Support for extra parameter in the V command
OpenSER: $ ./openser -V version: openser 1.3.0-pre1-notls (i386/linux) flags: STATS: Off, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535 poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. svnrevision: 2:2992M @(#) $Id: main.c 2880 2007-10-08 07:13:00Z henningw $ main.c compiled on 04:47:44 Oct 29 2007 with gcc 4.1.3
modparam("nathelper", "rtpproxy_sock", "2 == udp:localhost:7899") modparam("nathelper", "natping_interval", 0) modparam("nathelper", "sipping_bflag", 7) modparam("nathelper", "sipping_from", "sip:pinger@test.ro") modparam("nathelper", "sipping_method", "OPTIONS") modparam("nathelper", "ping_nated_only", 0) modparam("nathelper", "natping_processes", 3)
regards, bogdan
Iñaki Baz Castillo wrote:
El Tuesday 30 October 2007 10:28:36 Bogdan-Andrei Iancu escribió:
But why do you need to keep the timeout in the location table? keep it in avp table or in the subscriber table.
I don't understand how can be useful a timeout value in subscriber table. If a subscriber calls it will hangup when he decides, why to force it?
I use LCR for call before users with greater "q". And I insert entries in "location" table via web app to implement forwarding (depending on the "q" value it can be serial or parallel). So I need a INVITE timeout for each forwarding but not for each subscriber user.
For example:
"location" table:
username domain contact q timeout
200 domain.org sip:200@10.10.1.33:5060 0.50 null 200 domain.org sip:215@domain.org 0.40 20 200 domain.org sip:66612323@domain.org 0.30 60 200 domain.org sip:65532090@domain.org 0.30 60
When 200@domain.org is called "next_contacts()" returns "sip:200@10.10.1.33:5060" (the "real" registered user) so it's valid the parameter "fr_inv_timer_next" of "lcr" module.
If it doesn't answer, failure_route calls to sip:215@domain.org. The timeout would be "lcr" - "fr_inv_timer_next" by default, but I'd like this to be customizable per entry in "location" table: During "lookup(location)" "timeout" field should be loaded as "fr_inv_timer_avp".
For this I'd need a way to load that value when doing "lookup()".
That is why it'd be cool this feature in my case.
Regards.