Re: [OpenSIPS-Users] Question regarding b2b_bridge function

[Ping Han]

Hi Bogdan,

Yes, that is exactly what I am trying to do.

Regards,
Ping

On Tue, Jun 7, 2016 at 8:34 PM, Bogdan-Andrei Iancu 
wrote:

> Hi Ping,
>
> So you need the B2B Logic ID only when you create the B2B session, in
> order to place it in the first outgoing INVITE (as extra hdr), right ?
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 07.06.2016 04:59, Ping Han wrote:
>
> Thanks, Bogdan,
>
> What I am trying to do is to get the b2b logic ID and deliver to the next
> hop via a custom SIP header.
>
> I am using the b2b_init_request("top hiding") and it looks like the only
> place that I can add a custom header is in the local_route.
>
> So in the script I need the b2b logic ID after running b2b_init_request("top
> hiding") but before the new INVITE is sent to the B party as shown below.
>
> I am not sure how I can do that.
> [image: Inline image 2]
>
> Thanks,
> Ping
>
> On Tue, Jun 7, 2016 at 12:07 AM, Bogdan-Andrei Iancu <
> bog...@opensips.org> wrote:
>
>> Hi Ping,
>>
>> My bad - in Call-ID and TO tag you have the B2B _entity_ ID, while you
>> need the B2B _logic_ ID .which is not part of the signaling at all .
>>
>> Now, in script, where do you need the b2b logic ID ? after creating the
>> B2B session (after b2b_init() ) ? Or ?
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>>
>> On 06.06.2016 11:46, Ping Han wrote:
>>
>> Thanks, Bogdan,
>>
>> I have done a few testing. It seems only the value of the param works for
>> this function. However, it does not look like the callid and the to-tag.
>> Is it possible to get the param value in the Opensips config?
>>
>> Please see the test results below.
>>
>> -
>> [root@opensips-02 ~]# opensipsctl fifo b2be_list
>> dlg:: 37 param=237.0 state=5 last_invite_cseq=1 last_method=0
>> last_reply_code=200 db_flag=2
>> ruri:: 
>> sip:2401012350@10.216.235.38:5060
>> callid:: NjEyZWEyOTEwZmVlZDIzOTViMTc3YjJiMmJmY2RjODI.
>> from:: "Tropo test" uri=sip:2401012350@10.216.235.115:5060
>> tag=1e53cf61
>> to:: "2401012350" uri= 
>> sip:2401012350@10.216.235.115:5060 tag=B2B.297.37
>> cseq::  caller=1 callee=1
>> route_set::
>>  
>> caller=,
>> contact::  caller= 
>> sip:2401012350@10.203.1.196:22238 callee=sip:10.216.235.72:5060
>> send_sock:: 10.216.235.72
>> dlg:: 6715348 param=237.0 state=5 last_invite_cseq=2 last_method=4
>> db_flag=2
>> callid:: B2B.237.6715348
>> from:: "Tropo test" uri=sip:2401012350@10.216.235.115:5060
>> tag=44623c403b25fd7905bfa7a7325b2b8f
>> to::  uri= 
>> sip:dialog@10.216.235.38:5060 tag=40711690
>> cseq::  caller=2 callee=1
>> contact::  caller=sip:10.216.235.72:5060 callee=sip:
>> 10.216.235.38:5060
>> send_sock:: 10.216.235.72
>> LEGS::
>> leg:: 0 tag=40711690 cseq=2 contact=sip:
>> 10.216.235.38:5060
>>
>> [root@opensips-02 ~]# opensipsctl fifo b2b_bridge 237.6715348
>> sip:123@10.203.1.196  (this is the callid with
>> out the "B2B" prefix)
>> 500 command 'b2b_bridge' failed
>>
>> [root@opensips-02 ~]# opensipsctl fifo b2b_bridge 297.37
>> sip:123@10.203.1.196  (this is the To-tag)
>> 500 command 'b2b_bridge' failed
>>
>> [root@opensips-02 ~]# opensipsctl fifo b2b_bridge 237.0
>> sip:123@10.203.1.196 (this is the value of param,
>> only this works)
>>
>> -
>>
>> Regards,
>> Ping
>>
>>
>> On Fri, Jun 3, 2016 at 6:54 PM, Bogdan-Andrei Iancu <
>> bog...@opensips.org> wrote:
>>
>>> Hi Ping,
>>>
>>> b2b_bridge_request() is a script function:
>>>
>>> http://www.opensips.org/html/docs/modules/2.1.x/b2b_logic.html#id294094
>>>
>>> I pointed to this function as you mentioned (on my question) that you
>>> want to do the bridging from script level.
>>>
>>> Indeed, the equivalent MI function is b2b_bridge:
>>>
>>> http://www.opensips.org/html/docs/modules/2.1.x/b2b_logic.html#id294210
>>>
>>> If you want to get that "1020.30", you can get it from Call-ID or To
>>> tag, where you have B2B.1020.30 (so you have to strip that B2B prefix).
>>>
>>> Regards,
>>>
>>> Bogdan-Andrei Iancu
>>> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>>>
>>> On 03.06.2016 06:27, Ping Han wrote:
>>>
>>> Thanks, Bogdan,
>>>
>>> It seems the function you mentioned is the internal function  "1.4.2
>>> b2b_bridge_request(b2bl_key,entity_no)".
>>>
>>> Actually the function that I am trying to use is the "b2b_bridge"
>>> (Exported MI Functions). It is defined as below
>>> 

Re: [OpenSIPS-Users] IS_MYSELF() always uses 5060 if received port is 0

[Bogdan-Andrei Iancu]

Hi,

The patch is part of the latest release on 1.11 branch, the 1.11.7 version.
Here is the commits for that:
https://github.com/OpenSIPS/opensips/commit/f91441d43e814d06ebf325e637206be42879
https://github.com/OpenSIPS/opensips/commit/d39cfb73ed01b349c235949a16ccc5b559003a81

Apply them both !

Or simply use 1.11.7

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 07.06.2016 16:10, Ravitez Ravi wrote:

Hello Bogdan,
Good Morning,
I missed to updated that we are using 1.11.5 and 
not sure if the patch was targeted for that.
can you please share a patch for "OpenSIPS 
(1.11.5-tls (x86_64/linux))"

Thank you for the help.

Regards,
Ravitez.D

On Tue, May 17, 2016 at 11:51 AM, Bogdan-Andrei Iancu 
> wrote:


Hi,

That is a great catch, thank you for finding and reporting this.
See the attach patch that should address the problem. Could you
please give it a try to see if it really solves the problem ?

Best Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 13.05.2016 22:30, Ravitez Ravi wrote:

Hi All,
Good Day,
Here's the problem i'm facing and would be a great help
if you could comment.
Thank you.

is_myself() does not check for SIPS port if connection type is TLS
*Configuration :*
- Opensips V1.11.5 running in secure mode on port 5061
- Avaya trying to communicate with Opensips server.
- Opensips server ip 192.168.1.11
- Avaya ip : 192.168.1.20


*Steps :*
- Avaya sends INVITE to Opensips with route header
Route: 
- Opensips tries to process it but fails.
*DBG:rr:is_preloaded: is_preloaded: Yes*
*DBG:core:grep_sock_info: checking if host==us: 14==14 &&
 [192.168.1.11] == [192.168.1.11]*
*DBG:core:grep_sock_info: checking if port 5061 matches port 5060*
*DBG:core:check_self: host != me*
*DBG:rr:after_loose: Topmost URI is NOT myself*



SIP/2.0 403 Preload Route denied
*Code Snippet :*
/*
 * Check if URI is myself
 */
#ifdef ENABLE_USER_CHECK
static inline int is_myself(str *_user, str* _host, unsigned
short _port)
#else
static inline int is_myself(str* _host, unsigned short _port)
#endif
{
int ret;

*ret = check_self(_host, _port ? _port : SIP_PORT, 0);/* match
all protos*/*
if (ret < 0) return 0;

*Should is_myself() check for connection type and then decide to
either use SIP or SIPS port.*
*
*
*
*
*
*
Regards,
Ravitez.D


___
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] Continuous "WARNING:core:timer_ticker: timer task already scheduled" messages in log

[Rodrigo Pimenta Carvalho]

Hi Steve.


I had exactly this same problem!

I used to see that log very frequently.

So, I changed a configuration in my opensips.cfg file to be:


modparam("usrloc", "db_mode", 2)
modparam("usrloc", "timer_interval",3)


Then, the problem almost disappeared. That is, nowadays I see this log seldom.


Tell me about the solution for your case, when you have fixed it, please!

I also gonna to consider the last hint from Bogdan and change my TM parameter.


Best regards!


RODRIGO PIMENTA CARVALHO
Inatel Competence Center
Software
Ph: +55 35 3471 9200 RAMAL 979



De: users-boun...@lists.opensips.org  em nome 
de Steve Woolley 
Enviado: segunda-feira, 6 de junho de 2016 22:21
Para: users@lists.opensips.org
Assunto: [OpenSIPS-Users] Continuous "WARNING:core:timer_ticker: timer task 
 already scheduled" messages in log

Running opensips on a Raspberry Pi.  At some point after starting opensips 
(sometimes immediately, sometimes after quite a bit of time), the following 
message fills the log - once a second - continuously.

...
Jun  7 01:10:41 pi1 /usr/local/sbin/opensips[22396]: WARNING:core:timer_ticker: 
timer task  already scheduled for 7182080 ms (now 8258580 ms), it may 
overlap..
Jun  7 01:10:42 pi1 /usr/local/sbin/opensips[22396]: WARNING:core:timer_ticker: 
timer task  already scheduled for 7182080 ms (now 8259570 ms), it may 
overlap..
Jun  7 01:10:43 pi1 /usr/local/sbin/opensips[22396]: WARNING:core:timer_ticker: 
timer task  already scheduled for 7182080 ms (now 8260560 ms), it may 
overlap..
Jun  7 01:10:44 pi1 /usr/local/sbin/opensips[22396]: WARNING:core:timer_ticker: 
timer task  already scheduled for 7182080 ms (now 8261560 ms), it may 
overlap..
Jun  7 01:10:45 pi1 /usr/local/sbin/opensips[22396]: WARNING:core:timer_ticker: 
timer task  already scheduled for 7182080 ms (now 8262550 ms), it may 
overlap..
Jun  7 01:10:46 pi1 /usr/local/sbin/opensips[22396]: WARNING:core:timer_ticker: 
timer task  already scheduled for 7182080 ms (now 8263550 ms), it may 
overlap..
Jun  7 01:10:47 pi1 /usr/local/sbin/opensips[22396]: WARNING:core:timer_ticker: 
timer task  already scheduled for 7182080 ms (now 8264540 ms), it may 
overlap..
Jun  7 01:10:48 pi1 /usr/local/sbin/opensips[22396]: WARNING:core:timer_ticker: 
timer task  already scheduled for 7182080 ms (now 8265530 ms), it may 
overlap..
Jun  7 01:10:49 pi1 /usr/local/sbin/opensips[22396]: WARNING:core:timer_ticker: 
timer task  already scheduled for 7182080 ms (now 8266530 ms), it may 
overlap..
Jun  7 01:10:50 pi1 /usr/local/sbin/opensips[22396]: WARNING:core:timer_ticker: 
timer task  already scheduled for 7182080 ms (now 8267520 ms), it may 
overlap..

root@pi1:~# opensips -V
version: opensips 2.2.0 (arm6/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, QM_MALLOC, 
DBG_MALLOC, USE_PTHREAD_MUTEX
MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
git revision: 0e1cea7
main.c compiled on 21:56:59 Jun  3 2016 with gcc 4.9.2

Anyone experiencing the same?


--
Steve Woolley
steve.wool...@me.com



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

Re: [OpenSIPS-Users] Opensips -1.11 crash with mongodb replica set .

[Sasmita Panda]

Thank you so much . It will be helpful for me .

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

On Tue, Jun 7, 2016 at 4:41 PM, Liviu Chircu  wrote:

> To avoid those kind of problems, I would recommend putting one "mongos"
> instance for each OpenSIPS machine, on the same box. This way, not only do
> you avoid problems with the mongos machine going down, but you'll speed up
> query times as well, making your OpenSIPS workers more responsive!
>
> Liviu Chircu
> OpenSIPS Developerhttp://www.opensips-solutions.com
>
> On 07.06.2016 13:20, Sasmita Panda wrote:
>
> Hi Liviu ,
>
>  I just have one question .  I have implemented opensips with mongodb
> shard cluster . I have one replica set with three member . I have three
> config server for each and mongos service running .
>
>  What I wanted to know is , the server in which my mongos service is
> running , If that machine is get down what will happen ?
> I need to monitor that machine so that it wont go down ? Is this show ?
>
> *Thanks & Regards*
> *Sasmita Panda*
> *Network Testing and Software Engineer*
> *3CLogic , ph:07827611765*
>
> On Mon, Jun 6, 2016 at 4:41 PM, Liviu Chircu  wrote:
>
>> Thank you, Sasmita! Will reply here as soon as there is progress on the
>> matter.
>>
>> Liviu Chircu
>> OpenSIPS Developerhttp://www.opensips-solutions.com
>>
>> On 06.06.2016 13:55, Sasmita Panda wrote:
>>
>> Hi ,
>>
>>  I have created an issue with detailed steps . Bellow is the issue ID .
>> Let me know if the issue will get fixed .
>>
>>   https://github.com/OpenSIPS/opensips/issues/895
>>
>> Thanks
>>
>> *Thanks & Regards*
>> *Sasmita Panda*
>> *Network Testing and Software Engineer*
>> *3CLogic , ph:07827611765*
>>
>> On Mon, Jun 6, 2016 at 3:32 PM, Sasmita Panda < 
>> spa...@3clogic.com> wrote:
>>
>>> Thank you so much for the information . Let me try to deploy with mongos
>>> server .
>>>
>>> I will post the detailed steps for opensips crash as soon as I will be
>>> free .
>>>
>>> *Thanks & Regards*
>>> *Sasmita Panda*
>>> *Network Testing and Software Engineer*
>>> *3CLogic , ph:07827611765*
>>>
>>> On Mon, Jun 6, 2016 at 2:14 PM, Liviu Chircu < 
>>> li...@opensips.org> wrote:
>>>
 Hi Sasmita!

 We have some plans to do some more testing on the module, including
 your "connect directly to replica set" usage case, and  also bringing it up
 to date with the latest mongo driver. However, it is hard to give you an
 estimation for when this work will start.

 Currently, the fastest way to fix your problems is for you to set up a
 "mongos" instance, along with 3 config server instances (these are needed
 by mongos, and ensure proper write consistency), and configure
 "cachedb_mongodb" to use this new "mongos" node.

 A mongos instance is aware of all the replica sets (aka "shards"). In
 your case, it will initially shard the keys to your single replica set -
 thus, it will hold 100% of the data. As your data set grows, you may
 partition it over to additional replica sets, which you can configure into
 mongos without modifying anything on the OpenSIPS side. This way, failover
 within a replica set will also happen transparently, again, without
 impacting OpenSIPS at all.

 PS: if you have a way to 100% reproduce a crash, please open a GH
 ticket describing the steps, and we'll go from there! [1]

 [1]: https://github.com/OpenSIPS/opensips/issues

 Liviu Chircu
 OpenSIPS Developerhttp://www.opensips-solutions.com

 On 06.06.2016 11:23, Sasmita Panda wrote:

 Hi All ,

I am using opesips-1.11 with mongodb replica set . I have 3
 members in the replica set , promary , secondary and arbitrary .

   Problem 1 :  Sometime , If primay is not rechable , the secondary
 becomes primary , But opensips loss connection from mongodb . Its wont put
 any data in the data base . My call goes on but their is not data in the
 mongodb database .

 Problme 2: If the primay machine is down then secondary becomes
 primary within some millisecond time  , but  opensips crashes giving bellow
 error

   ERROR:cachedb_mongodb:mongo_con_get: Failed to run query. Err =
 6, 0 , 0
  CRITICAL:core:receive_fd: EOF on 10
  INFO:core:handle_sigs: child process 5278 exited by a signal 11
  INFO:core:handle_sigs: core was generated
  INFO:core:handle_sigs: terminating due to SIGCHLD
  INFO:core:sig_usr: signal 15 received
  INFO:core:sig_usr: signal 15 received
  INFO:core:sig_usr: signal 15 received
  INFO:core:sig_usr: signal 15 received
  INFO:core:sig_usr: signal 15 received
  INFO:core:sig_usr: signal 15 received
  INFO:core:sig_usr: signal 15 received
  INFO:core:sig_usr: signal 15 received
  

[OpenSIPS-Users] Available OpenSIPS releases ad their lifetime

[Bogdan-Andrei Iancu]

Hello,

Following the release of OpenSIPS 2.2.0, here is the current status of 
the available (maintained) releases and the planned expiration date.



OpenSIPS 1.11 LTS - to be maintained until 7th of May 2017

OpenSIPS 2.1  - to be maintained until 7th of November 2017

OpenSIPS 2.2 LTS  - to be maintained until 27th of May 2019


Best regards,

--
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com


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

Re: [OpenSIPS-Users] Register with TO Tag

[Bogdan-Andrei Iancu]

REGISTER and INVITE requests should be handled in different ways, so 
split your scripting per methods.


In regards, to MF, better do the validation first, to be sure that 
whatever you do later, at least you have a valid SIP msg.


Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 07.06.2016 13:53, John Nash wrote:

OK that means I should handle Register before In-dialog processing block?

I also have one more doubt function mf_process_maxfwd_header should it 
be used before sipmsg_validate or after?...Currently 
mf_process_maxfwd_header  is being called in my script first but in 
some cases with malformed packets its not even able to read max fwd 
header.


On Tue, Jun 7, 2016 at 4:11 PM, Bogdan-Andrei Iancu 
> wrote:


Hi John,

Assuming you do not do REGISTER relay (but you act as a
registrar), you should handle the REGISTER requests (with or
without to-tag) in the same way. IF they have a Route hdr , it may
be because they do pre-loaded route (the Route points to your SIP
server) to be sure the REGISTER gets to the registrar server.

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 07.06.2016 10:56, John Nash wrote:

I am dealing with In-dialog requests using


--
if (has_totag() && (is_domain_local("$rd") || $Ri==
"127.0.0.1") && is_method("INVITE|ACK|BYE|UPDATE"))
{
# sequential request within a dialog should
# take the path determined by record-routing
if (topology_hiding_match())
-

-

at the top of my script. After that I process initial requests,
but I see some REGISTER messages with TO-Tag and "Route" header
and they are being discarded by my script because Initial request
cannot have Route header.

Do i also need to pass REGISTER messages also through same
block?...or i need to call loose_route after has_to_tag check.




___
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] Register with TO Tag

[John Nash]

OK that means I should handle Register before In-dialog processing block?

I also have one more doubt function mf_process_maxfwd_header should it be
used before sipmsg_validate or after?...Currently mf_process_maxfwd_header
 is being called in my script first but in some cases with malformed
packets its not even able to read max fwd header.

On Tue, Jun 7, 2016 at 4:11 PM, Bogdan-Andrei Iancu 
wrote:

> Hi John,
>
> Assuming you do not do REGISTER relay (but you act as a registrar), you
> should handle the REGISTER requests (with or without to-tag) in the same
> way. IF they have a Route hdr , it may be because they do pre-loaded route
> (the Route points to your SIP server) to be sure the REGISTER gets to the
> registrar server.
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 07.06.2016 10:56, John Nash wrote:
>
> I am dealing with In-dialog requests using
>
>
> --
> if (has_totag() && (is_domain_local("$rd") || $Ri== "127.0.0.1") &&
> is_method("INVITE|ACK|BYE|UPDATE"))
> {
> # sequential request within a dialog should
> # take the path determined by record-routing
> if (topology_hiding_match())
> -
>
> -
>
> at the top of my script. After that I process initial requests, but I see
> some REGISTER messages with TO-Tag and "Route" header and they are being
> discarded by my script because Initial request cannot have Route header.
>
> Do i also need to pass REGISTER messages also through same block?...or i
> need to call loose_route after has_to_tag check.
>
>
>
>
> ___
> 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

Re: [OpenSIPS-Users] Opensips CP DROUTING GATEWAY enable/disable issue

[Bogdan-Andrei Iancu]

Hi Jeff,

So, FIFO works ok for you, but CP (using xmlrpc fails). Can you make a 
capture of the XMLRPC traffic between CP and OpenSIPS and post it 
somewhere ?


Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 31.05.2016 17:27, Jeff Wilkie wrote:


OpenSIPS Control Panel version 5.0


Jeff Wilkie
Chief Technology Officer
US IP Communications
919.297.1057


/"This e-mail communication and any attachments may contain 
confidential and privileged information and is for use by the 
designated addressee(s) named above only. Any files transmitted with 
it are confidential and intended solely for the use of the individual 
to whom it is addressed. Any views or opinions presented are solely 
those of the author and do not necessarily represent those of USIPCOM, 
LLC. If you are not the intended addressee, you are hereby notified 
that you have received this communication in error and that any use or 
reproduction of this email or its contents is strictly prohibited and 
may be unlawful. If you have received this communication in error, 
please notify us immediately by replying to this message and deleting 
it from your computer. Thank you". /


On Tue, May 31, 2016 at 3:28 AM, Bogdan-Andrei Iancu 
> wrote:


Hi Jeff,

What OpenSIPS Control Panel version are you using ?

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 21.05.2016 00:15, Jeff Wilkie wrote:

OPENSIPS 1.10.x
I have the following set

opensips.cfg

 FIFO Management Interface

loadmodule "mi_fifo.so"

modparam("mi_fifo", "fifo_name", "/tmp/opensips_proxy_fifo")

modparam("mi_fifo", "fifo_mode", 0666)


opensipsctlrc

## path to FIFO file

OSIPS_FIFO="/tmp/opensips_proxy_fifo"


Attempting to disable gateways via the CP gives the following errors:


From DROUTING-Gateway interface:


Error while disabling gateway 2
(the GWID is 2 for the gateway I'm attempting to disable)

From the MI Commands:
Initiating the following command: *dr_gw_status 2 0*
404 GW ID not found

From the DROUTING-Gateway interface I am able to enable the
interface if it is disabled
I'm able to also enable the Gateway from the MI Commands section.

I'm also able to enable and disable the Gateway using opensipsctl
fifo commands

opensipsctl fifo dr_gw_status 2

Enabled:: yes

opensipsctl fifo dr_gw_status 2 0

opensipsctl fifo dr_gw_status 2

Enabled:: no

opensipsctl fifo dr_gw_status 2 1

opensipsctl fifo dr_gw_status 2

Enabled:: yes


Not sure where the problem is but I feel its somewhere in the
syntax of how its delivered.  I'm sure it's something easy I've
overlooked.  Any help on this?

Thanks
Jeff


___
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] Continuous "WARNING:core:timer_ticker: timer task already scheduled" messages in log

[Bogdan-Andrei Iancu]

Hello Steve,

What OpenSIPS tells you is that you the TM timer routine (which gets 
executed once per second) takes longer than 1 second (as execution). 
Probably you have retransmissions or many failure routes to be executed.
You can increase the level of parallelism in TM timer via the 
timer_partition parameter:

http://www.opensips.org/html/docs/modules/2.2.x/tm.html#id294483
Try to set it to 4.

Best regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 07.06.2016 04:21, Steve Woolley wrote:
Running opensips on a Raspberry Pi.  At some point after starting 
opensips (sometimes immediately, sometimes after quite a bit of time), 
the following message fills the log — once a second — continuously.


...
Jun  7 01:10:41 pi1 /usr/local/sbin/opensips[22396]: 
WARNING:core:timer_ticker: timer task  already scheduled for 
7182080 ms (now 8258580 ms), it may overlap..
Jun  7 01:10:42 pi1 /usr/local/sbin/opensips[22396]: 
WARNING:core:timer_ticker: timer task  already scheduled for 
7182080 ms (now 8259570 ms), it may overlap..
Jun  7 01:10:43 pi1 /usr/local/sbin/opensips[22396]: 
WARNING:core:timer_ticker: timer task  already scheduled for 
7182080 ms (now 8260560 ms), it may overlap..
Jun  7 01:10:44 pi1 /usr/local/sbin/opensips[22396]: 
WARNING:core:timer_ticker: timer task  already scheduled for 
7182080 ms (now 8261560 ms), it may overlap..
Jun  7 01:10:45 pi1 /usr/local/sbin/opensips[22396]: 
WARNING:core:timer_ticker: timer task  already scheduled for 
7182080 ms (now 8262550 ms), it may overlap..
Jun  7 01:10:46 pi1 /usr/local/sbin/opensips[22396]: 
WARNING:core:timer_ticker: timer task  already scheduled for 
7182080 ms (now 8263550 ms), it may overlap..
Jun  7 01:10:47 pi1 /usr/local/sbin/opensips[22396]: 
WARNING:core:timer_ticker: timer task  already scheduled for 
7182080 ms (now 8264540 ms), it may overlap..
Jun  7 01:10:48 pi1 /usr/local/sbin/opensips[22396]: 
WARNING:core:timer_ticker: timer task  already scheduled for 
7182080 ms (now 8265530 ms), it may overlap..
Jun  7 01:10:49 pi1 /usr/local/sbin/opensips[22396]: 
WARNING:core:timer_ticker: timer task  already scheduled for 
7182080 ms (now 8266530 ms), it may overlap..
Jun  7 01:10:50 pi1 /usr/local/sbin/opensips[22396]: 
WARNING:core:timer_ticker: timer task  already scheduled for 
7182080 ms (now 8267520 ms), it may overlap..


root@pi1:~# opensips -V
version: opensips 2.2.0 (arm6/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, 
QM_MALLOC, DBG_MALLOC, USE_PTHREAD_MUTEX
MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, 
BUF_SIZE 65535

poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
git revision: 0e1cea7
main.c compiled on 21:56:59 Jun  3 2016 with gcc 4.9.2

Anyone experiencing the same?


--
Steve Woolley
steve.wool...@me.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] Opensips as proxy, config problem on INVITES

[Saioa Perurena]

Hi,

We have only one proxy Opensips (version 1.11) that does all the work
(register's, invite's, tls conection...) on a DMZ behind a firewall.

We want to move that to a new schema, with one Opensips (version 2.1)
as a frontend that handles the tls connections (with a public ip) on
the DMZ, and another Opensips (version 1.11) at the backend (with
private ip), but we are not able to complete the invite signaling
correctly. Register, message, options worked ok, but we have problems
with the invite.
The invite request arrives to the callee, and the OK answers arrives
to the caller, but the caller does not send and ACK to this OK, so the
callee keeps sending OK until it send a BYE because of timeout.

Any idea of where is the problem or what am i doing wrong?? Any advice
will be appreciated!!

I attach the sip_trace log and the Opensips script of the frontend server:

Caller: sip:u1iupzg...@jipubnx2ef.bell.enigmedia.eu
Callee: d27p6ui...@jipubnx2ef.bell.enigmedia.eu
Opensips frontend ip: internal -> 192.168.3.35, external -> 192.168.1.18
Opensips backend ip: internal -> 192.168.2.6





from_ip | from_port | to_ip  | to_port | direction |

content 
   
+---++-+---+---
 192.168.10.109 | 41302 | 192.168.3.35   |5061 | in| INVITE 
sip:d27p6ui...@jipubnx2ef.bell.enigmedia.eu SIP/2.0\r 
|   || |   | Via: 
SIP/2.0/TLS 192.168.200.238:41302;branch=z9hG4bK.5v5fmStat;rport\r 
|   || |   | From: 
;tag=~DvmtD4uF\r 
|   || |   | To: 
sip:d27p6ui...@jipubnx2ef.bell.enigmedia.eu\r
|   || |   | CSeq: 20 
INVITE\r
|   || |   | Call-ID: 
At8pM4Jbgs\r
|   || |   | 
Max-Forwards: 69\r   
|   || |   | Route: 
\r  
|   || |   | Supported: 
outbound\r
|   || |   | Allow: 
INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO, 
UPDATE\r
|   || |   | 
CALLEE-KEY: 123456789123456789\r 
|   || |   | 
Content-Type: application/sdp\r  
|   || |   | 
Content-Length: 538\r
|   || |   | 
LocalDateTime: 2016-05-31T11:14:47 +0200\r   
|   || |   | InstallId: 
0oitm5of4m\r  
|   || |   | Contact: 
;+sip.instance=""\r
|   || |   | 
User-Agent: 0oitm5of4m/EnigmediaAppAnd/2.3.1/bell-sip/1.4.2/3.9.1.E1.0.11\r 
   
|   || |   | \r 
  
|   || |   | v=0\r  
  
|   || |   | 
o=u1iupzg6we 944 1255 IN IP4 192.168.200.238\r   
|   || |   | s=Talk\r   
  
|   || |   | c=IN IP4 
192.168.200.238\r   
|   || |   | t=0 0\r
  
|   || |   | 
a=rtcp-xr:rcvr-rtt=all:1 stat-summary=loss,dup,jitt,TTL voip-metrics\r  
   
|   || |   | m=audio 

Re: [OpenSIPS-Users] Register with TO Tag

[Bogdan-Andrei Iancu]

Hi John,

Assuming you do not do REGISTER relay (but you act as a registrar), you 
should handle the REGISTER requests (with or without to-tag) in the same 
way. IF they have a Route hdr , it may be because they do pre-loaded 
route (the Route points to your SIP server) to be sure the REGISTER gets 
to the registrar server.


Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 07.06.2016 10:56, John Nash wrote:

I am dealing with In-dialog requests using

--
if (has_totag() && (is_domain_local("$rd") || $Ri== "127.0.0.1") 
&& is_method("INVITE|ACK|BYE|UPDATE"))

{
# sequential request within a dialog should
# take the path determined by record-routing
if (topology_hiding_match())
-
-

at the top of my script. After that I process initial requests, but I 
see some REGISTER messages with TO-Tag and "Route" header and they are 
being discarded by my script because Initial request cannot have Route 
header.


Do i also need to pass REGISTER messages also through same block?...or 
i need to call loose_route after has_to_tag check.





___
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 -1.11 crash with mongodb replica set .

[Sasmita Panda]

Hi Liviu ,

 I just have one question .  I have implemented opensips with mongodb
shard cluster . I have one replica set with three member . I have three
config server for each and mongos service running .

 What I wanted to know is , the server in which my mongos service is
running , If that machine is get down what will happen ?
I need to monitor that machine so that it wont go down ? Is this show ?

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

On Mon, Jun 6, 2016 at 4:41 PM, Liviu Chircu  wrote:

> Thank you, Sasmita! Will reply here as soon as there is progress on the
> matter.
>
> Liviu Chircu
> OpenSIPS Developerhttp://www.opensips-solutions.com
>
> On 06.06.2016 13:55, Sasmita Panda wrote:
>
> Hi ,
>
>  I have created an issue with detailed steps . Bellow is the issue ID .
> Let me know if the issue will get fixed .
>
>   https://github.com/OpenSIPS/opensips/issues/895
>
> Thanks
>
> *Thanks & Regards*
> *Sasmita Panda*
> *Network Testing and Software Engineer*
> *3CLogic , ph:07827611765*
>
> On Mon, Jun 6, 2016 at 3:32 PM, Sasmita Panda  wrote:
>
>> Thank you so much for the information . Let me try to deploy with mongos
>> server .
>>
>> I will post the detailed steps for opensips crash as soon as I will be
>> free .
>>
>> *Thanks & Regards*
>> *Sasmita Panda*
>> *Network Testing and Software Engineer*
>> *3CLogic , ph:07827611765*
>>
>> On Mon, Jun 6, 2016 at 2:14 PM, Liviu Chircu < 
>> li...@opensips.org> wrote:
>>
>>> Hi Sasmita!
>>>
>>> We have some plans to do some more testing on the module, including your
>>> "connect directly to replica set" usage case, and  also bringing it up to
>>> date with the latest mongo driver. However, it is hard to give you an
>>> estimation for when this work will start.
>>>
>>> Currently, the fastest way to fix your problems is for you to set up a
>>> "mongos" instance, along with 3 config server instances (these are needed
>>> by mongos, and ensure proper write consistency), and configure
>>> "cachedb_mongodb" to use this new "mongos" node.
>>>
>>> A mongos instance is aware of all the replica sets (aka "shards"). In
>>> your case, it will initially shard the keys to your single replica set -
>>> thus, it will hold 100% of the data. As your data set grows, you may
>>> partition it over to additional replica sets, which you can configure into
>>> mongos without modifying anything on the OpenSIPS side. This way, failover
>>> within a replica set will also happen transparently, again, without
>>> impacting OpenSIPS at all.
>>>
>>> PS: if you have a way to 100% reproduce a crash, please open a GH ticket
>>> describing the steps, and we'll go from there! [1]
>>>
>>> [1]: https://github.com/OpenSIPS/opensips/issues
>>>
>>> Liviu Chircu
>>> OpenSIPS Developerhttp://www.opensips-solutions.com
>>>
>>> On 06.06.2016 11:23, Sasmita Panda wrote:
>>>
>>> Hi All ,
>>>
>>>I am using opesips-1.11 with mongodb replica set . I have 3
>>> members in the replica set , promary , secondary and arbitrary .
>>>
>>>   Problem 1 :  Sometime , If primay is not rechable , the secondary
>>> becomes primary , But opensips loss connection from mongodb . Its wont put
>>> any data in the data base . My call goes on but their is not data in the
>>> mongodb database .
>>>
>>> Problme 2: If the primay machine is down then secondary becomes
>>> primary within some millisecond time  , but  opensips crashes giving bellow
>>> error
>>>
>>>   ERROR:cachedb_mongodb:mongo_con_get: Failed to run query. Err = 6,
>>> 0 , 0
>>>  CRITICAL:core:receive_fd: EOF on 10
>>>  INFO:core:handle_sigs: child process 5278 exited by a signal 11
>>>  INFO:core:handle_sigs: core was generated
>>>  INFO:core:handle_sigs: terminating due to SIGCHLD
>>>  INFO:core:sig_usr: signal 15 received
>>>  INFO:core:sig_usr: signal 15 received
>>>  INFO:core:sig_usr: signal 15 received
>>>  INFO:core:sig_usr: signal 15 received
>>>  INFO:core:sig_usr: signal 15 received
>>>  INFO:core:sig_usr: signal 15 received
>>>  INFO:core:sig_usr: signal 15 received
>>>  INFO:core:sig_usr: signal 15 received
>>>  INFO:core:sig_usr: signal 15 received
>>>  INFO:core:sig_usr: signal 15 received
>>>  INFO:core:sig_usr: signal 15 received
>>>  INFO:core:sig_usr: signal 15 received
>>>  INFO:core:sig_usr: signal 15 received
>>>  INFO:core:cleanup: cleanup
>>>  NOTICE:db_cachedb:destroy: destroy module db_cachedb ...
>>>  NOTICE:cachedb_mongodb:destroy: destroy module cachedb_mongodb ...
>>>
>>>  If my secondary mongodb machine is not reachable then rather
>>> connection with db breaks for sometime but opensips wont crashes . But in
>>> case of Primary opensips crashes with above error . Is this an expected
>>> behavior or I am doing anything wrong .
>>>
>>>   Data loss can be bearable but application cant be . So please let
>>> me know whats the problem .
>>>
>>> *Thanks & Regards*
>>> 

[OpenSIPS-Users] Register with TO Tag

[John Nash]

I am dealing with In-dialog requests using

--
if (has_totag() && (is_domain_local("$rd") || $Ri== "127.0.0.1") &&
is_method("INVITE|ACK|BYE|UPDATE"))
{
# sequential request within a dialog should
# take the path determined by record-routing
if (topology_hiding_match())
-
-

at the top of my script. After that I process initial requests, but I see
some REGISTER messages with TO-Tag and "Route" header and they are being
discarded by my script because Initial request cannot have Route header.

Do i also need to pass REGISTER messages also through same block?...or i
need to call loose_route after has_to_tag check.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users