[OpenSIPS-Users] sipsak and sip_trace module
Bogdan-Andrei Iancu
bogdan at opensips.org
Wed May 11 09:35:12 CEST 2016
Change your routing script to be sure that the OPTIONS request does not
hit the load balancing logic. Maybe you should reply to it using the
options module:
http://www.opensips.org/html/docs/modules/2.1.x/options.html#id293442
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 11.05.2016 10:31, Nduwayezu, Joselyne wrote:
> Hello Bogdan,
>
> Thank you for your reply. How can i fix it then?
>
> NDUWAYEZU Joselyne
>
> 2016-05-11 9:28 GMT+02:00 Bogdan-Andrei Iancu <bogdan at opensips.org
> <mailto:bogdan at opensips.org>>:
>
> Hi,
>
> Your OPTIONS hits the load_balance() function which returns false
> in this case as only INVITEs are supposed to be handled by this
> function.
>
> Best regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> http://www.opensips-solutions.com
>
> On 10.05.2016 17:37, Francjos wrote:
>
> hello ,
>
> I wish
>
> I'm using two opensips servers in redundancy mode, i would
> like one be able
> to check if the other is still aliveand vice versa. I use a
> sipsak to
> perform this.
> But when i execute the commande "sipsak -s sip:opensips at xxxx
> where xxx in
> the ip address of the other server, i get the following:
>
>
> Server 10.0.0.5 gives:
> .
>
>
> U 2016/05/10 13:57:12.402720 10.0.0.5:47413
> <http://10.0.0.5:47413> -> 10.0.0.4:5060 <http://10.0.0.4:5060>
> OPTIONS sip:opensips at 10.0.0.4 <mailto:sip%3Aopensips at 10.0.0.4>
> SIP/2.0.
> Via: SIP/2.0/UDP
> 10.0.0.5:47413;branch=z9hG4bK.3fc50b66;rport;alias.
> From: sip:sipsak at 10.0.0.5:47413;tag=4c5c78b9.
> To: sip:opensips at 10.0.0.4 <mailto:sip%3Aopensips at 10.0.0.4>.
> Call-ID: 1281128633 at 10.0.0.5 <mailto:1281128633 at 10.0.0.5>.
> CSeq: 1 OPTIONS.
> Contact: sip:sipsak at 10.0.0.5:47413
> <http://sip:sipsak@10.0.0.5:47413>.
> Content-Length: 0.
> Max-Forwards: 70.
> User-Agent: sipsak 0.9.6.
> Accept: text/plain.
> .
>
>
> U 2016/05/10 13:57:12.405823 10.0.0.4:5060
> <http://10.0.0.4:5060> -> 10.0.0.5:47413 <http://10.0.0.5:47413>
> SIP/2.0 500 Service full.
> Via: SIP/2.0/UDP
> 10.0.0.5:47413;received=10.0.0.5;branch=z9hG4bK.3fc50b66;rport=47413;alias.
> From: sip:sipsak at 10.0.0.5:47413;tag=4c5c78b9.
> To: sip:opensips at 10.0.0.4
> <mailto:sip%3Aopensips at 10.0.0.4>;tag=61890dad1e908c702027bf054a266115.c3bd.
> Call-ID: 1281128633 at 10.0.0.5 <mailto:1281128633 at 10.0.0.5>.
> CSeq: 1 OPTIONS.
> Server: OpenSIPS (2.1.2 (x86_64/linux)).
> Content-Length: 0.
> .
>
>
>
>
> Server 10.0.0.4 gives:
>
>
>
>
> root at front-1:/etc/opensips# ngrep -d eth0 -t -W byline "$1"
> port 5060 -q
> interface: eth0 (10.0.0.0/255.255.255.0
> <http://10.0.0.0/255.255.255.0>)
> filter: (ip or ip6) and ( port 5060 )
>
> U 2016/05/10 13:57:12.406208 10.0.0.5:47413
> <http://10.0.0.5:47413> -> 10.0.0.4:5060 <http://10.0.0.4:5060>
> OPTIONS sip:opensips at 10.0.0.4 <mailto:sip%3Aopensips at 10.0.0.4>
> SIP/2.0.
> Via: SIP/2.0/UDP
> 10.0.0.5:47413;branch=z9hG4bK.3fc50b66;rport;alias.
> From: sip:sipsak at 10.0.0.5:47413;tag=4c5c78b9.
> To: sip:opensips at 10.0.0.4 <mailto:sip%3Aopensips at 10.0.0.4>.
> Call-ID: 1281128633 at 10.0.0.5 <mailto:1281128633 at 10.0.0.5>.
> CSeq: 1 OPTIONS.
> Contact: sip:sipsak at 10.0.0.5:47413
> <http://sip:sipsak@10.0.0.5:47413>.
> Content-Length: 0.
> Max-Forwards: 70.
> User-Agent: sipsak 0.9.6.
> Accept: text/plain.
> .
>
>
> U 2016/05/10 13:57:12.406735 10.0.0.4:5060
> <http://10.0.0.4:5060> -> 10.0.0.5:47413 <http://10.0.0.5:47413>
> SIP/2.0 500 Service full.
> Via: SIP/2.0/UDP
> 10.0.0.5:47413;received=10.0.0.5;branch=z9hG4bK.3fc50b66;rport=47413;alias.
> From: sip:sipsak at 10.0.0.5:47413;tag=4c5c78b9.
> To: sip:opensips at 10.0.0.4
> <mailto:sip%3Aopensips at 10.0.0.4>;tag=61890dad1e908c702027bf054a266115.c3bd.
> Call-ID: 1281128633 at 10.0.0.5 <mailto:1281128633 at 10.0.0.5>.
> CSeq: 1 OPTIONS.
> Server: OpenSIPS (2.1.2 (x86_64/linux)).
> Content-Length: 0.
>
>
>
> I guess the error "500 Service full" is related to a bloc in
> the script
> where i define the routing logic for the load balancing:
>
>
>
>
>
> ## Freeswitch
> route[2] {
>
> xlog("L_NOTICE","[$pr:$fU@$si:$sp]: This is
> Media-Server Route Use
> Load-balancer NOW!!\n");
> if (!load_balance("1","calls")) {
> sl_send_reply("500","Service full");
> exit;
> }
> xlog("L_NOTICE","[$pr:$fU@$si:$sp]: Selected destination
> Media-Server : $du\n");
> }
>
> In need more explanation how i can fix that.
> Is sipsak a tool of checking the status of the servers or are
> there othor
> tools?
>
> My end goal is to put in place high availability with the two
> servers.
> Ideas please!!!!!
>
>
>
>
> --
> View this message in context:
> http://opensips-open-sip-server.1449251.n2.nabble.com/sipsak-and-sip-trace-module-tp7602933.html
> Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org <mailto:Users at lists.opensips.org>
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
>
> Haute École de Bruxelles
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20160511/19cf76c0/attachment-0001.htm>
More information about the Users
mailing list