26 Feb
2004
26 Feb
'04
11:33 p.m.
Toni Barata wrote:
Hi Bogdan,
The version of ser is 0.8.13. (I will update from cvs today)
About the timeout issue, ok, the proxy no answer works with the "tm"
modparams.
My question now is, how to configure a proxy no answer and busy for
the same user who will upload the script?
Just add both noanswer and busy tag to your proxy:
<cpl>
<incoming>
<location url="sip:client2@10.112.128.5">
<proxy>
<noanswer>
<location url="sip:client3@10.112.128.5">
<proxy />
</location>
</noanswer>
<busy>
<location url=".......">
<proxy/>
</location>
</busy>
</proxy>
</location>
</incoming>
</cpl>
Can you try to see if the crash still happens (after setting that tm
params) ?
Bogdan
Thanks again,
Toni
-----Original Message-----
From: Bogdan-Andrei IANCU [mailto:iancu@fokus.fraunhofer.de]
Sent: quinta-feira, 26 de Fevereiro de 2004 12:02
To: Toni Barata
Cc: 'serusers(a)lists.iptel.org'
Subject: Re: [Serusers] CPL
Hi Tony,
First one question: what ser version are you using?
The noanswer issue was previous disscused on the mailing list - here is
some copy past :
Try to do the followings:
modparam("tm","noisy_ctimer",1) # this will force timeout
modparam("tm","fr_inv_timer",30) # sets the timeout for INVITE to 40
sec
(default is 120)
Please tell me if this works for you.
Toni Barata wrote:
Hi Bogdan,
Thanks for the recomendation ;-)
But I still have some troubles with the script for "proxy if no
answer".
If I upload the following script on the user,
e.g. "client1", the
"proxy if no answer" works for the new url (in the first location tag):
<cpl>
<incoming>
<location url="sip:client2@10.112.128.5">
<proxy>
<noanswer>
<location url="sip:client3@10.112.128.5">
<proxy />
</location>
</noanswer>
</proxy>
</location>
</incoming>
</cpl>
But if the "new" url is the same of the client who have uploaded the
script (client1), like in the following script, the ser respond with a
"too many hops error":
make sens to do so. If somebody calls user client1, it's script will do
proxy to himself (to clinet1) and the request will hit again the proxy,
the CPL script will be run again, and so one.....
<cpl>
<incoming>
<location url="sip:client1@10.112.128.5">
<proxy>
<noanswer>
<location url="sip:client2@10.112.128.5">
<proxy />
</location>
</noanswer>
</proxy>
</location>
</incoming>
</cpl>
So my question is, how can i implement the script to activate the
proxy no answer to the user who will upload the script?
Many Thanks,
Toni
-----Original Message-----
From: Bogdan-Andrei IANCU [mailto:iancu@fokus.fraunhofer.de]
Sent: quarta-feira, 25 de Fevereiro de 2004 17:49
To: Toni Barata
Cc: 'serusers(a)lists.iptel.org'
Subject: Re: [Serusers] CPL
Hi Toni,
the problem is that your script is wrong. Please read carefully the
cpl-draft from ietf
http://www.ietf.org/internet-drafts/draft-ietf-iptel-cpl-08.txt (there
are also several examples there).
Some hints: when you do proxy, your location set is empty - there is no
location or lookup tag before and for incoming processing the location
set is init as empty. That's the reason for this message:
(17752) DEBUG:run_proxy: location set found empty -> going on
failure/default branch
and as your proxy tag has no failure/default branch, the interpreter
will return to SER script (default behavior).
About timeout, yes indeed, it is not supported for the moment. This
parameter is totally ignored.
Regards,
Bogdan
Toni Barata wrote:
Hi Bogdan,
We are experiencing some problems with the proxy no answer (timeout
don't work?) and proxy on busy in our scripts.
script for proxy if busy on client "cliente1":
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE cpl PUBLIC '-//IETF//DTD RFCxxxx CPL 1.0//EN' 'cpl.dtd'>
<cpl>
<incoming>
<proxy ordering="sequential">
<busy>
<location url="sip:1234@10.112.128.5" />
</busy>
</proxy>
</incoming>
</cpl>
debug for proxy if busy:
6(17752) DEBUG:cpl-c:get_dest_user: tring to get user from new_uri
6(17752) DEBUG:cpl-c:get_dest_user: tring to get user from R_uri
6(17752) DEBUG:get_user_script: fetching script for user
<cliente1(a)10.112.128.5>
6(17752) DEBUG:get_user_script: we got the script len=58
6(17752) DEBUG: t_check: msg id=12 global id=12 T start=0x422bb6a8
6(17752) DEBUG: t_check: T alredy found!
6(17752) parse_headers: flags=-1
6(17752) check_via_address(10.112.128.55, 10.112.128.55, 0)
6(17752) WARNING:vqm_resize: resize(0) called
6(17752) DEBUG: reply sent out. buf=0x80c9c98: SIP/2.0 1...,
shmem=0x422bd0f8: SIP/2.0 1
6(17752) DEBUG: t_reply: finished
6(17752) DEBUG:cpl_run_script: processing CPL node
6(17752) DEBUG:cpl_run_script: processing proxy node
6(17752) DEBUG:run_proxy: location set found empty -> going on
failure/default branch !!!!!!!!!!!!!!!!?????????????
6(17752) DEBUG:cpl_c:cpl_run_script: running default action
6(17752) rewrite(): Rewriting Request-URI with
'sip:10.112.128.220:14045'
script for proxy if no answer on client "cliente1":
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE cpl PUBLIC '-//IETF//DTD RFCxxxx CPL 1.0//EN' 'cpl.dtd'>
<cpl>
<incoming>
<proxy ordering="sequential" timeout="5">
<noanswer>
<location url="sip:666@10.112.128.5" />
</noanswer>
</proxy>
</incoming>
</cpl>
debug for proxy if no answer:
5(17963) DEBUG:cpl-c:get_dest_user: tring to get user from new_uri
5(17963) DEBUG:cpl-c:get_dest_user: tring to get user from R_uri
5(17963) DEBUG:get_user_script: fetching script for user
<cliente1(a)10.112.128.5>
5(17963) DEBUG:get_user_script: we got the script len=62
5(17963) DEBUG: t_check: msg id=680 global id=680 T start=0x42355b88
5(17963) DEBUG: t_check: T alredy found!
5(17963) parse_headers: flags=-1
5(17963) check_via_address(10.112.128.55, 10.112.128.55, 0)
5(17963) WARNING:vqm_resize: resize(0) called
5(17963) DEBUG: reply sent out. buf=0x80cac78: SIP/2.0 1...,
shmem=0x422e8a58: SIP/2.0 1
5(17963) DEBUG: t_reply: finished
5(17963) DEBUG:cpl_run_script: processing CPL node
5(17963) DEBUG:cpl_run_script: processing proxy node
5(17963) DEBUG:run_proxy: location set found empty -> going on
failure/default branch (the same problem!!!!!!!!!!!!!!!)
5(17963) DEBUG:cpl_c:cpl_run_script: running default action
5(17963) rewrite(): Rewriting Request-URI with
'sip:10.112.128.220:14045'
Can you help us on these issues?
Best regards,
Toni