date:20160413

Re: [OpenSIPS-Users] Rely forbidden

2016-04-13 Thread SamyGo

Hi,
So it seems that the RURI contains a $rd (request-domain) which is not
recognizable at your opensips and hence it says I won't relay the call from
one external domain to another external domain.

In simple words, how come that there is req-domain "localhost" is the RURI
for a call coming from Provider destined to your OpenSIPS ? Apparently the
incoming RURI-user part is also 'opensips'. This all seems odd specially
when you mentioned you called your DID  !!

Can you please explain your provider side setup , is that a dummy setup or
a real provider? Also, paste the complete call trace, you can make
sure of sngrep
by irontec  

Regards,
Sammy

On Wed, Apr 13, 2016 at 10:04 AM, Francjos <35...@heb.be> wrote:

> I've configured Opensips to register to a sip provider and acts as
> loadbalancer.
> When i call my number (that i got from my provider),i have the following(i
> try to capture packets using tshark):
> Capturing on 'eth0'
> -40.640830 91.X.X.X -> 10.Y.Y.Y  SIP/SDP 1096 Requests: INVITE
> sip:opensips@localhost:5060;transport=udp
> - 50.641021   10.Y.Y.Y  ->  91.X.X.X   SIP/SDP 452 Status : 403 Rely
> forbidden
> Where "Rely forbidden" is related to this piece of code in opensips.cfg
>
> if(!uri==myself){
> send_relpy("403", "Relay forbidden");
> exit;
> }
>
> Can you help me to understand this and how i can correct this error?
> Thank you.
>
>
>
> --
> View this message in context:
> http://opensips-open-sip-server.1449251.n2.nabble.com/Rely-forbidden-tp7602608.html
> Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Rely forbidden

2016-04-13 Thread Francjos

I've configured Opensips to register to a sip provider and acts as
loadbalancer.
When i call my number (that i got from my provider),i have the following(i
try to capture packets using tshark):
Capturing on 'eth0'
-40.640830 91.X.X.X -> 10.Y.Y.Y  SIP/SDP 1096 Requests: INVITE
sip:opensips@localhost:5060;transport=udp
- 50.641021   10.Y.Y.Y  ->  91.X.X.X   SIP/SDP 452 Status : 403 Rely
forbidden
Where "Rely forbidden" is related to this piece of code in opensips.cfg

if(!uri==myself){
send_relpy("403", "Relay forbidden");
exit;
}

Can you help me to understand this and how i can correct this error?
Thank you.



--
View this message in context: 
http://opensips-open-sip-server.1449251.n2.nabble.com/Rely-forbidden-tp7602608.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Sip trace module .

2016-04-13 Thread Ben Bliss


Sasmita,

If i'm honest, its impossible to outline what to do here. The best thing 
I can do is try to explain how the software functions, and then you can 
fill in the gaps.


I'll try and break it down as much as possible.

You have 3 main elements.

1. Capturing + sending the SIP information - Trace node
2. Analysing and storing SIP information - Capture node
3. Viewing SIP information - HOMER

So, as far as I am aware, you have already configured siptrace within 
OpenSIPs. This does the capturing and sending of the SIP information. 
What you capture, is up to you. We, by design, wanted to capture 
everything, so we have a rule at the start of our Opensips configuration 
to capture the SIP packets, no matter what they are or where they are 
from. You configure the destination address and port of where you are 
analysing the data within the module options. See this 
for more 
information.


Usually, your trace node will be your proxy, or where you are gathering 
your SIP data, although this isn't always the case (you could mirror 
your SIP traffic to a separate trace node, for example). This then sends 
the data to your capture node. Once again, this can be setup as a 
separate instance, receiving the information from the trace node, 
processing it, and then storing it. In our case, we implemented HOMER on 
the same physical box as the capture node. As I am more familiar with 
Kamailio, I used kamailio as the capture node software (which is 
included in the manual installation instructions here.) 



