Hi!
Once again I'm stucked in the loose routing topic, maybe some can answer
my question!
I have ser configured to use RR. At the top of my ser.cfg I have:
# loose-route processing
log(1, "check loose_route ...");
if (loose_route()) {
log(1, "loose_route processing, finished routing!\n");
t_relay();
break;
};
log(1, "no loose_route processing\n");
...
Client A is xlite, which is a loose router, and Client B is Windows
Messenger 4.7, which is a strict router. One client calls the other
client, which accepts the call. Then the client hangs up.
If client A hangs up (xlite, loose router) the loose_route(){...} block
will not be processed and the BYE is handled by the following routing
logic. If client B (strict router) hangs up, the loose_route(){...}
block will be executed.
So, why is the request from xlite (loose router) not treated in the
loose_route block?
IMHO, I would suggest that both requests (loose and strict) should be
handled be the loose_route block. Also RFC3261 (16.4) says that "strict
router" request should be transformed into a loose routing request
(writing the last Route header field into the req-URI and remove this
route header field) and than be handled like all other requests.
Maybe I've missed something.
Regards,
Klaus
Hey...
When you call a cisco 7960 f.eks. you see a text string with the name
of a user. .. Is it possible "hook" ser upto a database, witch contains
the whole phonecatalog. then make ser lookup a number, then put it into
the realname feeld ?
- Atle
btw: I didn't tried the setup with serial cable and a dedicated NIC for
heartbeat as described in the hearbeat howto. I just had one NIC inside
the PCs which was also used for heartbeat.
klaus
Arnd Vehling wrote:
> nope, havent tried it yet. I am waiting for 2 new 1U rack boxes
> for testing it with. Thanx for the warning, ill keep u posted.
>
> -- Arnd
>
>
Hi,
I have already installed SER 0.8.9. Now I want to install 0.8.12 with MYSQL.
Is there anybody who can send me information for sequence of operations I
have to do to perform this uninstall (0.8.9) and install (0.8.12).
What I have to do on SER machine and what I have to do on MYSQL machine.
Thanks,
Fahriz Aqeel Ansari,
Telogy Inc, MD, USA.
Hi!
The question a little bit off topic, but I'm sure you canhelp me :-)
Usually, I used Redhat, but as they stopped their free update service,
I'm looking for a new platform.
In older postings, most people recommend debian, that's why I want to
give it a try. The debian homepage tells me, that security updates will
only be available for the stable release, so I wanted to use stable. But
stable does not support mysql 4, which is required for serweb.
So, what are your common practices to overcome such problems (the trade
off between stable/old software and unstable/new software)?
Do you use Debian testing?
Do you use just the base packages on stable and compile mysql 4 yourself?
Do you use backports or do you mix stable/testing?
thanks,
Klaus
Check out this method.
http://www.presttun.org/kare/DNS/DNS-LB-FT.pdf
It's designed for HTTP requests, but I don't see any reason that it couldn't
be used for SER as well.
Darren Nay
-----Original Message-----
From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at]
Sent: Thursday, February 26, 2004 12:55 PM
To: Andres
Cc: Nils Ohlmeier; serusers(a)lists.iptel.org
Subject: Re: [Serusers] replication and rtpproxy
But this will work only if the client uses your DNS servers, because the
DNS entries are cached by the other nameservers - or do you have a very
short TTL configured?
I think also softclients will have problems as Windows XP by default
caches the DNS lookups.
regards,
klaus
Andres wrote:
> Hi Klaus,
>
> We use DNS updates. We have special scripts based on sipsak (Thanks
Nils!),
> that check all SIP servers every minute. If something is wrong, then we
> update our DNS dynamically to point to another SIP Server. If the UAs are
> unable to register then they redo their DNS query and find the new IP.
> Works quite well in combination with replication since the backup server
has
> the exact duplicate location table.
>
> Regards,
> Andres
>
> ----- Original Message -----
> From: "Klaus Darilion" <klaus.mailinglists(a)pernau.at>
> To: "Nils Ohlmeier" <nils(a)iptel.org>
> Cc: <serusers(a)lists.iptel.org>
> Sent: Thursday, February 26, 2004 9:59 AM
> Subject: Re: [Serusers] replication and rtpproxy
>
>
>
>>
>>Nils Ohlmeier wrote:
>>
>>>On Thursday 26 February 2004 03:28, Arnd Vehling wrote:
>>>
>>>>Next question :) Is there any way that a failover server pickups the
>>>>neccessary port bindings for portaones rtpproxy or do will all
>>>>"rtpproxied" sessions fail when a failover server will take over
>>>>a primary server?
>>>
>>>
>>>As currently the rtp-proxy has to run on the same host as SER it does
>
> not make
>
>>>much sence IMHO to think about taking over rtp-proxy sessions. Then you
>
> would
>
>>>need some kind of rtp-proxy session replication, which should be easy
>
> when
>
>>>the nathelper module and the rtp proxy ever uses IP protocol for
>>>communication. But all this will only work if the backup server takes
>
> over
>
>>>the IP of the failed server, and you are not using SRV backup servers
>
> for
>
>>>example (except that a SRV backup can obviously also can takeover the
>
> IP).
>
>>Is it yet possible to build redundancy on top of SRV? I tested some
>>clients (Xlite, Budgetone-100, Windows Messenger 4.7) wether they use
>>SRV records to locate the proxy and Messenger is the only one who uses it.
>>
>>So, if I use these clients, is there any other failover solution than IP
>>takeover?
>>
>>regards,
>>klaus
>>
>>_______________________________________________
>>Serusers mailing list
>>serusers(a)lists.iptel.org
>>http://lists.iptel.org/mailman/listinfo/serusers
>>
>
>
>
>
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
Search the mailing list archive for configuration samples!
regards,
klaus
PS: cc to the mailing list!
Shirley Toh wrote:
> Hi ,
>
> How about the force_rtp_proxy? Where should I appropriate apply this
> command? The current Nat module have no problem going through from Symmetric
> Newtwork to Symmetric Network right? Thank you for your answer it really
> helps!!! :)
>
> Regards,
> Shirley
>
>
>>-----Original Message-----
>>From: Klaus Darilion [SMTP:klaus.mailinglists@pernau.at]
>>Sent: Thursday, February 26, 2004 8:18 PM
>>To: Shirley Toh
>>Cc: SER Users (E-mail)
>>Subject: Re: FW: [Serusers] Rtpproxy
>>
>>start ethereal on the machine with the SIP&RTP proxy. as filter use: UDP
>>Then take a look at the SIP messages. The nathelper module has to
>>rewrite the IP-address and the port in the SDP of the INVITE and the 200
>>OK message.
>>
>>klaus
>>
>>Shirley Toh wrote:
>>
>>>Hi,
>>>
>>>thank you for replying....
>>>
>>>Yes my UA do support Symmetric. What are the things that I have to take
>>
>>note
>>
>>>on the messages that whether the messages is properly written? And how
>>
>>can I
>>
>>>check the IP address and port on the RTP traffic? Please help...is
>>
>>really
>>
>>>greatly appreciated.
>>>
>>>
>>>Regards,
>>>Shirley
>>>
>>>
>>>
>>>>-----Original Message-----
>>>>From: Klaus Darilion [SMTP:klaus.mailinglists@pernau.at]
>>>>Sent: Thursday, February 26, 2004 5:56 PM
>>>>To: Shirley Toh
>>>>Cc: SER Users (E-mail)
>>>>Subject: Re: FW: [Serusers] Rtpproxy
>>>>
>>>>You have to provide more information. Which clients (do they support
>>>>symmetric RTP?). Take a look at SIP messages when they arive at the
>>>>proxy and when they are forwarded and vrify that the messages are
>>>>properly rewritten by the nathelper module.
>>>>
>>>>Check if there is any RTP traffic going to the RTPproxy and if it is
>>>>forwarded to the proper IP address and port.
>>>>
>>>>regards,
>>>>Klaus
>>>>
>>>>Shirley Toh wrote:
>>>>
>>>>
>>>>
>>>>>Hi,
>>>>>
>>>>>I am using the code below. When I am dialing through this scenario --->
>>>>>UA1(Symmetric NAT) ----> SER ---> UA2 (Symmetric NAT)
>>>>>. I hear no audio and I haev no error in my route. Please kindly advise
>>>>
>>>>is
>>>>
>>>>
>>>>>there something missing or I need to have extra components. I am using
>>>>
>>>>CVS
>>>>
>>>>
>>>>>rel_0.8.12 and latest rtpproxy!!! Help Help!!!
>>>>>
>>>>>Regards,
>>>>>Shirley
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>-----Original Message-----
>>>>>>From: Shirley Toh
>>>>>>Sent: Wednesday, February 25, 2004 6:37 PM
>>>>>>To: SER Users (E-mail)
>>>>>>Subject: FW: [Serusers] Rtpproxy
>>>>>>
>>>>>>Hi
>>>>>>
>>>>>>I have problem calling through UA behind Symmetric network? Please
>>>>
>>>>advice
>>>>
>>>>
>>>>>>any solution to this problem. Thank you!!!
>>>>>>
>>>>>>UA1(Symmetric NAT) ----> SER ---> UA2 (Symmetric NAT)
>>>>>>
>>>>>>Regards,
>>>>>>Shirley
>>>>>>-----Original Message-----
>>>>>>From: Shirley Toh
>>>>>>Sent: Tuesday, February 24, 2004 9:09 PM
>>>>>>To: 'Jan Janak'
>>>>>>Subject: RE: [Serusers] Rtpproxy
>>>>>>
>>>>>>Hi,
>>>>>>
>>>>>>Thank you for your answer.
>>>>>>
>>>>>>Can I check the latest module in CVS does it support to call from
>>>>>>Symmetric network to Symmetric network?Please help. If can what sgould
>>
>>I
>>
>>>>>>take note in the commands?
>>>>>>
>>>>>>Regards,
>>>>>>Shirley
>>>>>>
>>>>>>-----Original Message-----
>>>>>>From: Jan Janak [SMTP:jan@iptel.org]
>>>>>>Sent: Tuesday, February 24, 2004 8:35 PM
>>>>>>To: Shirley Toh
>>>>>>Cc: SER Users (E-mail)
>>>>>>Subject: Re: [Serusers] Rtpproxy
>>>>>>
>>>>>>You are calling force_rtp_proxy or fix_nated_sdp on a message with
>>
>>empty
>>
>>>>>>body. Make sure that you call the functions from the script only when
>>>>>>the message contains SDP body (usually INVITE and 200 OK).
>>>>>>
>>>>>>Jan.
>>>>>>
>>>>>>On 24-02 11:36, Shirley Toh wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Hi,
>>>>>>>
>>>>>>>Can anyone help me!! I am having this error on my log file when I try
>>>>
>>>>to
>>>>
>>>>
>>>>>>>make calls. I have attached my ser.cfg. Please help!! Thanks!!
>>>>>>>
>>>>>>>Feb 24 11:29:54 sipserver2 /usr/local/sbin/ser[20404]: ERROR:
>>>>>>>send_rtpp_command: can't read reply from a RTP proxy
>>>>>>>Feb 24 11:29:54 sipserver2 /usr/local/sbin/ser[20413]: ERROR:
>>>>>>
>>>>>>extract_body:
>>>>>>
>>>>>>
>>>>>>
>>>>>>>message body has lenght zero
>>>>>>>Feb 24 11:29:54 sipserver2 /usr/local/sbin/ser[20413]: ERROR:
>>>>>>>force_rtp_proxy: can't extract body from the message
>>>>>>>Feb 24 11:29:54 sipserver2 /usr/local/sbin/ser[20413]: ERROR:
>>
>>on_reply
>>
>>>>>>>processing failed
>>>>>>>Feb 24 11:29:54 sipserver2 /usr/local/sbin/ser[20417]: ERROR:
>>>>>>
>>>>>>extract_body:
>>>>>>
>>>>>>
>>>>>>
>>>>>>>message body has lenght zero
>>>>>>>Feb 24 11:29:54 sipserver2 /usr/local/sbin/ser[20417]: ERROR:
>>>>>>>force_rtp_proxy: can't extract body from the message
>>>>>>>Feb 24 11:29:54 sipserver2 /usr/local/sbin/ser[20417]: ERROR:
>>
>>on_reply
>>
>>>>>>>processing failed
>>>>>>>Feb 24 11:30:24 sipserver2 /usr/local/sbin/ser[20417]: ERROR:
>>>>>>
>>>>>>extract_body:
>>>>>>
>>>>>>
>>>>>>
>>>>>>>message body has lenght zero
>>>>>>>Feb 24 11:30:24 sipserver2 /usr/local/sbin/ser[20417]: ERROR:
>>>>>>>force_rtp_proxy: can't extract body from the message
>>>>>>>Feb 24 11:30:24 sipserver2 /usr/local/sbin/ser[20417]: ERROR:
>>
>>on_reply
>>
>>>>>>>processing failed
>>>>>>>Feb 24 11:30:24 sipserver2 /usr/local/sbin/ser[20407]: ERROR:
>>>>>>
>>>>>>extract_body:
>>>>>>
>>>>>>
>>>>>>
>>>>>>>message body has lenght zero
>>>>>>>Feb 24 11:30:24 sipserver2 /usr/local/sbin/ser[20407]: ERROR:
>>>>>>
>>>>>>fix_nated_sdp:
>>>>>>
>>>>>>
>>>>>>
>>>>>>>cannot extract body from msg!
>>>>>>>Feb 24 11:30:24 sipserver2 /usr/local/sbin/ser[20407]: ERROR:
>>>>>>
>>>>>>extract_body:
>>>>>>
>>>>>>
>>>>>>
>>>>>>>message body has lenght zero
>>>>>>>Feb 24 11:30:24 sipserver2 /usr/local/sbin/ser[20407]: ERROR:
>>>>>>>force_rtp_proxy: can't extract body from the message
>>>>>>>Feb 24 11:30:24 sipserver2 /usr/local/sbin/ser[20407]: ERROR:
>>
>>on_reply
>>
>>>>>>>processing failed
>>>>>>>
>>>>>>><<ser.cfg.txt>>
>>>>>>>
>>>>>>>regards,
>>>>>>>shirley
>>>>>>>
>>>>>>
>>>>>>>#
>>>>>>># $Id: ser.cfg,v 1.21.4.1 2003/11/10 15:35:15 andrei Exp $
>>>>>>>#
>>>>>>># simple quick-start config script
>>>>>>>#
>>>>>>>
>>>>>>># ----------- global configuration parameters
>>
>>------------------------
>>
>>>>>>>#debug=3 # debug level (cmd line: -dddddddddd)
>>>>>>>#fork=yes
>>>>>>>#log_stderror=no # (cmd line: -E)
>>>>>>>
>>>>>>>/* Uncomment these lines to enter debugging mode
>>>>>>>debug=7
>>>>>>>fork=no
>>>>>>>log_stderror=yes
>>>>>>>*/
>>>>>>>
>>>>>>>check_via=no # (cmd. line: -v)
>>>>>>>dns=no # (cmd. line: -r)
>>>>>>>rev_dns=no # (cmd. line: -R)
>>>>>>>#port=5060
>>>>>>>#children=4
>>>>>>>fifo="/tmp/ser_fifo"
>>>>>>>mhomed=yes
>>>>>>>
>>>>>>># ------------------ module loading
>>
>>----------------------------------
>>
>>>>>>># Uncomment this if you want to use SQL database
>>>>>>>loadmodule "/usr/local/lib/ser/modules/mysql.so"
>>>>>>>
>>>>>>>loadmodule "/usr/local/lib/ser/modules/nathelper.so"
>>>>>>>loadmodule "/usr/local/lib/ser/modules/textops.so"
>>>>>>>loadmodule "/usr/local/lib/ser/modules/sl.so"
>>>>>>>loadmodule "/usr/local/lib/ser/modules/tm.so"
>>>>>>>loadmodule "/usr/local/lib/ser/modules/rr.so"
>>>>>>>loadmodule "/usr/local/lib/ser/modules/maxfwd.so"
>>>>>>>loadmodule "/usr/local/lib/ser/modules/usrloc.so"
>>>>>>>loadmodule "/usr/local/lib/ser/modules/registrar.so"
>>>>>>>
>>>>>>># Uncomment this if you want digest authentication
>>>>>>># mysql.so must be loaded !
>>>>>>>loadmodule "/usr/local/lib/ser/modules/auth.so"
>>>>>>>loadmodule "/usr/local/lib/ser/modules/auth_db.so"
>>>>>>>
>>>>>>># ----------------- setting module-specific parameters
>>
>>---------------
>>
>>>>>>># -- usrloc params --
>>>>>>>
>>>>>>>#modparam("usrloc", "db_mode", 0)
>>>>>>>
>>>>>>># Uncomment this if you want to use SQL database
>>>>>>># for persistent storage and comment the previous line
>>>>>>>modparam("usrloc", "db_mode", 2)
>>>>>>>
>>>>>>># -- auth params --
>>>>>>># Uncomment if you are using auth module
>>>>>>>#
>>>>>>>modparam("auth_db", "calculate_ha1", yes)
>>>>>>>#
>>>>>>># If you set "calculate_ha1" parameter to yes (which true in this
>>>>>>
>>>>>>config),
>>>>>>
>>>>>>
>>>>>>
>>>>>>># uncomment also the following parameter)
>>>>>>>#
>>>>>>>modparam("auth_db", "password_column", "password")
>>>>>>>
>>>>>>># -- rr params --
>>>>>>># add value to ;lr param to make some broken UAs happy
>>>>>>>modparam("rr", "enable_full_lr", 1)
>>>>>>>
>>>>>>># -- Nathelper --
>>>>>>>modparam("registrar" , "nat_flag", 6)
>>>>>>>modparam("nathelper", "natping_interval", 60)
>>>>>>>modparam("nathelper", "ping_nated_only", 1)
>>>>>>>
>>>>>>># ------------------------- request routing logic
>>
>>-------------------
>>
>>>>>>># main routing logic
>>>>>>>
>>>>>>>route{
>>>>>>>
>>>>>>> # initial sanity checks -- messages with
>>>>>>> # max_forwards==0, or excessively long requests
>>>>>>> if (!mf_process_maxfwd_header("10")) {
>>>>>>> sl_send_reply("483","Too Many Hops");
>>>>>>> break;
>>>>>>>
>>>>>>> };
>>>>>>> if ( msg:len > max_len ) {
>>>>>>> sl_send_reply("513", "Message too big");
>>>>>>> break;
>>>>>>> };
>>>>>>>
>>>>>>>
>>>>>>> #!! Nathelper
>>>>>>> if (nat_uac_test("3")){
>>>>>>> if (method == "REGISTER"){
>>>>>>> log("LOG:Someone trying to register from
>>>>
>>>>private
>>>>
>>>>
>>>>>>IP, rewriting\n");
>>>>>>
>>>>>>
>>>>>>
>>>>>>> fix_nated_contact(); # Rewtite contact with
>>>>>>
>>>>>>source IP of signalling
>>>>>>
>>>>>>
>>>>>>
>>>>>>> if(method== "INVITE"){
>>>>>>> fix_nated_sdp("1"); # Add
>>>>>>
>>>>>>direction-active to SDP
>>>>>>
>>>>>>
>>>>>>
>>>>>>> };
>>>>>>> force_rport();
>>>>>>> setflag(6);
>>>>>>> };
>>>>>>> };
>>>>>>>
>>>>>>> # we record-route all messages -- to make sure that
>>>>>>> # subsequent messages will go through our proxy; that's
>>>>>>> # particularly good if upstream and downstream entities
>>>>>>> # use different transport protocol
>>>>>>> record_route();
>>>>>>> # loose-route processing
>>>>>>> if (loose_route()) {
>>>>>>> t_relay();
>>>>>>> break;
>>>>>>> };
>>>>>>>
>>>>>>> # if the request is for other domain use UsrLoc
>>>>>>> # (in case, it does not work, use the following command
>>>>>>> # with proper names and addresses in it)
>>>>>>> if (uri==myself) {
>>>>>>>
>>>>>>> if (method=="REGISTER") {
>>>>>>> save("location");
>>>>>>> break;
>>>>>>> };
>>>>>>>
>>>>>>> # native SIP destinations are handled using our USRLOC
>>>>>>
>>>>>>DB
>>>>>>
>>>>>>
>>>>>>
>>>>>>> if (!lookup("location")) {
>>>>>>> sl_send_reply("", "Connecting");
>>>>>>> break;
>>>>>>> };
>>>>>>> };
>>>>>>> if (isflagset(6)){
>>>>>>> force_rtp_proxy();
>>>>>>> };
>>>>>>> t_on_reply("1");
>>>>>>>
>>>>>>> # forward to current uri now; use stateful forwarding; that
>>>>>>> # works reliably even if we forward from TCP to UDP
>>>>>>> if (!t_relay()) {
>>>>>>> sl_reply_error();
>>>>>>> break;
>>>>>>> };
>>>>>>>
>>>>>>>}
>>>>>>>
>>>>>>># all incoming replies for t_onrepli-ed transactions enter here
>>>>>>>onreply_route[1] {
>>>>>>> if (isflagset(6) && status=~"(183)|2[0-9][0-9]") {
>>>>>>> fix_nated_contact();
>>>>>>> fix_nated_sdp("1");
>>>>>>> force_rtp_proxy();
>>>>>>> }else if(nat_uac_test("1")){
>>>>>>> fix_nated_contact();
>>>>>>> force_rtp_proxy();
>>>>>>> };
>>>>>>>
>>>>>>>}
>>>>>>
>>>>>>>_______________________________________________
>>>>>>>Serusers mailing list
>>>>>>>serusers(a)lists.iptel.org
>>>>>>>http://lists.iptel.org/mailman/listinfo/serusers
>>>>>
>>>>>
>>>>>_______________________________________________
>>>>>Serusers mailing list
>>>>>serusers(a)lists.iptel.org
>>>>>http://lists.iptel.org/mailman/listinfo/serusers
>>>>>
>>>>>
>>>
>>>
>>>
>
>
Shirley Toh wrote:
> Hi,
>
> thank you for your reply and your explaination! :)
>
> The record_routing that you are refering to is the save("location") to store
> into the database or what you meant by record_routing? Please
> advise...thanks.
>
> regards,
> shirley
>
>
>>-----Original Message-----
>>From: Klaus Darilion [SMTP:klaus.mailinglists@pernau.at]
>>Sent: Thursday, February 26, 2004 8:21 PM
>>To: Shirley Toh
>>Cc: SER Users (E-mail)
>>Subject: Re: [Serusers] NAT
>>
>>ser without record-routing: only the INVITE transaction traverses the
>>proxy, all other messages will be sent directly between the UAs.
>>
>>ser with record-routing: all the SIP messages traverse the proxy, the
>>RTP data is sent directly between both UAs.
>>
>>ser with record-route and rtpproxy: all SIP messages traverese the SIP
>>proxy and all RTP packets traverse the rtpproxy.
>>
>>
>>aklsu
>>
>>
>>Shirley Toh wrote:
>>
>>
>>>Hi,
>>>
>>>Can anyone tell me is SER is routing UA directly out and connect two UA
>>>directly or is it connect to SER always to do the transmission of data.
>>>Please advice?
>>>
>>>Regards,
>>>Shirley
>>>
>>>_______________________________________________
>>>Serusers mailing list
>>>serusers(a)lists.iptel.org
>>>http://lists.iptel.org/mailman/listinfo/serusers
>>>
>>>
>
>
>
Bogdan,
Sorry, I am not expressing myseft clearly, at this moment I intend to
configure a proxy no answer for the user (client1) who will upload the
script, to working this way: when a incoming call for user client1 ( the one
who uploaded the CPL script) reaches the SER and if he (client1) is busy the
call is forwarding to another user (client2). can you send me the script who
will work this way?
Thanks,
Toni
-----Original Message-----
From: Bogdan-Andrei IANCU [mailto:iancu@fokus.fraunhofer.de]
Sent: quinta-feira, 26 de Fevereiro de 2004 12:33
To: Toni Barata
Cc: 'serusers(a)lists.iptel.org'
Subject: Re: [Serusers] CPL
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
> > >
> > >
> > >
> > >
> >
>
Anyone know why I get this when connecting to/from an asterisk box?
Feb 26 12:54:55 ns-nby-ser1 /usr/local/sbin/ser[6785]: ERROR: t_newtran: EoH
not
parsed
Feb 26 12:54:55 ns-nby-ser1 /usr/local/sbin/ser[6785]: Warning:
sl_send_reply: I
won't send a reply for ACK!!
Feb 26 12:54:55 ns-nby-ser1 /usr/local/sbin/ser[6785]: ERROR: sl_reply_error
use
d: I'm terribly sorry, server error occured (1/SL)
Call lasts about3 seconds, then dies.
Any help would be grately appreciated.
Mike
