date:20160609

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

2016-06-09 Thread Jeff Wilkie

Bogdan,

Based on what you have provided, I decided to change the boxes.global.inc.php
file as follows:

$box_id=0;


// mi host:port pair || fifo_file

*$boxes[$box_id]['mi']['conn']="127.0.0.1:8080 ";*

//boxes[$box_id]['mi']['conn']="/tmp/opensips_proxy_fifo";

It now is able to disable and enable the gateways. I'm not sure if anything
else is broken as a result but I will go through the testing.  Is there a
reason why it would not work using the fifo file instead?


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 Thu, Jun 9, 2016 at 11:14 AM, Bogdan-Andrei Iancu 
wrote:

> Jeff,
>
> To have the CP connecting to OpenSIPS you can use any of the MI backends -
> FIFO, XMLRPC, UDP...any will do the trick. The downside of FIFO is that the
> CP and OpenSIPS must be on the same server.
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 09.06.2016 17:38, Jeff Wilkie wrote:
>
> Is XMLRPC required to make this function work?  Currently, we are only
> using the fifo method as the boxes.global.inc.php only referencing this
> method.  The documentation for CP says to use one or the other but does not
> mention that some functions will not work if not using XMLRPC.
>
> Thanks
> Jeff
>
> 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, Jun 7, 2016 at 6:52 AM, Bogdan-Andrei Iancu <
> bog...@opensips.org> wrote:
>
>> 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 Developerhttp://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 <
>> bog...@opensips.org> wrote:
>>
>>> Hi Jeff,
>>>
>>> What OpenSIPS Control Panel version are you using ?
>>>
>>> Regards,
>>>
>>> Bogdan-Andrei Iancu
>>> OpenSIPS Founder and Developerhttp://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)
>>>

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

2016-06-09 Thread Jeff Wilkie

Yes. CP and opensips are on the same server.  Only the disable doesn't
work. I can enable them using CP.

Thanks

Jeff Wilkie
USIP Communications
On Jun 9, 2016 11:14 AM, "Bogdan-Andrei Iancu"  wrote:

> Jeff,
>
> To have the CP connecting to OpenSIPS you can use any of the MI backends -
> FIFO, XMLRPC, UDP...any will do the trick. The downside of FIFO is that the
> CP and OpenSIPS must be on the same server.
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 09.06.2016 17:38, Jeff Wilkie wrote:
>
> Is XMLRPC required to make this function work?  Currently, we are only
> using the fifo method as the boxes.global.inc.php only referencing this
> method.  The documentation for CP says to use one or the other but does not
> mention that some functions will not work if not using XMLRPC.
>
> Thanks
> Jeff
>
> 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, Jun 7, 2016 at 6:52 AM, Bogdan-Andrei Iancu 
> wrote:
>
>> 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 Developerhttp://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 Developerhttp://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 
>>>

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

2016-06-09 Thread Bogdan-Andrei Iancu

Jeff,

To have the CP connecting to OpenSIPS you can use any of the MI backends 
- FIFO, XMLRPC, UDP...any will do the trick. The downside of FIFO is 
that the CP and OpenSIPS must be on the same server.

Regards,

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

On 09.06.2016 17:38, Jeff Wilkie wrote:
Is XMLRPC required to make this function work?  Currently, we are only 
using the fifo method as the boxes.global.inc.php only referencing 
this method.  The documentation for CP says to use one or the other 
but does not mention that some functions will not work if not using 
XMLRPC.

Thanks
Jeff

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, Jun 7, 2016 at 6:52 AM, Bogdan-Andrei Iancu 
> wrote:

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

[OpenSIPS-Users] How to update table location, but directly on memory cache (RAM)?

2016-06-09 Thread Rodrigo Pimenta Carvalho


Hi.


My script has the configuration:


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

Always after receiving a new register in table location, I must to execute a 
code like this:


avp_db_query("UPDATE location...


That is, an update will complement data in the new register.


However, how could I immediately update table location if data might be in 
memory cache (RAM) for 3 seconds. It could fail obviously.

The command avp_db_query UPDATE is acting over the database on hard disc, not 
in obviously.

So, is there a way to update table location even still in cache (RAM)? If yes, 
when data from RAM is recorded into the database, the register will already be 
updated.


Any hint will be very helpful!


Best regards.


RODRIGO PIMENTA CARVALHO
Inatel Competence Center
Software
Ph: +55 35 3471 9200 RAMAL 979
___
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

2016-06-09 Thread Jeff Wilkie

Is XMLRPC required to make this function work?  Currently, we are only
using the fifo method as the boxes.global.inc.php only referencing this
method.  The documentation for CP says to use one or the other but does not
mention that some functions will not work if not using XMLRPC.

Thanks
Jeff

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, Jun 7, 2016 at 6:52 AM, Bogdan-Andrei Iancu 
wrote:

> 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 Developerhttp://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 <
> bog...@opensips.org> wrote:
>
>> Hi Jeff,
>>
>> What OpenSIPS Control Panel version are you using ?
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>> OpenSIPS Founder and Developerhttp://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 
>> 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] Problems migrating from v2.1 to v2.2

2016-06-09 Thread Bogdan-Andrei Iancu


Hi John,

Thank you for your report.

I found a typo (c'n'p error) in the DB migration code - this is fixed 
now, so you can update from GIT and re-test.


We will follow up on the issue related to the CTL scripts.

Regards,

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

On 08.06.2016 17:51, John Quick wrote:

I just wanted to report some snags I hit when migrating. Note: I had the
install prefix set to /

After running make+Install for v2.2, executable files in /usr/local/sbin
were not updated to the v2.2 versions. The new versions were *only* in /sbin
That would be okay, except that when I ran opensipsdbctl, it tried to run
the old version in /usr/local/sbin
When I deleted the old executable files in /usr/local/sbin, I got this
error:
"-bash: /usr/local/sbin/opensipsdbctl: No such file or directory"
...so I copied everything for opensips that was in /sbin to /usr/local/sbin
and that seemed to fix it.

Then I finally was able to run opensipsdbctl migrate   and I
got the following errors which I was able to skip:
ERROR: failed to migrate opensips_v21.cc_flows to opensips_v22.cc_agents
(ERROR 1054 (42S22) at line 1: Unknown column
'opensips_v21.cc_flows.agentid' in 'field list')!!!
Skip it and continue (y/n)? y
ERROR: failed to migrate opensips_v21.cc_flows to opensips_v22.cc_cdrs
(ERROR 1054 (42S22) at line 1: Unknown column 'opensips_v21.cc_flows.caller'
in 'field list')!!!

John Quick
Smartvox Limited
Web: www.smartvox.co.uk



___
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 CP DROUTING GATEWAY enable/disable issue

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

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

[OpenSIPS-Users] How to update table location, but directly on memory cache (RAM)?

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

Re: [OpenSIPS-Users] Problems migrating from v2.1 to v2.2

6 matches

Site Navigation

Mail list logo

Footer information