The capture node is there to receive the SIP traffic, isolate what it 
is, and then insert it into an appropriate MySQL table. This database 
information is then read by the HOMER front end. Once again, you can 
install HOMER wherever you like, as long as it can access the database 
you are storing the data which is being captured by the capture node. It 
is, after all, just a web gui, so just needs to be installed on a box 
running apache/nginx. Once again, all the installation instructions are 
on the sipcapture github page here. 



As I said, all the instructions you need are on the github page. It took 
me a few attempts, but the instructions do work, so i would advise 
carefully reading through these, and then follow the instructions 
accordingly.


Kind Regards,

-
Ben Bliss
Network Systems Administrator
Entanet International Ltd
T: 0333 101 9229
F: 0333 101 0601
E: supp...@enta.net
W: http://www.enta.net
W: http://opinion.enta.net

This e-mail and any attachments transmitted with it, including replies and
forwarded copies subsequently transmitted, contains information which may be
confidential and which may also be legally privileged. The content of this
e-mail is for the exclusive use of the individual(s) or entity named above, if
you are not the intended recipient, please note that any form of distribution,
copying or use of this e-mail or the information in it is strictly prohibited
and may be unlawful. If you have received this e-mail in error please reply to
the sender at Entanet International Ltd and then delete the e-mail immediately.
Any views or opinions presented are solely those of the author, and may not
necessarily represent those of Entanet International Ltd. Entanet international
Ltd is registered in England and Wales, registered no 3274237, and its
registered office is Stafford Park 6, Telford, Shropshire, TF3 3AT. registered
VAT number GB 184 5136 01.

On 13/04/2016 11:55 AM, Sasmita Panda wrote:
First I am trying to integrate with mysql only . If it will work for 
me as I want then I will explore with mongodb .


Before that , I am facing lots of problem to install this yet .

Can anyone provide me simple installation and configuration steps for 
homer in linux machine  ?


