Abdul,
On Tue, 5 Dec 2006 at 18:22 -0800, Abdul Qadir wrote:
> I have attached my oralce include file.
You should not send big attachments to the list.
I unpacked your archive to /usr/local/oracle9, and changed DEFS
definition inside modules/oracle/Makefile to
DEFS += -I/usr/local/oracle9/demo -I/usr/local/oracle9/public
After that I was able to build the module without errors with
"make modules=modules/oracle modules" command.
Please, double-check your path to the includes, and verify it is
properly passed to the compiler. Sample output for dbase.c compilation
is as follows (note the include paths at the end):
gcc -fPIC -DPIC -g -O9 -funroll-loops -Wcast-align -Wall
-minline-all-stringops -malign-double -falign-loops -ftree-vectorize
-mtune=athlon64 -DNAME='"ser"' -DVERSION='"0.9.7-pre7"'
-DARCH='"i386"' -DOS='"linux"' -DCOMPILER='"gcc 4.1.2"' -D__CPU_i386
-D__OS_linux -DCFG_DIR='"/usr/local/etc/ser/"' -DPKG_MALLOC -DSHM_MEM
-DSHM_MMAP -DDNS_IP_HACK -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP
-DDISABLE_NAGLE -DF_MALLOC -DFAST_LOCK -DADAPTIVE_WAIT
-DADAPTIVE_WAIT_LOOPS=1024 -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN
-DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL
-DHAVE_ALLOCA_H -DLINUX -D_GNU_SOURCE -D_REENTRANT
-I/usr/local/oracle9/demo -I/usr/local/oracle9/public -c dbase.c -o
dbase.o
> Dmitry Semyonov <dsemyonov(a)dins.ru> wrote: Abdul,
>
> On Mon, 4 Dec 2006 at 23:44 -0800, Abdul Qadir wrote:
>
> > Thats why I did modified the make file to reflect my path. But
> > still getting the same error. Do u think I still need to install
> > Instant Client, although I have full client installed.
>
> I don't think so.
--
...Bye..Dmitry.
Hi all,
Is it deal with the ctd.sh script? Configure inside loose_route()?
I can get the REFER message but no responses (202 Accepted and NOTIFY) to it.
So I send reply 202 inside loose_route if method=REFER.
After that, inside ethereal, I can see the code 202 response to REFER.
However, It send REFER again and after a while 408 TIMEOUT.
This is what i configured:
if(loose_route()){
if(method=="BYE"){
setflag(1);
setflag(2);
};
if(method=="REFER"){
sl_send_reply("202","Accepted");
};
t_relay();
break;
};
Please help.
Thanks in advance
Regards,
jorain
----- Original Message -----
From: Greger V. Teigre
To: jorain
Sent: Tuesday, December 05, 2006 9:30 PM
Subject: Re: [Serusers] Call transfer
cc serusers
jorain wrote:
Thanks Greger,
Could you give me some clues how to do that or some references about it? I really have no idea.
Thanks again.
Regards,
jorain
----- Original Message -----
From: Greger V. Teigre
To: jorain
Cc: SER+RTPproxy
Sent: Monday, December 04, 2006 7:48 PM
Subject: Re: [Serusers] Call transfer
Well, yes, you have to route REFER, and you should allow NOTIFYs.
g-)
jorain wrote:
Hi all,
I have some question about call transfer.
When I press transfer key follow by the new destination and "send", I can see the REFER message inside ethereal but after that request timeout error(408).
Inside REFER message, i can see the refer-to and referred-by values are correct.
Do I need to add something inside ser.cfg to enable call transfering? Because I cannot find any sample codings regarding ser call transfer.
Thanks for any help.
Regards,
jorain
------------------------------------------------------------------------
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
Hi Nick,
Here is how the top of my cfg looks now:
debug=3 # debug level (cmd line: -dddddddddd)
fork=no
log_stderror=no # (cmd line: -E)
log_facility=LOG_LOCAL6
I also added this line to syslog.conf:
# Save openser accounting logs to openseracc.log
local6.* -/var/log/openseracc.log
Previously there was information written to /var/log/openser.log which
contained mostly things that happened on start up. It seems that openser
logs to that file by default even if there is no log_facility set in the
cfg file. Now all those messages are instead being put in
/var/log/openseracc.log. However, still there are no accounting messages
logged.
Any ideas?
Thanks again,
Daniel
nick wrote:
> Daniel Burge wrote:
>> Hello,
>>
>> I'm trying to configure the accounting module to log messages to
>> syslog by following the instructions here:
>>
>> http://www.openser.org/docs/modules/1.1.x/acc.html
>>
>> I've included these lines where appropriate according to the example
>> on that page. The meaningful parts of the code are as follows:
>>
>> loadmodule "/usr/local/lib64/openser/modules/acc.so"
>> modparam("acc", "log_level", 1)
>> modparam("acc", "log_flag", 1)
>>
>> route
>> {
>> if (method=="INVITE" || method=="BYE" || method=="CANCEL")
>> {
>> setflag(1); /* set for accounting (the same value as in log_flag!)
>> } }
>>
>> However this is not causing any information to be logged to syslog.
>>
>> Any idea?
>>
>> Thanks in advance,
>>
>> Daniel
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)openser.org
>> http://openser.org/cgi-bin/mailman/listinfo/users
>>
>
>
> Make sure you put a line at the top of your config like:
>
> log_facility=LOG_LOCAL6
>
> The number at the end can vary, it depends on what Log facilities you
> have "free" on your system.
>
>
Hello,
I'm trying to configure the accounting module to log messages to syslog
by following the instructions here:
http://www.openser.org/docs/modules/1.1.x/acc.html
I've included these lines where appropriate according to the example on
that page. The meaningful parts of the code are as follows:
loadmodule "/usr/local/lib64/openser/modules/acc.so"
modparam("acc", "log_level", 1)
modparam("acc", "log_flag", 1)
route
{
if (method=="INVITE" || method=="BYE" || method=="CANCEL")
{
setflag(1); /* set for accounting (the same value as in log_flag!)
}
}
However this is not causing any information to be logged to syslog.
Any idea?
Thanks in advance,
Daniel
Hi everybody,
following some time ago discussion, a new Pseudo-Variable (PV) is
exported by the TM module "- $T_reply_code" - this PV will offer access
the the reply code from all different kind of routes. See:
http://www.openser.org/docs/modules/1.2.x/tm.html#AEN562
This will allow mainly access (printing, comparing, pushing into AVPs,
logging, etc) to the reply code of the winning reply in failure_route.
regards,
bogdan
Hi,
I'm using UAC module in order to centralized authentication when I
need to use an external proxy server to call PSTN numbers. To use it, I use
a unique tuple login/pwd/domain
The environment is:
My openser handles the domain: "myopenserdomain.com"
For each INVITE or REGISTER of SIP client of this domain, I force
the authentication
The external proxy handles the domain "externaldomain.com"
Now I have two questions:
1) before to send an INVITE to the external proxy, must I change the
contact header with the correct information of the tuple login/pwd/domain ?
Or I must wait the 401 or 407 message before ? In fact I tests several
external proxy. Some are waiting a contact header with the information of
the tuple and some don't. What is the correct way to do this ?
2) Some of this external proxy accept only my INVITE (with or
without contact header modified) if I registered first on it ! I receive 403
message in this situation. But I don't know how to REGISTER first since I
don't find any openser module to that . How can I handle this situation ?
Thanks,
Regards,
Christophe
Hi everybody,
following several discussion threads from some time ago, I added a
support for controlling the behaviour of t_relay() functions. This
addresses:
1) to ability to stop t_relay() from automatically sending the 100
trying provisional reply before relaying the request. This is useful in
scenarios where you already send a stateless 100 trying from the script.
2) ability to do serial forking in failover scenarios - as original
t_relay() automatically sends a negative reply in case of a failure
(unresolvable URI, TCP connect refused, etc), it was impossible to
continue with the next destination. Now, the auto-reply can be disabled.
backward compatibility is kept.
For more details (how to do it, options, etc), please see the online docs:
http://www.openser.org/docs/modules/1.2.x/tm.html#AEN340
regards,
bogdan
Hi all,
Someone using LVS can send his configuration to help us?
Thanks,
Thomas
-----Message d'origine-----
De : users-bounces(a)openser.org [mailto:users-bounces@openser.org] De la part de Klaus Darilion
Envoyé : mercredi, 6. décembre 2006 09:58
À : Watkins, Bradley
Cc : users(a)openser.org
Objet : Re: [Users] Load Balancing
Hi Bradley!
Watkins, Bradley wrote:
>
> I use UltraMonkey (www.ultramonkey.org), but it's basically a packaging
> of Linux-HA and LVS.
>
> LVS supports connection persistence, and that works very well. The
> level of granularity of load balancing is on a per-IP basis, not
> per-transaction (LVS only does L3 load-balancing, not L4-7). But
> assuming a reasonable value for the persistence timeout, there should be
> no problems with SIP transactions (and I haven't experienced anything
> problematic).
Are you using TCP or UDP (or both) for SIP?
Reading LVS doc I see there are several methods for packet forwarding:
- Direct Routing
- IP-IP Encapsulation
- NAT
Which one do you use?
regards
Klaus
>
> Ldirectord also supports SIP health checks (they're pretty basic OPTIONS
> requests, but it's something), and will fail over to working SIP
> proxies. Of course, in-progress transactions will fail as the OpenSER
> process on one box doesn't have the stateful knowledge of the other.
>
> Regards,
> - Brad
> The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
>
> _______________________________________________
> Users mailing list
> Users(a)openser.org
> http://openser.org/cgi-bin/mailman/listinfo/users
--
Klaus Darilion
nic.at
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
Hi,
thanks to Lavinia Andrei, we added today a new transport implementation
for the Management Interface (MI). This is XMRPC and it the second after
the initial FIFO transport, but not the last :).
The module is build by using the xmlrpc library, following all XMLRPC
standards. It is in alpha stage, so more testing is needed.
NOTE that only commands ported to the new MI interface (and not all
former FIFO cmds) are available via XMLRPC, but this is a temporary
problem - there are only 2 module left to update (TM and USRLOC).
For more info, please see the online documentation:
http://www.openser.org/docs/modules/1.2.x/mi_xmlrpc.html
or ask on the mailing list.
Any feedback - bugs or improvements - are welcomed.
Regards,
Bogdan
