sipsak and sip_trace module

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

sipsak and sip_trace module

Francjos
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@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 -> 10.0.0.4:5060
OPTIONS sip:opensips@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@10.0.0.5:47413;tag=4c5c78b9.
To: sip:opensips@10.0.0.4.
Call-ID: 1281128633@10.0.0.5.
CSeq: 1 OPTIONS.
Contact: 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 -> 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@10.0.0.5:47413;tag=4c5c78b9.
To: sip:opensips@10.0.0.4;tag=61890dad1e908c702027bf054a266115.c3bd.
Call-ID: 1281128633@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@front-1:/etc/opensips# ngrep -d eth0 -t -W byline "$1" port 5060 -q
interface: eth0 (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 -> 10.0.0.4:5060
OPTIONS sip:opensips@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@10.0.0.5:47413;tag=4c5c78b9.
To: sip:opensips@10.0.0.4.
Call-ID: 1281128633@10.0.0.5.
CSeq: 1 OPTIONS.
Contact: 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 -> 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@10.0.0.5:47413;tag=4c5c78b9.
To: sip:opensips@10.0.0.4;tag=61890dad1e908c702027bf054a266115.c3bd.
Call-ID: 1281128633@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!!!!!
Reply | Threaded
Open this post in threaded view
|

Re: sipsak and sip_trace module

Bogdan-Andrei Iancu-2
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@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 -> 10.0.0.4:5060
> OPTIONS sip:opensips@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@10.0.0.5:47413;tag=4c5c78b9.
> To: sip:opensips@10.0.0.4.
> Call-ID: 1281128633@10.0.0.5.
> CSeq: 1 OPTIONS.
> Contact: 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 -> 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@10.0.0.5:47413;tag=4c5c78b9.
> To: sip:opensips@10.0.0.4;tag=61890dad1e908c702027bf054a266115.c3bd.
> Call-ID: 1281128633@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@front-1:/etc/opensips# ngrep -d eth0 -t -W byline "$1" port 5060 -q
> interface: eth0 (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 -> 10.0.0.4:5060
> OPTIONS sip:opensips@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@10.0.0.5:47413;tag=4c5c78b9.
> To: sip:opensips@10.0.0.4.
> Call-ID: 1281128633@10.0.0.5.
> CSeq: 1 OPTIONS.
> Contact: 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 -> 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@10.0.0.5:47413;tag=4c5c78b9.
> To: sip:opensips@10.0.0.4;tag=61890dad1e908c702027bf054a266115.c3bd.
> Call-ID: 1281128633@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
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: sipsak and sip_trace module

Bogdan-Andrei Iancu-2
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 <[hidden email]>:
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@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 -> 10.0.0.4:5060
OPTIONS [hidden email] SIP/2.0.
Via: SIP/2.0/UDP 10.0.0.5:47413;branch=z9hG4bK.3fc50b66;rport;alias.
From: [hidden email].
To: [hidden email].
Call-ID: [hidden email].
CSeq: 1 OPTIONS.
Contact: 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 -> 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: [hidden email].
To: [hidden email];tag=61890dad1e908c702027bf054a266115.c3bd.
Call-ID: [hidden email].
CSeq: 1 OPTIONS.
Server: OpenSIPS (2.1.2 (x86_64/linux)).
Content-Length: 0.
.




Server 10.0.0.4 gives:




root@front-1:/etc/opensips# ngrep -d eth0 -t -W byline "$1" port 5060 -q
interface: eth0 (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 -> 10.0.0.4:5060
OPTIONS [hidden email] SIP/2.0.
Via: SIP/2.0/UDP 10.0.0.5:47413;branch=z9hG4bK.3fc50b66;rport;alias.
From: [hidden email].
To: [hidden email].
Call-ID: [hidden email].
CSeq: 1 OPTIONS.
Contact: 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 -> 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: [hidden email].
To: [hidden email];tag=61890dad1e908c702027bf054a266115.c3bd.
Call-ID: [hidden email].
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
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users




Haute École de Bruxelles


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: sipsak and sip_trace module

alain BIEUZENT
In reply to this post by Francjos
Hi,

Add this lines before load_balance test :

if (is_method("OPTIONS"))
        {
        sl_send_reply("200", "OK");
        exit;
        }


Regards




Le 10/05/2016 16:37, « Francjos » <[hidden email] au nom de [hidden email]> a écrit :

>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@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 -> 10.0.0.4:5060
>OPTIONS sip:opensips@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@10.0.0.5:47413;tag=4c5c78b9.
>To: sip:opensips@10.0.0.4.
>Call-ID: 1281128633@10.0.0.5.
>CSeq: 1 OPTIONS.
>Contact: 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 -> 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@10.0.0.5:47413;tag=4c5c78b9.
>To: sip:opensips@10.0.0.4;tag=61890dad1e908c702027bf054a266115.c3bd.
>Call-ID: 1281128633@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@front-1:/etc/opensips# ngrep -d eth0 -t -W byline "$1" port 5060 -q
>interface: eth0 (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 -> 10.0.0.4:5060
>OPTIONS sip:opensips@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@10.0.0.5:47413;tag=4c5c78b9.
>To: sip:opensips@10.0.0.4.
>Call-ID: 1281128633@10.0.0.5.
>CSeq: 1 OPTIONS.
>Contact: 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 -> 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@10.0.0.5:47413;tag=4c5c78b9.
>To: sip:opensips@10.0.0.4;tag=61890dad1e908c702027bf054a266115.c3bd.
>Call-ID: 1281128633@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
>[hidden email]
>http://lists.opensips.org/cgi-bin/mailman/listinfo/users


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users