*/Thanks & Regards/*
/Sasmita Panda/
/Network Testing and Software Engineer/
/3CLogic , ph:07827611765/

On Mon, Apr 11, 2016 at 8:25 PM, Ben Bliss > wrote:


Hi,

Alas, we use MySQL, so no, i can't.

Apologies :)

Kind Regards,

-
Ben Bliss
Network Systems Administrator
Entanet International Ltd

On 11/04/2016 3:32 PM, Aqs Younas wrote:

Can you provide me the snippet how you configured the sip trace
module with  mongodb?

On 11 April 2016 at 19:01, Ben Bliss > wrote:

Sasmita,

HOMER is an open source web GUI, designed for SIP traffic
analysis, and fairly easy to setup and use. It partners with
a SIP capture agent, and a db to store the data you are
gathering.

We use it here, and its fantastically useful.

URL - http://sipcapture.org/

Kind Regards,

-
Ben Bliss

Re: [OpenSIPS-Users] Sip trace module .

2016-04-13 Thread Sasmita Panda

First I am trying to integrate with mysql only . If it will work for me as
I want then I will explore with mongodb .

Before that , I am facing lots of problem to install this yet .

Can anyone provide me simple installation and configuration steps for homer
in linux machine  ?

*Thanks & Regards*
*Sasmita Panda*
*Network Testing and Software Engineer*
*3CLogic , ph:07827611765*

On Mon, Apr 11, 2016 at 8:25 PM, Ben Bliss  wrote:

> Hi,
>
> Alas, we use MySQL, so no, i can't.
>
> Apologies :)
>
> Kind Regards,
>
> -
> Ben Bliss
> Network Systems Administrator
> Entanet International Ltd
>
> On 11/04/2016 3:32 PM, Aqs Younas wrote:
>
> Can you provide me the snippet how you configured the sip trace module
> with  mongodb?
>
> On 11 April 2016 at 19:01, Ben Bliss  wrote:
>
>> Sasmita,
>>
>> HOMER is an open source web GUI, designed for SIP traffic analysis, and
>> fairly easy to setup and use. It partners with a SIP capture agent, and a
>> db to store the data you are gathering.
>>
>> We use it here, and its fantastically useful.
>>
>> URL - http://sipcapture.org/
>>
>> Kind Regards,
>>
>> -
>> Ben Bliss
>> Network Systems Administrator
>> Entanet International Ltd
>>
>> On 11/04/2016 2:07 PM, Sasmita Panda wrote:
>>
>> Hi All ,
>>
>>  I wanted to use siptrace module of opensips and i wanted to
>> extend this feature and save the logs in mongodb . Which is done inby me .
>>
>>Now I wanted to show the data in flow diagram format .
>>
>> Is there any opensource  tool anybody have ever used to do so please le
>> me know .
>>
>> Is there any intermediat step I should do to achive my requirment
>> ,anybody can suggest something .
>>
>> All type of suggestion are welcome . Thank you in advance .
>>
>>
>> *Thanks & Regards*
>> *Sasmita Panda*
>> *Network Testing and Software Engineer*
>> *3CLogic , ph:07827611765*
>>
>>
>> ___
>> Users mailing 
>> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>
>
> ___
> Users mailing 
> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSips as an inbound loadbalancer and outbound proxy - issue with routing BYES

2016-04-13 Thread Francjos

Thank you Younas
I sent an invitation on skype,  but i had two persons with same ID, one Aqs
Younas and another aqs younas. Let's me know when you get the invitation.



--
View this message in context: 
http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSips-as-an-inbound-loadbalancer-and-outbound-proxy-issue-with-routing-BYES-tp6984017p7602605.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] SIPTRACE module behavior in 2.2

2016-04-13 Thread Dragomir Haralambiev

I have same massege in my log.
On Apr 13, 2016 1:30 AM, "Yuri Ritvin"  wrote:

> It looks like some information is missing in the SIPTRACE module
> documentation for OpenSIPS 2.2, or apparently it bears a bug. With the
> given example of the configuration the log file displays these messages:
> ERROR:siptrace:save_siptrace: invalid trace info
> ERROR:siptrace:trace_msg_out: failed to save siptrace
>
> And this is the config snippet:
>
>  SIPTRACE module
> loadmodule "siptrace.so"
> modparam("siptrace", "trace_id",
> "[tid]uri=mysql://opensips:opensipsrw@dbserver/opensips;table=sip_trace;")
> modparam("siptrace", "trace_on", 1)
>
> 
>
> if (method==INVITE && !has_totag()) {
> $var(user)="os...@thisnetwork.com";
> $var(trace_id) = "tid";
> sip_trace("$var(trace_id)", "d", "$var(user)");
> }
>
>
> Then at some particular scenario SIPTRACE module crashes the OpenSIPS 2.2
> application:
> #0  save_siptrace (info=0x7f6878bf6b58, msg=,
> vals=0x7f68722bcf80, keys=0x7f68722bd180) at siptrace.c:878
> hash = 
> it = 
> #1  0x7f68720b5415 in trace_onreply_out (t=,
> type=, ps=0x7fff0548a820) at siptrace.c:1982
> faked = 
> fromip_buff = "udp1XX.2X.XXX.185", '\000' 
> toip_buff = "udp1XX.2X.XXX.78", '\000' 
> msg = 0x7f6878c00740
> to_ip = {af = 2, len = 4, u = {addrl = {1310254956, 0}, addr32 =
> {1310254956, 0, 0, 0}, addr16 = {59244, 19992, 0, 0, 0, 0, 0, 0}, addr =
> "l\347\030N", '\000' }}
> len = 3
> statusbuf = "408\000\001\000\000"
> sbuf = 
> dst = 
> __FUNCTION__ = "trace_onreply_out"
> #2  0x7f68748789a1 in run_trans_callbacks (type=128,
> trans=0x7f6878bfecc8, req=, rpl=,
> code=) at t_hooks.c:209
> params = {req = 0x7f6878c00740, rpl = 0x, code =
> 408, param = 0x7f6878bfeb28, extra1 = 0x7fff0548a9a0, extra2 =
> 0x7f6878bfede0}
> cbp = 0x7f6878bfeb18
> backup = 0x7816c0
> trans_backup = 0x7f6878bfecc8
> __FUNCTION__ = "run_trans_callbacks"
> #3  0x7f6874878b00 in run_trans_callbacks_locked (type= optimized out>, trans=0x7f6878bfecc8, req=, rpl= optimized out>, code=)
> at t_hooks.c:262
> No locals.
> #4  0x7f68748851b1 in relay_reply (t=0x7f6878bfecc8, p_msg= optimized out>, branch=, msg_status= out>, cancel_bitmap=0x7fff0548aa7c)
> at t_reply.c:1255
> relay = 0
> save_clone = 0
> buf = 0x7f6888aa78a8 "SIP/2.0 408 Request Timeout\r\nVia:
> SIP/2.0/UDP
> 1XX.2X.XXX.78:8408;received=1XX.2X.XXX.78;branch=z9hG4bK-524287-1---af6608797b55630d;rport=8408\r\nTo:
> ;tag=3b8d"...
> res_len = 412
> relayed_code = 408
> relayed_msg = 0x
> bm = {to_tag_val = {
> s = 0x7f6888aa796c
> "3b8d6d10a54b0752c937c18d274bef37-402e\r\nFrom: \"TestingSubscriber1001\"<
> sip:testingsubscriber1...@sip.thisnetwork.com>;tag=735c442d\r\nCall-ID:
> PKSLf7Smdwyk-hULVsGkKg..\r\nCSeq: 2 INVITE\r\nServer: SBC-185\r\nConte"...,
> len = 37}}
> totag_retr = 0
> reply_status = RPS_COMPLETED
> uas_rb = 0x7f6878bfedc8
> cb_s = {
>   s = 0x7f6888aa78a8 "SIP/2.0 408 Request Timeout\r\nVia:
> SIP/2.0/UDP
> 1XX.2X.XXX.78:8408;received=1XX.2X.XXX.78;branch=z9hG4bK-524287-1---af6608797b55630d;rport=8408\r\nTo:
> ;tag=3b8d"..., len = 412}
> text = {s = 0x50daf3 "Request Timeout", len = 15}
> __FUNCTION__ = "relay_reply"
> #5  0x7f68746e in fake_reply (ticks=70, set=)
> at timer.c:260
> cancel_bitmap = 0
> do_cancel_branch = 
> reply_status = 
> #6  final_response_handler (ticks=70, set=) at
> timer.c:391
> old_ctx = 0x0
> my_ctx = 0x7f6888aa7f08
> r_buf = 0x7f6878bfeea0
> ---Type  to continue, or q  to quit---
> t = 0x7f6878bfecc8
> #7  timer_routine (ticks=70, set=) at timer.c:1066
> tl = 0x7f6878bfef18
> tmp_tl = 0x0
> id = 
> __FUNCTION__ = "timer_routine"
> #8  0x0047e28b in handle_timer_job () at timer.c:632
> t = 0x7f687890d760
> l = 
> __FUNCTION__ = "handle_timer_job"
> #9  0x004ed64d in handle_io (fm=0x7f6888a9c388, idx=1,
> event_type=) at net/net_tcp_proc.c:117
> ret = 0
> n = 
> con = 
> s = 
> rw = 
> resp = 
> response = {140733282036968, 140086962256117}
> __FUNCTION__ = "handle_io"
> #10 0x004ee140 in io_wait_loop_epoll (repeat=0, t=2, h= optimized out>) at ./io_wait_loop.h:221
> n = 1
> r = 1
> e = 0x7f6888a9c388
> ret = 1
> #11 0x004ef407 in tcp_worker_proc (unix_sock= out>) at net/net_tcp_proc.c:312
> __FUNCTION__ = "tcp_worker_proc"
> #12 0x004eb31d in

Re: [OpenSIPS-Users] Rely forbidden

[OpenSIPS-Users] Rely forbidden

Re: [OpenSIPS-Users] Sip trace module .

Re: [OpenSIPS-Users] Sip trace module .

Re: [OpenSIPS-Users] OpenSips as an inbound loadbalancer and outbound proxy - issue with routing BYES

Re: [OpenSIPS-Users] SIPTRACE module behavior in 2.2

6 matches

Site Navigation

Mail list logo

Footer information