[OpenSIPS-Users] Opensips CP Permissions "RELOAD on SERVER" produces error

[Jeff Wilkie]

Opensips 3.1.2
CP 8.3.1
Debian 10

When adding permissions, I hit "Reload on Server" but I get the following error:

Sending to json:127.0.0.1:/mi : MI command failed with code -32601 (Method 
not found)

I​
I don't get this error on any other page but this one when attempting to 
"Reload on Server".  Is there something specifically wrong with this page and 
how it uses the MI command structure?  Again, All other pages that use the 
"Reload on Server" give a 200ok and work as expected.

Thanks,

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

Re: [OpenSIPS-Users] Opensips CP Permissions "RELOAD on SERVER" produces error

[Jeff Wilkie]

You are correct.  My error.  It wasn't loaded.

Thanks
Jeff


On Thu, Jul 22, 2021 at 2:57 AM Bogdan-Andrei Iancu 
wrote:

> Hi Jeff,
>
> Are you sure the OpenSIPS (your CP is connected to ) has the permissions
> module loaded ?
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
> OpenSIPS Bootcamp 2021 online
>   https://opensips.org/training/OpenSIPS_eBootcamp_2021/
>
> On 7/21/21 4:17 PM, Jeff Wilkie wrote:
>
> Opensips 3.1.2
> CP 8.3.1
> Debian 10
>
> When adding permissions, I hit "Reload on Server" but I get the
> following error:
>
> Sending to *json:127.0.0.1:/mi <http://127.0.0.1:/mi>* : MI
> command failed with code -32601 (Method not found)
>
> I
> I don't get this error on any other page but this one when attempting to
> "Reload on Server".  Is there something specifically wrong with this page
> and how it uses the MI command structure?  Again, All other pages that use
> the "Reload on Server" give a 200ok and work as expected.
>
> 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

[OpenSIPS-Users] Opensips CP Permissions "RELOAD on SERVER" produces error

[Jeff Wilkie]

Opensips 3.1.2
CP 8.3.1
Debian 10

When adding permissions, I hit "Reload on Server" but I get the
following error:

Sending to *json:127.0.0.1:/mi * : MI command
failed with code -32601 (Method not found)

I
I don't get this error on any other page but this one when attempting to
"Reload on Server".  Is there something specifically wrong with this page
and how it uses the MI command structure?  Again, All other pages that use
the "Reload on Server" give a 200ok and work as expected.

Thanks,

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

Re: [OpenSIPS-Users] Opensips 2.4.x and CP 8

[Jeff Wilkie]

Last comments in Changelog are the following dates

2019-07-22  Bogdan Iancu  


I think I downloaded 8.3.0 by mistake!  f.  Let me reinstall with 8.2.4
git


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

Re: [OpenSIPS-Users] Recommended Radius client/server for AAA on 2.4.x under Debian 9

[Jeff Wilkie]

Any build and config docs to support radcli installation with opensips 2.4
and 3.x by chance?

Thanks
Jeff

On Wed, Nov 6, 2019 at 4:56 AM Răzvan Crainea  wrote:

> radcli is the library we're using in our latest packages.
>
> Best regards,
> Răzvan
>
> On 11/6/19 5:48 AM, qasimak...@gmail.com wrote:
> > You can use latest version of freeradius it has both client and server.
> >
> > Regards,
> > Qasim
> >
> > On Wed, 6 Nov 2019 at 8:27 AM, Jeff Wilkie  > <mailto:jwil...@usipcom.com>> wrote:
> >
> > Attempting to find current docs since radiusclient-ng is referenced
> > in several old docs but is no longer available.  Currently, what is
> > the recommending radius packages to use for accounting purposes on
> > opensips for CDRs and ACC?
> >
> > Thanks
> > Jeff
> > ___
> > Users mailing list
> > Users@lists.opensips.org <mailto: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
> >
>
> --
> Răzvan Crainea
> OpenSIPS Core Developer
>http://www.opensips-solutions.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

Re: [OpenSIPS-Users] Opensips 2.4.x and CP 8

[Jeff Wilkie]

>
> Thanks for the response.  That document does not explain why I'm seeing a
> POST error using the CP8.  If I directly http to opensips using requests
> for json it works properly using a GET.  Why would the the CP generate a
> POST using JSON?  How do I turn that off?  Any reload command in the CP
> generate this ERROR in the opensips logs.
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Recommended Radius client/server for AAA on 2.4.x under Debian 9

[Jeff Wilkie]

Attempting to find current docs since radiusclient-ng is referenced in
several old docs but is no longer available.  Currently, what is the
recommending radius packages to use for accounting purposes on opensips for
CDRs and ACC?

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

[OpenSIPS-Users] Opensips 2.4.x and CP 8

[Jeff Wilkie]

Attempting to get CP8 and 2.4.x talking to each other.  I have modules in
the config enabled

loadmodule "httpd.so"
modparam("httpd", "ip", "127.0.0.1")
modparam("httpd", "port", )
loadmodule "mi_json.so"
modparam("mi_json", "mi_json_root", "json")

When attempting to execute any MI_json command from CP we're seeing this
from the opensips logs.

ERROR:mi_json:mi_json_answer_to_connection: unexpected method [POST]

Where is this error being generated?  How do we correct this?

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

Re: [OpenSIPS-Users] [RELEASE] OpenSIPS 2.4.6 Minor Version

[Jeff Wilkie]

Thanks for that info.  I've extracted 2.4.6 and saved the old Makefile.conf
then moved it back into the 2.4.6 root directory followed by a make
install.  After completing and running I still get the following on
opensips -V:

version: opensips *2.4.0* (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_MALLOC,
FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll, sigio_rt, select.
main.c compiled on 22:12:42 Oct 24 2019 with gcc 6.3.0

Shouldn't I see 2.4.6 here?


<https://www.usipcom.com/>
Jeff Wilkie
*CTO*

p: 919-297-1057 <(919)%20297-1057> p/f: 919-882-8490 <(919)%20882-8490> m:
919-348-0753 <(919)%20348-0753>
a: 3201 Northside Dr, Suite 109, Raleigh NC, 27615
w: www.usipcom.com e: jwil...@usipcom.com

[image: supp...@usipcom.com] .
<https://twitter.com/UsipcomSupport>.
<https://www.linkedin.com/company/usipcommunications?trk=top_nav_home>


*"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, Oct 24, 2019 at 11:25 AM Răzvan Crainea  wrote:

> Hi, Jeff!
>
> Unfortunately you can't update without a complete reinstall, but most
> likely there's no need of any migration.
> If you still have the old src directory, all you have to do is to copy
> the Makefile.conf file in the new root directory of the decompressed
> opensips-2.4.6.tar.gz.
> After that, running `make install` should compile the same modules in
> the same paths as the previous install. NOTE that this will overwrite
> the previous install, but you can always rollback by running `make
> install` on the old decompress dir.
> If you don't have the old sources, you'll have to reconfigure opensips
> build all over again.
> Hope this helps!
>
> Best regards,
> Răzvan
>
> On 10/23/19 1:04 AM, Jeff Wilkie wrote:
> >
> > We've been sitting on 2.4.0 in the lab for a while and would like to
> > update to 2.4.6 or latest LTS.  Originally installed with a tar file,
> > can we update without having to completely reinstall or migrate?  Can
> > you link the procedure if so?
> >
> > Thank you
> >
> > On Tue, Jun 11, 2019 at 11:29 AM Răzvan Crainea  > <mailto:raz...@opensips.org>> wrote:
> >
> > Hi, everyone!
> >
> > We are thrilled to announce you that we've just released a new minor
> > version of the OpenSIPS 2.4 branch. The new OpenSIPS 2.4.6[1]
> contains
> > all the bug fixes we've resolved during the last months, ensuring you
> > your deployment more stable now!
> > This minor release does not need any migration, so feel free to
> update
> > to the latest version anytime! For a full list of changes, consult
> the
> > ChangeLog[2].
> >
> > [1] https://opensips.org/pub/opensips/2.4.6/opensips-2.4.6.tar.gz
> > [2] https://opensips.org/pub/opensips/2.4.6/ChangeLog
> >
> > Cheers,
> > --
> > Răzvan Crainea
> > OpenSIPS Core Developer
> > http://www.opensips-solutions.com
> >
> > ___
> > Users mailing list
> > Users@lists.opensips.org <mailto: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
> >
>
> --
> Răzvan Crainea
> OpenSIPS Core Developer
>http://www.opensips-solutions.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

Re: [OpenSIPS-Users] [RELEASE] OpenSIPS 2.4.6 Minor Version

[Jeff Wilkie]

We've been sitting on 2.4.0 in the lab for a while and would like to update
to 2.4.6 or latest LTS.  Originally installed with a tar file, can we
update without having to completely reinstall or migrate?  Can you link the
procedure if so?

Thank you

On Tue, Jun 11, 2019 at 11:29 AM Răzvan Crainea  wrote:

> Hi, everyone!
>
> We are thrilled to announce you that we've just released a new minor
> version of the OpenSIPS 2.4 branch. The new OpenSIPS 2.4.6[1] contains
> all the bug fixes we've resolved during the last months, ensuring you
> your deployment more stable now!
> This minor release does not need any migration, so feel free to update
> to the latest version anytime! For a full list of changes, consult the
> ChangeLog[2].
>
> [1] https://opensips.org/pub/opensips/2.4.6/opensips-2.4.6.tar.gz
> [2] https://opensips.org/pub/opensips/2.4.6/ChangeLog
>
> Cheers,
> --
> Răzvan Crainea
> OpenSIPS Core Developer
>http://www.opensips-solutions.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

Re: [OpenSIPS-Users] CDRtool vs CGRATES for Opensips 2.2 +

[Jeff Wilkie]

DanB,

Thanks for the very useful information!

I'm reading that the preferred install OS for CGRATES is Debian.  Most of
our development happens on CENTOS 6.x.  Are there packages yet for CENT?
Or would we be required to install from source if we keep that OS?

Thanks

Jeff Wilkie


On Sun, Mar 5, 2017 at 6:32 AM, DanB <danb.li...@gmail.com> wrote:

> Hi Jeff,
>
> Although it is a slippery ground, in order to have the question answered,
> I can claim having experience with both systems (we used to install CDRTool
> for customers and still have today installs running since like 8 years
> without issues).
>
> CDRTool (CDR rating system):
>
> * Written in php, works closely with db (eg: relies on it's query
> speed with some caching for parts of the rates)
>
> * Mature implementation, not much development changing the code over
> the years (other than bug fixes).
>
> * Simple rating definition and implementation.
>
> * Web interface for rates management as well as CDRs.
>
> * Designed around rating CDRs and maintaining account balance.
>
>
> CGRateS (OCS - online charging system):
>
> * Written in Go, caches almost all information in process, database
> agnostic (abstracts databases into interfaces), database speed does not
> influence the speed of calculations, built on micro-services with full
> asynchronous processing.
>
> * Still in Release Candidate when it comes to architecture, evolved a
> lot over the years, master should be always stable in terms of
> functionality since it runs in production environments (architecture part
> is not yet declared stable - you can expect it to still evolve).
>
> * Complex rating (rates voice calls, data streams, sms, etc) and
> accounting (unlimited number of balances/bundles and failover between them
> during a call).
>
> * API (JSON) driven management (full set) with no official web
> interface available yet.
>
> * Additional functionality: fraud detection with automatic mitigation
> (3 layers: accounts, CDR stats, resources usage), CDR logging with support
> for interim records, QoS LCR and LCR over bundels, real-time (complete in
> memory) call statistics with pattern monitoring and triggers/web hooks
> towards external systems, derive charging (session emulation -
> reseller/distributor scenarios, customer/supplier parallel calculations),
> performance optimized (one CGRateS instance should be able to handle 5k
> requests per second in terms of rating calculations), built-in high
> availability for Diameter setups.
>
>
> So these being said, it is all about the need vs price (time investment)
> you are ready to pay for it by using one system or another (considering
> both systems are opensource and you can extend yourself in one way or
> another). If you don't have complex rating requirements nor the need of
> increased CPS, I trust CDRTool will do the job just fine since it did it
> for us over the years (you get the advantage as said of simple management
> and architecture stability, quick learning curve). CGRateS on the other
> hand should be there if you decide you need more functionality/speed and
> you are also ready to offer it more time and efforts.
>
>
> I hope this helps someone!
>
> DanB
>
>
> ___
> 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] CDRtool vs CGRATES for Opensips 2.2 +

[Jeff Wilkie]

Just pinging the general community on a pros/cons list between these two
systems for rating calls.  I would love to hear feedback on comparisons and
experiences. Finding it hard to see big differences from documentation
other than methods to produce the records and the graphical front end.

Thanks

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

[OpenSIPS-Users] OPENSIPS-CP 6.2

[Jeff Wilkie]

Found small error in drouting code for CP

opensips-cp/web/tools/system/drouting/template/carriers.main.php


has a reference to src="../../../images/share/inactive.gif
and src="../../../images/share/active.gif but neither of these are
present.  Both of these file extensions should be .png


Thanks


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

Re: [OpenSIPS-Users] 2.2.x and CP with json

[Jeff Wilkie]

Disregard. I was giving you the version of opensips in which the errors
occurred. My subject says 2.2.x. It was actually dev

Thanks

Jeff Wilkie
USIP Communications

On Feb 27, 2017 5:09 AM, "Bogdan-Andrei Iancu" <bog...@opensips.org> wrote:

> Hi Jeff,
>
> What do you mean ? I tried the "version" command via the MI tool and it
> properly works - what kind of error do you experience ?
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 02/24/2017 07:21 PM, Jeff Wilkie wrote:
>
> Thanks Bogdan,  I will dl 2.2.3 and retest.  This error occurred on the
> following BTW
>
> Array
> (
> [Server] => OpenSIPS (2.3.0-dev (x86_64/linux))
> )
>
>
> Jeff Wilkie
>
> On Fri, Feb 24, 2017 at 4:46 AM, Bogdan-Andrei Iancu <bog...@opensips.org>
> wrote:
>
>> Hi Jeff,
>>
>> There was an issue on how the MI output of the address_dump was formated
>> when using JSON. This issue was leading to an invalid JSON being returned.
>> And CP was dropping the returned JSON as not able being able to parse it.
>> If you do the direct web query, there is nothing to parse/validate the
>> JSON, so it is displayed.
>>
>> The issue was fixed in latest 2.2, so please grab the 2.2.3 and give it a
>> try please.
>>
>> Best regards,
>>
>> Bogdan-Andrei Iancu
>> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>>
>> On 02/22/2017 08:24 PM, Jeff Wilkie wrote:
>>
>> Ok, question part 2, now that the proper module is loaded :)  From the MI
>> interface in CP, I have 1 small issue.  Using json to interface with
>> opensips, I execute the command "*address_dump" *and execute.  I receive
>> the output of address dump   |  son:127.0.0.1:/json Successfully
>> executed, no output generated.  Other commands like domain_dump work as
>> expected in the SYSTEM/MI interface.  If I bypass CP and use web direct
>> command 127.0.0.1:/json/address_dump I receive the proper output.
>> Not sure why CP provides no output from this command though.
>> The web query directly looks like this as a response when not using MI
>> via CP
>> http://10.10.20.229:/json/address_dump
>>
>> {"part": [{"value":"default", "children":{"dest": [{"value":"   8 
>> <10.10.10.99,2, 5060, 1, NULL, 151559>"}, {"value":" 19 
>> <10.10.20.193,2, 5060, 1, NULL, 151559>"}, {"value":"81 
>> <192.168.1.203,1, 5060, 1, NULL, NULL>"}]}}]}
>>
>> It's not a show stopper but bugging me why it doesn't work for that
>> command only from what I can tell from initial testing.
>> Jeff Wilkie
>>
>>> Yes, you did overlook to load the dialplan module into your OpenSIPS
>>> (the dp_reload command is prvided by this modules). Regards,
>>>
>>> Bogdan-Andrei Iancu
>>> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>>>
>>> On 02/22/2017 05:56 PM, Jeff Wilkie wrote:
>>>
>>> When using the mi_json module combined with CP, it appears that not all
>>> of the functions were ported over for this interaction to complete 100%.
>>> JSON enabled in opensips-cp/config/boxes.global.inc.php only allows
>>> some commands to work.  One particular command that appears to not be
>>> working is under SYSTEM/DIALPLAN of CP when you attempt to hit "apply to
>>> server".  I receive a Sending to *json:127.0.0.1:/json
>>> <http://127.0.0.1:/json>* : Error code 500 (Command not found) for
>>> the dp_reload command.  If I do the same thing under the SYSTEM/PERMISSIONS
>>> page "apply to server" returns success for address_reload.   Is this a
>>> known issue?  Did I overlook something small in the config?  How do I
>>> remedy this issue?
>>> Thanks
>>> Jeff Wilkie
>>>
>>> ___
>>> 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

[OpenSIPS-Users] CP 6.2 drouting Error code 500 (Internal server error)

[Jeff Wilkie]

_run_mi_cmd: command=dr_gw_status accepts parameters

Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_run_mi_cmd: got string param [2]

Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_run_mi_cmd: got string param [1]

*Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
ERROR:mi_json:mi_json_run_mi_cmd: failed to process the command*

*Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
ERROR:mi_json:mi_json_answer_to_connection: no reply*

Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
DBG:httpd:answer_to_connection: MHD_create_response_from_data
[0x7f0a7ddcc600:60]

Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
DBG:httpd:answer_to_connection: START *** cls=(nil), connection=0x1c83380,
url=/json/dr_gw_status, method=GET, versio=HTTP/1.1, upload_data[0]=(nil),
*con_cls=(nil)

Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
DBG:httpd:getConnectionHeader: Accept=*/*

Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
DBG:httpd:answer_to_connection: accept_type=[-1]

Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
DBG:httpd:answer_to_connection: normalised_url=[/dr_gw_status]

Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_answer_to_connection: START *** cls=(nil),
connection=0x1c83380, url=/dr_gw_status, method=GET, versio=HTTP/1.1,
upload_data[0]=(nil), *con_cls=(nil)

Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_run_mi_cmd: got command=dr_gw_status

Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_run_mi_cmd: command=dr_gw_status accepts parameters

Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_run_mi_cmd: but no parameters were found

Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_run_mi_cmd: got mi_rpl=[0x7f0a885c34a0]

Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_answer_to_connection: building on page
[0x7f0a86dc3318:0]

Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_build_page: start

Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_build_content: start

Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_recur_write_tree: Treat as an array

Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_recur_write_tree: done

Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_build_content: done

Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
DBG:httpd:answer_to_connection: MHD_create_response_from_data
[0x7f0a86dc3318:440]


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". *
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] 2.2.x and CP with json

[Jeff Wilkie]

Compiling the 2.2.3, I'm seeing several warnings of similar type below:

lookup.c: In function ‘is_contact_registered’:

lookup.c:559: warning: ‘callid.len’ may be used uninitialized in this
function

lookup.c:559: warning: ‘callid.s’ may be used uninitialized in this function


dlg_replication.c: In function ‘dlg_replicated_profiles’:

dlg_replication.c:838: warning: ‘old_name.s’ may be used uninitialized in
this function

dlg_replication.c:838: warning: ‘old_name.len’ may be used uninitialized in
this function

Is this anything to worry about?

Jeff Wilkie


On Fri, Feb 24, 2017 at 12:21 PM, Jeff Wilkie <jwil...@usipcom.com> wrote:

> Thanks Bogdan,  I will dl 2.2.3 and retest.  This error occurred on the
> following BTW
>
> Array
> (
> [Server] => OpenSIPS (2.3.0-dev (x86_64/linux))
> )
>
>
> Jeff Wilkie
>
> On Fri, Feb 24, 2017 at 4:46 AM, Bogdan-Andrei Iancu <bog...@opensips.org>
> wrote:
>
>> Hi Jeff,
>>
>> There was an issue on how the MI output of the address_dump was formated
>> when using JSON. This issue was leading to an invalid JSON being returned.
>> And CP was dropping the returned JSON as not able being able to parse it.
>> If you do the direct web query, there is nothing to parse/validate the
>> JSON, so it is displayed.
>>
>> The issue was fixed in latest 2.2, so please grab the 2.2.3 and give it a
>> try please.
>>
>> Best regards,
>>
>> Bogdan-Andrei Iancu
>> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>>
>> On 02/22/2017 08:24 PM, Jeff Wilkie wrote:
>>
>> Ok, question part 2, now that the proper module is loaded :)  From the MI
>> interface in CP, I have 1 small issue.  Using json to interface with
>> opensips, I execute the command "*address_dump" *and execute.  I receive
>> the output of address dump   |  son:127.0.0.1:/json Successfully
>> executed, no output generated.  Other commands like domain_dump work as
>> expected in the SYSTEM/MI interface.  If I bypass CP and use web direct
>> command 127.0.0.1:/json/address_dump I receive the proper output.
>> Not sure why CP provides no output from this command though.
>>
>> The web query directly looks like this as a response when not using MI
>> via CP
>>
>> http://10.10.20.229:/json/address_dump
>>
>> {"part": [{"value":"default", "children":{"dest": [{"value":"   8 
>> <10.10.10.99,2, 5060, 1, NULL, 151559>"}, {"value":" 19 
>> <10.10.20.193,2, 5060, 1, NULL, 151559>"}, {"value":"81 
>> <192.168.1.203,1, 5060, 1, NULL, NULL>"}]}}]}
>>
>>
>> It's not a show stopper but bugging me why it doesn't work for that
>> command only from what I can tell from initial testing.
>>
>> Jeff Wilkie
>>
>>
>>
>>> Yes, you did overlook to load the dialplan module into your OpenSIPS
>>> (the dp_reload command is prvided by this modules).
>>>
>>> Regards,
>>>
>>> Bogdan-Andrei Iancu
>>> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>>>
>>> On 02/22/2017 05:56 PM, Jeff Wilkie wrote:
>>>
>>> When using the mi_json module combined with CP, it appears that not all
>>> of the functions were ported over for this interaction to complete 100%.
>>> JSON enabled in opensips-cp/config/boxes.global.inc.php only allows
>>> some commands to work.  One particular command that appears to not be
>>> working is under SYSTEM/DIALPLAN of CP when you attempt to hit "apply to
>>> server".  I receive a Sending to *json:127.0.0.1:/json
>>> <http://127.0.0.1:/json>* : Error code 500 (Command not found) for
>>> the dp_reload command.  If I do the same thing under the SYSTEM/PERMISSIONS
>>> page "apply to server" returns success for address_reload.   Is this a
>>> known issue?  Did I overlook something small in the config?  How do I
>>> remedy this issue?
>>> Thanks
>>> Jeff Wilkie
>>>
>>> ___
>>> 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] 2.2.x and CP with json

[Jeff Wilkie]

Thanks Bogdan,  I will dl 2.2.3 and retest.  This error occurred on the
following BTW

Array
(
[Server] => OpenSIPS (2.3.0-dev (x86_64/linux))
)


Jeff Wilkie

On Fri, Feb 24, 2017 at 4:46 AM, Bogdan-Andrei Iancu <bog...@opensips.org>
wrote:

> Hi Jeff,
>
> There was an issue on how the MI output of the address_dump was formated
> when using JSON. This issue was leading to an invalid JSON being returned.
> And CP was dropping the returned JSON as not able being able to parse it.
> If you do the direct web query, there is nothing to parse/validate the
> JSON, so it is displayed.
>
> The issue was fixed in latest 2.2, so please grab the 2.2.3 and give it a
> try please.
>
> Best regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 02/22/2017 08:24 PM, Jeff Wilkie wrote:
>
> Ok, question part 2, now that the proper module is loaded :)  From the MI
> interface in CP, I have 1 small issue.  Using json to interface with
> opensips, I execute the command "*address_dump" *and execute.  I receive
> the output of address dump   |  son:127.0.0.1:/json Successfully
> executed, no output generated.  Other commands like domain_dump work as
> expected in the SYSTEM/MI interface.  If I bypass CP and use web direct
> command 127.0.0.1:/json/address_dump I receive the proper output.
> Not sure why CP provides no output from this command though.
>
> The web query directly looks like this as a response when not using MI via
> CP
>
> http://10.10.20.229:/json/address_dump
>
> {"part": [{"value":"default", "children":{"dest": [{"value":"8 
> <10.10.10.99,2, 5060, 1, NULL, 151559>"}, {"value":" 19 
> <10.10.20.193,2, 5060, 1, NULL, 151559>"}, {"value":"81 
> <192.168.1.203,1, 5060, 1, NULL, NULL>"}]}}]}
>
>
> It's not a show stopper but bugging me why it doesn't work for that
> command only from what I can tell from initial testing.
>
> Jeff Wilkie
>
>
>
>> Yes, you did overlook to load the dialplan module into your OpenSIPS (the
>> dp_reload command is prvided by this modules).
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>>
>> On 02/22/2017 05:56 PM, Jeff Wilkie wrote:
>>
>> When using the mi_json module combined with CP, it appears that not all
>> of the functions were ported over for this interaction to complete 100%.
>> JSON enabled in opensips-cp/config/boxes.global.inc.php only allows some
>> commands to work.  One particular command that appears to not be working is
>> under SYSTEM/DIALPLAN of CP when you attempt to hit "apply to server".  I
>> receive a Sending to *json:127.0.0.1:/json
>> <http://127.0.0.1:/json>* : Error code 500 (Command not found) for
>> the dp_reload command.  If I do the same thing under the SYSTEM/PERMISSIONS
>> page "apply to server" returns success for address_reload.   Is this a
>> known issue?  Did I overlook something small in the config?  How do I
>> remedy this issue?
>> Thanks
>> Jeff Wilkie
>>
>> ___
>> 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] 2.2.x and CP with json

[Jeff Wilkie]

Ok, question part 2, now that the proper module is loaded :)  From the MI
interface in CP, I have 1 small issue.  Using json to interface with
opensips, I execute the command "*address_dump" *and execute.  I receive
the output of address dump   |  son:127.0.0.1:/json Successfully
executed, no output generated.  Other commands like domain_dump work as
expected in the SYSTEM/MI interface.  If I bypass CP and use web direct
command 127.0.0.1:/json/address_dump I receive the proper output.  Not
sure why CP provides no output from this command though.

The web query directly looks like this as a response when not using MI via
CP

http://10.10.20.229:/json/address_dump

{"part": [{"value":"default", "children":{"dest": [{"value":"  8
<10.10.10.99,2, 5060, 1, NULL, 151559>"}, {"value":"  19
<10.10.20.193,2, 5060, 1, NULL, 151559>"}, {"value":" 81
<192.168.1.203,1, 5060, 1, NULL, NULL>"}]}}]}


It's not a show stopper but bugging me why it doesn't work for that command
only from what I can tell from initial testing.

Jeff Wilkie



> Yes, you did overlook to load the dialplan module into your OpenSIPS (the
> dp_reload command is prvided by this modules).
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 02/22/2017 05:56 PM, Jeff Wilkie wrote:
>
> When using the mi_json module combined with CP, it appears that not all of
> the functions were ported over for this interaction to complete 100%.  JSON
> enabled in opensips-cp/config/boxes.global.inc.php only allows some
> commands to work.  One particular command that appears to not be working is
> under SYSTEM/DIALPLAN of CP when you attempt to hit "apply to server".  I
> receive a Sending to *json:127.0.0.1:/json
> <http://127.0.0.1:/json>* : Error code 500 (Command not found) for
> the dp_reload command.  If I do the same thing under the SYSTEM/PERMISSIONS
> page "apply to server" returns success for address_reload.   Is this a
> known issue?  Did I overlook something small in the config?  How do I
> remedy this issue?
>
> Thanks
>
> Jeff Wilkie
>
>
>
> ___
> 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] 2.2.x and CP with json

[Jeff Wilkie]

DOH!  Got me.  Sorry for the distraction but thanks for the simple fix.
Working too fast on this new test bed I guess.

Jeff Wilkie


On Wed, Feb 22, 2017 at 11:20 AM, Bogdan-Andrei Iancu <bog...@opensips.org>
wrote:

> Hi Jeff,
>
> Yes, you did overlook to load the dialplan module into your OpenSIPS (the
> dp_reload command is prvided by this modules).
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 02/22/2017 05:56 PM, Jeff Wilkie wrote:
>
> When using the mi_json module combined with CP, it appears that not all of
> the functions were ported over for this interaction to complete 100%.  JSON
> enabled in opensips-cp/config/boxes.global.inc.php only allows some
> commands to work.  One particular command that appears to not be working is
> under SYSTEM/DIALPLAN of CP when you attempt to hit "apply to server".  I
> receive a Sending to *json:127.0.0.1:/json
> <http://127.0.0.1:/json>* : Error code 500 (Command not found) for
> the dp_reload command.  If I do the same thing under the SYSTEM/PERMISSIONS
> page "apply to server" returns success for address_reload.   Is this a
> known issue?  Did I overlook something small in the config?  How do I
> remedy this issue?
>
> Thanks
>
> Jeff Wilkie
>
>
>
> ___
> 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

[OpenSIPS-Users] 2.2.x and CP with json

[Jeff Wilkie]

When using the mi_json module combined with CP, it appears that not all of
the functions were ported over for this interaction to complete 100%.  JSON
enabled in opensips-cp/config/boxes.global.inc.php only allows some
commands to work.  One particular command that appears to not be working is
under SYSTEM/DIALPLAN of CP when you attempt to hit "apply to server".  I
receive a Sending to *json:127.0.0.1:/json <http://127.0.0.1:/json>*
 : Error code 500 (Command not found) for the dp_reload command.  If I do
the same thing under the SYSTEM/PERMISSIONS page "apply to server" returns
success for address_reload.   Is this a known issue?  Did I overlook
something small in the config?  How do I remedy this issue?

Thanks

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

[OpenSIPS-Users] Fraud module

[Jeff Wilkie]

Any chance of this module showing up in the cp soon?  Minus me writing it
that is lol

Thanks

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

Re: [OpenSIPS-Users] yum install vs download manual install

[Jeff Wilkie]

If using the yum install on Centos, what's the preferred method to control
the mem size since those files do not appear to be present?

Jeff


On Mon, Feb 20, 2017 at 7:38 AM, Bogdan-Andrei Iancu <bog...@opensips.org>
wrote:

> Hi Jeff,
>
> The main different between packages versus tarballs is the OS integration
> : while the tarball gives you OpenSIPS, the pacakges come with additional
> scripts to help with the OS integration (like the init.d script, some
> default settings)
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 02/15/2017 08:22 PM, Jeff Wilkie wrote:
>
> What am I missing out on by installing via yum vs the way I've always
> installed OPENSIPS by download extraction?  I notice some of the linking
> files and MEMORY setting files are not to be located from the yum install
> version but I'm afraid other important items might also be missing to
> complete a full and successful implementation of OPENSIPS for production
> use?  Recommendations?  Should I abandon the yum install?  I do like the
> ease of the installation! lol  Is there a file to control MEM used and
> threads?
>
> 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

[OpenSIPS-Users] User_preferences vs db_alias for forwarding.

[Jeff Wilkie]

Using 1.10. Is there any issues using db_alias for forwarding as opposed to
user_preferences?

Thanks

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

Re: [OpenSIPS-Users] drouting

[Jeff Wilkie]

Sorry ...do_routing(1)

Thanks

Jeff Wilkie
USIP Communications

On Sep 20, 2016 8:45 AM, "Kirill Galinurov" <k.galinu...@gmail.com> wrote:

> Hello Bogdan. I try drouting() without any parameters.
>
> 2016-09-20 14:20 GMT+03:00 Bogdan-Andrei Iancu <bog...@opensips.org>:
> > Hello Kirill,
> >
> > I see the MI command succeeded, right? but the scrip do_routing() fails ?
> > what are the parameters you pass to do_routing() ?
> >
> > Best regards,
> >
> > Bogdan-Andrei Iancu
> > OpenSIPS Founder and Developer
> > http://www.opensips-solutions.com
> >
> >
> > On 19.09.2016 15:50, Kirill Galinurov wrote:
> >>
> >> Hi all I try to use drouting module.
> >>
> >> Sep 19 17:18:28 [37245] DBG:drouting:do_routing: using dr group 1,
> >> rule_idx 0, username 79632780099
> >> Sep 19 17:18:28 [37245] DBG:drouting:internal_check_rt: found rgid 1
> >> (rule list 0x7fe60616b800)
> >> Sep 19 17:18:28 [37245] INFO:drouting:do_routing: no destination for
> >> dr group 1, rule_idx 0, username 79632780099
> >> L_INFOdo_routing: No rules matching the URI
> >> In dr_rules
> >>   ruleid | groupid | prefix | timerec | priority | routeid | gwlist |
> >> attrs |  description
> >>
> >> +-++-+--+-+-
> ---+---+
> >>   0 | 1   | 7  | |1 | | #cr1   |
> >> | outgoing calls
> >>
> >> dr_carriers
> >>   id | carrierid | gwlist | flags | state | attrs | description
> >> +---++---+---+---+-
> >>   1 | cr1   | gw1;   | 0 | 2 | 0x2   | OUT
> >>
> >> dr_gateways
> >>   id | gwid | type |  address  | strip | pri_prefix | attrs |
> >> probe_mode | state | socket  | description
> >>
> >> +--+--+---+---++
> ---++---+-+-
> >>   1 | gw1  |1 | sip:out_voip.ru | 0 ||   |
> >>  0 | 0 | udp:XX.XX.XX.XX:5060 | out
> >>
> >> opensipsctl fifo dr_gw_status
> >> ID:: gw1 IP=XX.XXX.XXX.XX State=Active
> >>
> >> [root@sbc-msk opensips]# opensipsctl fifo dr_number_routing 1
> 79182220222
> >> Matched Prefix:: 7.
> >> What is wrong?
> >>
> >> ___
> >> 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
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] drouting

[Jeff Wilkie]

Use the group 1 you created in the command drouting(1) to send out using
group 1.

Thanks

Jeff Wilkie
USIP Communications

On Sep 20, 2016 8:45 AM, "Kirill Galinurov" <k.galinu...@gmail.com> wrote:

> Hello Bogdan. I try drouting() without any parameters.
>
> 2016-09-20 14:20 GMT+03:00 Bogdan-Andrei Iancu <bog...@opensips.org>:
> > Hello Kirill,
> >
> > I see the MI command succeeded, right? but the scrip do_routing() fails ?
> > what are the parameters you pass to do_routing() ?
> >
> > Best regards,
> >
> > Bogdan-Andrei Iancu
> > OpenSIPS Founder and Developer
> > http://www.opensips-solutions.com
> >
> >
> > On 19.09.2016 15:50, Kirill Galinurov wrote:
> >>
> >> Hi all I try to use drouting module.
> >>
> >> Sep 19 17:18:28 [37245] DBG:drouting:do_routing: using dr group 1,
> >> rule_idx 0, username 79632780099
> >> Sep 19 17:18:28 [37245] DBG:drouting:internal_check_rt: found rgid 1
> >> (rule list 0x7fe60616b800)
> >> Sep 19 17:18:28 [37245] INFO:drouting:do_routing: no destination for
> >> dr group 1, rule_idx 0, username 79632780099
> >> L_INFOdo_routing: No rules matching the URI
> >> In dr_rules
> >>   ruleid | groupid | prefix | timerec | priority | routeid | gwlist |
> >> attrs |  description
> >>
> >> +-++-+--+-+-
> ---+---+
> >>   0 | 1   | 7  | |1 | | #cr1   |
> >> | outgoing calls
> >>
> >> dr_carriers
> >>   id | carrierid | gwlist | flags | state | attrs | description
> >> +---++---+---+---+-
> >>   1 | cr1   | gw1;   | 0 | 2 | 0x2   | OUT
> >>
> >> dr_gateways
> >>   id | gwid | type |  address  | strip | pri_prefix | attrs |
> >> probe_mode | state | socket  | description
> >>
> >> +--+--+---+---++
> ---++---+-+-
> >>   1 | gw1  |1 | sip:out_voip.ru | 0 ||   |
> >>  0 | 0 | udp:XX.XX.XX.XX:5060 | out
> >>
> >> opensipsctl fifo dr_gw_status
> >> ID:: gw1 IP=XX.XXX.XXX.XX State=Active
> >>
> >> [root@sbc-msk opensips]# opensipsctl fifo dr_number_routing 1
> 79182220222
> >> Matched Prefix:: 7.
> >> What is wrong?
> >>
> >> ___
> >> 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
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Best method to add port to RECORD ROUTE, or should we?

[Jeff Wilkie]

Looking for the best method to add the port number to record route.
Upstream carrier is adding it in a response message when we do not have it
there once we send the INVITE.  The BYE from the carrier causes the problem
with the added port.  Since they modify the RR we hand them, OPENSIPS is
throwing an error on matching dialogs.  Granted, OPENSIPS seems smart
enough to still patch the dialog but I don't like excessive errors and
warnings showing up in my logs.

Bogdan, I've also read history of threads where you say it's not best to
fix it on our end when their SBC is not RFC compliantlol  So I'm ready
for that answer, also.

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

Re: [OpenSIPS-Users] OPENSIPS_CP DIALPLAN

[Jeff Wilkie]

So reading the following:

*Parameters*

*unescaped_string*

The string that is to be escaped.
*link_identifier*

The MySQL connection. If the link identifier is not specified, the last
link opened by mysql_connect
 is
assumed. If no such link is found, it will try to create one as if
mysql_connect

had
been called with no arguments. If no connection is found or established, an
E_WARNING level error is generated.

*Return Values*

Returns the escaped string, or FALSE on error.

*Errors/Exceptions*

Executing this function without a MySQL connection present will also emit
E_WARNING level PHP errors. Only execute this function with a valid MySQL
connection present.
I decided to remove the $link from each of the sections under the "modify"
portion of the code.  Assuming since in the code we call the DB connection
in the include statement anyway, the $link should already be established
and able to be assumed.  The code executes as expected with no warnings.
This does not tell me why is doesn't work yet but it does tell me that the
connection to the DB is established and working as expected along with the
code minus this one parameter.

I checked all of my patch versions and PDO with mysqli shouldn't be
required until 5.5 where I'm on 5.3.  Using PDO would have me rewriting
this entire section I would think.

Thanks

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

Re: [OpenSIPS-Users] OPENSIPS_CP DIALPLAN

[Jeff Wilkie]

php.i686   5.3.3-48.el6_8
@updates

php-cli.i686   5.3.3-48.el6_8
@updates

php-common.i6865.3.3-48.el6_8
@updates

php-gd.i6865.3.3-48.el6_8
@updates

php-mysql.i686 5.3.3-48.el6_8
@updates

php-pdo.i686   5.3.3-48.el6_8
@updates

php-pear.noarch1:1.9.4-5.el6
@base

php-xmlrpc.i6865.3.3-48.el6_8
@updates

*Installed packages, channel pear.php.net <http://pear.php.net>:*

=

*Package*   *Version* *State*

Archive_Tar   1.3.7   stable

Console_Getopt1.2.3   stable

Log   1.12.8  stable

MDB2  2.4.1   stable

MDB2_Driver_mysql 1.4.1   stable

PEAR  1.9.4   stable

Structures_Graph  1.0.4   stable

XML_RPC   1.5.4   stable

XML_Util  1.2.1   stable


freeradius-mysql.i686  2.2.6-6.el6_7
@updates

lua-sql-mysql.i686 2.1.1-7.el6
@epel

mysql.i686 5.1.73-7.el6
@base

mysql-devel.i686   5.1.73-7.el6
@base

mysql-libs.i6865.1.73-7.el6
@base

mysql-server.i686  5.1.73-7.el6
@base

php-mysql.i686 5.3.3-48.el6_8
@updates


I'll run those tests with mysqli.  I'm not currently using that though.
Will report today.

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, Aug 30, 2016 at 4:12 AM, Bogdan-Andrei Iancu <bog...@opensips.org>
wrote:

> Hi Jeff,
>
> We are getting closer :).
>
> I found this http://stackoverflow.com/questions/9014877/mysql-real-
> escape-string-error-despite-connecting-to-database-what-am-i-doing
>
> where the problem goes into mysql versus mysqli. I guess your MDB2 uses
> mysqli ?? Could you list all the php packages you have on your system along
> with all the php pears (pear list) ?
>
> Also, for testing purposes, try to change mysql_real_escape_string() into
> mysqli_real_escape_string()
>
>
> Thanks,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 30.08.2016 00:41, Jeff Wilkie wrote:
>
> Got this from a var dump on $link when i process if !is_resource.  Not
> sure if this actually provides any information that may help.  I'm digging
> online to see why the $link is not connecting as a resource in this portion
> for whatever reason:
>
> Warning: mysql_real_escape_string() expects parameter 2 to be resource,
> object given in /var/www/opensips_cp/web/tools/system/dialplan/dialplan.php
> on line 288
>
>
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OPENSIPS_CP DIALPLAN

[Jeff Wilkie]

I'll check the versions.  As for the flag field in dialplan,  I guess the
documents are wrong?  I show it as flag field in 1.10.x which I am
currently running

http://www.opensips.org/html/docs/modules/1.10.x/dialplan.html#id293827


Jeff

On Fri, Aug 26, 2016 at 5:24 AM, Bogdan-Andrei Iancu <bog...@opensips.org>
wrote:

> Hi Jeff,
>
> Maybe the version of MDB2 or MDB2::mysql php pear ?
>
> The CP versions are correlated with the OpenSIPS versions. The len field
> was moved to a flag field (in dialplan table) in opensips 1.11,
> corresponding to CP 6.0 (6.1 matches opensips 2.1 and CP trunk matches the
> 2.2)
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 26.08.2016 08:33, Jeff Wilkie wrote:
>
> I just loaded all the web directory content from git to test but the
> results are the same.  The config dir for dialplan are the same other than
> the toggle for 1 on text attributes.  Are there other files/dirs that would
> affect the dial plan section of CP?  Also, the git download does not
> include the changes from expression string length to expression flags (5.0
> cp)
>
> Jeff
>
>
> On Thu, Aug 25, 2016 at 5:11 PM, Bogdan-Andrei Iancu <bog...@opensips.org>
> wrote:
>
>> Hi Jeff,
>>
>> I run some test with the exact code on GITHUB (branch 5.0) and the edit
>> actually worked well (without any further changes).
>>
>> The $link is a variable that is initialized in the included file
>> lib/db_connect.php, so it valid (anyhow, it is used later for the actual
>> query, which works ;) ).
>>
>> Could you check if the return of mysql_real_escape_string() is actually
>> something valid or is it FALSE ?
>> http://stackoverflow.com/questions/3005135/mysql-real-escape
>> -string-just-makes-an-empty-string
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>>
>> On 25.08.2016 05:33, Jeff Wilkie wrote:
>>
>> If I modify the file /var/www/opensips_cp/web/
>> tools/system/dialplan/dialplan.php and comment out the following:
>>
>> //  if(get_magic_quotes_gpc()==0){
>>
>> //  $match_exp =
>> mysql_real_escape_string($match_exp, *$link*);
>>
>> //  }
>> The updates work fine.  I think noticed that the ref to *$link* sits
>> below this line in the "modify" section so I decided to remove the $link
>> ref in the above lines and then uncommented the lines leaving the modify
>> section like this
>>
>> if ($errors=="") {
>>
>> if(get_magic_quotes_gpc()==0){
>>
>> $match_exp =
>> mysql_real_escape_string($match_exp);
>>
>> }
>>
>> $sql = "SELECT * FROM ".$table.
>>
>> " WHERE dpid=" .$dpid. " AND match_exp='"
>> .$match_exp. "'".
>>
>> " AND id!=".$id;
>>
>> $resultset = *$link*->queryAll($sql);
>> Let me know if I've broken something as a result but this appears to have
>> corrected the problem I was having.  Unknown of any side effects currently
>> :)  Take a look and let me know your thoughts.
>> Jeff
>> On Wed, Aug 24, 2016 at 6:22 PM, Jeff Wilkie <jwil...@usipcom.com>
>> wrote:
>>>
>>> Here is what it looks like to my db when I create a DialPlan
>>>
>>>   20 Query SELECT * FROM dialplan WHERE dpid=36 AND match_exp='877'
>>>
>>>   20 Query PREPARE MDB2_STATEMENT_mysql_a9e5e113b009b855c4d690637965bc74
>>> FROM 'INSERT INTO dialplan\n (dpid, pr, match_op, match_exp,
>>> match_flags, subst_exp, \n repl_exp, attrs) VALUES \n (36, 0,1,
>>> \'877\',0,\'\',\'\',\'.30\')'
>>>
>>>   20 Prepare INSERT INTO dialplan
>>>
>>> (dpid, pr, match_op, match_exp, match_flags, subst_exp,
>>>
>>> repl_exp, attrs) VALUES
>>>
>>> (36, 0,1, '877',0,'','','.30')
>>>
>>>   20 Query EXECUTE MDB2_STATEMENT_mysql_a9e5e113b009b855c4d690637965bc74
>>>
>>>   20 Execute INSERT INTO dialplan
>>>
>>> (dpid, pr, match_op, match_exp, match_flags, subst_exp,
>>>
>>> repl_exp, attrs) VALUES
>>>
>>> (36, 0,1, '877',0,'','','.30')
>>> This is what happens when I edit that same DialPlan
>>>
>>>   23 Query selec

Re: [OpenSIPS-Users] OPENSIPS_CP DIALPLAN

[Jeff Wilkie]

Attempting to edit any of these fields produces these warnings and null
entries.

Warning: mysql_real_escape_string() expects parameter 2 to be resource,
object given in /var/www/opensips_cp/web/tools/system/dialplan/dialplan.php
on line 292 Warning: mysql_real_escape_string() expects parameter 2 to be
resource, object given in
/var/www/opensips_cp/web/tools/system/dialplan/dialplan.php on line 320
Warning: mysql_real_escape_string() expects parameter 2 to be resource,
object given in /var/www/opensips_cp/web/tools/system/dialplan/dialplan.php
on line 322

All three of these errors reference the $link resource pulled from the lib
dir.

"pear/MDB2", version 2.4.1

I just updated all the others but still get the same error.

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

Re: [OpenSIPS-Users] OPENSIPS_CP DIALPLAN

[Jeff Wilkie]

I'll check the versions.  As for the flag field in dialplan,  I guess the
documents are wrong?  I show it as flag field in 1.10.x which I am
currently running

http://www.opensips.org/html/docs/modules/1.10.x/dialplan.html#id293827

Thanks

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

Re: [OpenSIPS-Users] OPENSIPS_CP DIALPLAN

[Jeff Wilkie]

I just loaded all the web directory content from git to test but the
results are the same.  The config dir for dialplan are the same other than
the toggle for 1 on text attributes.  Are there other files/dirs that would
affect the dial plan section of CP?  Also, the git download does not
include the changes from expression string length to expression flags (5.0
cp)

Jeff


On Thu, Aug 25, 2016 at 5:11 PM, Bogdan-Andrei Iancu <bog...@opensips.org>
wrote:

> Hi Jeff,
>
> I run some test with the exact code on GITHUB (branch 5.0) and the edit
> actually worked well (without any further changes).
>
> The $link is a variable that is initialized in the included file
> lib/db_connect.php, so it valid (anyhow, it is used later for the actual
> query, which works ;) ).
>
> Could you check if the return of mysql_real_escape_string() is actually
> something valid or is it FALSE ?
> http://stackoverflow.com/questions/3005135/mysql-real-
> escape-string-just-makes-an-empty-string
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 25.08.2016 05:33, Jeff Wilkie wrote:
>
> If I modify the file 
> /var/www/opensips_cp/web/tools/system/dialplan/dialplan.php
> and comment out the following:
>
> //  if(get_magic_quotes_gpc()==0){
>
>
> //  $match_exp = 
> mysql_real_escape_string($match_exp,
> *$link*);
>
> //  }
>
> The updates work fine.  I think noticed that the ref to *$link* sits
> below this line in the "modify" section so I decided to remove the $link
> ref in the above lines and then uncommented the lines leaving the modify
> section like this
>
> if ($errors=="") {
>
> if(get_magic_quotes_gpc()==0){
>
>
> $match_exp = mysql_real_escape_string($
> match_exp);
>
> }
>
>
> $sql = "SELECT * FROM ".$table.
>
> " WHERE dpid=" .$dpid. " AND match_exp='"
> .$match_exp. "'".
>
> " AND id!=".$id;
>
> $resultset = *$link*->queryAll($sql);
>
>
> Let me know if I've broken something as a result but this appears to have
> corrected the problem I was having.  Unknown of any side effects currently
> :)  Take a look and let me know your thoughts.
>
> Jeff
>
>
>
> On Wed, Aug 24, 2016 at 6:22 PM, Jeff Wilkie <jwil...@usipcom.com> wrote:
>
>> Here is what it looks like to my db when I create a DialPlan
>>
>>   20 Query SELECT * FROM dialplan WHERE dpid=36 AND match_exp='877'
>>
>>   20 Query PREPARE MDB2_STATEMENT_mysql_a9e5e113b009b855c4d690637965bc74
>> FROM 'INSERT INTO dialplan\n (dpid, pr, match_op, match_exp,
>> match_flags, subst_exp, \n repl_exp, attrs) VALUES \n (36, 0,1,
>> \'877\',0,\'\',\'\',\'.30\')'
>>
>>   20 Prepare INSERT INTO dialplan
>>
>> (dpid, pr, match_op, match_exp, match_flags, subst_exp,
>>
>> repl_exp, attrs) VALUES
>>
>> (36, 0,1, '877',0,'','','.30')
>>
>>   20 Query EXECUTE MDB2_STATEMENT_mysql_a9e5e113b009b855c4d690637965bc74
>>
>>   20 Execute INSERT INTO dialplan
>>
>> (dpid, pr, match_op, match_exp, match_flags, subst_exp,
>>
>> repl_exp, attrs) VALUES
>>
>> (36, 0,1, '877',0,'','','.30')
>>
>> This is what happens when I edit that same DialPlan
>>
>>   23 Query select * from dialplan where id='9030'
>>
>>   23 Quit
>>
>>   24 Query SELECT * FROM dialplan WHERE dpid=36 AND match_exp='' AND
>> id!=9030
>>
>>   24 Query PREPARE MDB2_STATEMENT_mysql_880efa45d78ebff7cbf5f617428df4d2
>> FROM 'UPDATE dialplan SET dpid=36, pr = 0, match_op= 1, match_exp =\'\',
>> match_flags=0, subst_exp = \'\', repl_exp=\'\', attrs= \'.30\' WHERE
>> id=9030'
>>
>>   24 Prepare UPDATE dialplan SET dpid=36, pr = 0, match_op= 1, match_exp
>> ='', match_flags=0, subst_exp = '', repl_exp='', attrs= '.30' WHERE id=9030
>>
>>   24 Query EXECUTE MDB2_STATEMENT_mysql_880efa45d78ebff7cbf5f617428df4d2
>>
>>   24 Execute UPDATE dialplan SET dpid=36, pr = 0, match_op= 1, match_exp
>> ='', match_flags=0, subst_exp = '', repl_exp='', attrs= '.30' WHERE id=9030
>>
>>   24 Query DEALLOCATE PREPARE MDB2_STATEMENT_mysql_880efa45d
>> 78ebff7cbf5f617428df4d2
>>
>>   24 Quit
>>
>>
>> You can see that the container for match_ex is not getting passed to the
>> '24' SELECT statement which ends in a 0 res

Re: [OpenSIPS-Users] OPENSIPS_CP DIALPLAN

[Jeff Wilkie]

When using

$match_exp = mysql_real_escape_string($match_exp, *$link*);

I get NULL with var_dump

When using

$match_exp = mysql_real_escape_string($match_exp);

I get with a var_dump

string(10) "^\\+1907.*"

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

Re: [OpenSIPS-Users] OPENSIPS_CP DIALPLAN

[Jeff Wilkie]

Disregard the statement I made about the select statement. This is where
you're checking for duplicates. But I do notice the regex is not present
here either.

Thanks

Jeff Wilkie
USIP Communications

On Aug 24, 2016 6:22 PM, "Jeff Wilkie" <jwil...@usipcom.com> wrote:

> Here is what it looks like to my db when I create a DialPlan
>
>   20 Query SELECT * FROM dialplan WHERE dpid=36 AND match_exp='877'
>
>   20 Query PREPARE MDB2_STATEMENT_mysql_a9e5e113b009b855c4d690637965bc74
> FROM 'INSERT INTO dialplan\n (dpid, pr, match_op, match_exp, match_flags,
> subst_exp, \n repl_exp, attrs) VALUES \n (36, 0,1,
> \'877\',0,\'\',\'\',\'.30\')'
>
>   20 Prepare INSERT INTO dialplan
>
> (dpid, pr, match_op, match_exp, match_flags, subst_exp,
>
> repl_exp, attrs) VALUES
>
> (36, 0,1, '877',0,'','','.30')
>
>   20 Query EXECUTE MDB2_STATEMENT_mysql_a9e5e113b009b855c4d690637965bc74
>
>   20 Execute INSERT INTO dialplan
>
> (dpid, pr, match_op, match_exp, match_flags, subst_exp,
>
> repl_exp, attrs) VALUES
>
> (36, 0,1, '877',0,'','','.30')
>
> This is what happens when I edit that same DialPlan
>
>   23 Query select * from dialplan where id='9030'
>
>   23 Quit
>
>   24 Query SELECT * FROM dialplan WHERE dpid=36 AND match_exp='' AND
> id!=9030
>
>   24 Query PREPARE MDB2_STATEMENT_mysql_880efa45d78ebff7cbf5f617428df4d2
> FROM 'UPDATE dialplan SET dpid=36, pr = 0, match_op= 1, match_exp =\'\',
> match_flags=0, subst_exp = \'\', repl_exp=\'\', attrs= \'.30\' WHERE
> id=9030'
>
>   24 Prepare UPDATE dialplan SET dpid=36, pr = 0, match_op= 1, match_exp
> ='', match_flags=0, subst_exp = '', repl_exp='', attrs= '.30' WHERE id=9030
>
>   24 Query EXECUTE MDB2_STATEMENT_mysql_880efa45d78ebff7cbf5f617428df4d2
>
>   24 Execute UPDATE dialplan SET dpid=36, pr = 0, match_op= 1, match_exp
> ='', match_flags=0, subst_exp = '', repl_exp='', attrs= '.30' WHERE id=9030
>
>   24 Query DEALLOCATE PREPARE MDB2_STATEMENT_mysql_
> 880efa45d78ebff7cbf5f617428df4d2
>
>   24 Quit
>
>
> You can see that the container for match_ex is not getting passed to the
> '24' SELECT statement which ends in a 0 results query apparently.
>
>
> Thanks
>
> Jeff
>
> On Wed, Aug 24, 2016 at 5:30 PM, Jeff Wilkie <jwil...@usipcom.com> wrote:
>
>> Yes.  After any edits followed by a save with the attribute field active
>> as text causes "Matching Regular Expression" to be deleted.
>>
>> Thanks
>>
>> Jeff
>>
>> On Wed, Aug 24, 2016 at 5:15 PM, Bogdan-Andrei Iancu <bog...@opensips.org
>> > wrote:
>>
>>> Jeff,
>>>
>>> You mean "Matching Regular Expression", right ? upon performing an edit
>>> + save where you only changed the attrs, the "Matching Regular
>>> Expression" gets to empty ?
>>>
>>> Regards,
>>>
>>> Bogdan-Andrei Iancu
>>> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>>>
>>> On 24.08.2016 23:25, Jeff Wilkie wrote:
>>>
>>> Ok.  The value now displays but if you modify the value and hit save, it
>>> kills the regex value upon saving.  Also, you cannot add the regex value
>>> back into the row.  All other values appear to be kept.
>>>
>>> Thanks
>>>
>>> Jeff
>>>
>>> On Wed, Aug 24, 2016 at 11:35 AM, Bogdan-Andrei Iancu <
>>> bog...@opensips.org> wrote:
>>>
>>>> Hi Jeff,
>>>>
>>>> I spotted the issue and fixed it on GIT repo. Please give it a try and
>>>> let me know if it works for you too.
>>>>
>>>> Thanks and regards,
>>>>
>>>> Bogdan-Andrei Iancu
>>>> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>>>>
>>>> On 24.08.2016 17:46, Jeff Wilkie wrote:
>>>>
>>>> Yes, The text box is there but when you place a value in a preexisting
>>>> dial plan, the result in the DB is just the value in the text attribute
>>>> field with no dial plan information.  By editing or adding an attribute it
>>>> kills the rest of the dial plan that you were editing and you cannot add
>>>> the dial plan information back in via the CP as long as an attribute in
>>>> text form is added.  The same does not happen if using check box.  I can
>>>> provide pics if you'd like.  The only var changed is the
>>>>
>>>> $dialplan_attributes_mode = 1
>>>>
>>>> Jeff Wilkie
>>>> Chief Technology Officer
>>>> US IP Communications 919.29

Re: [OpenSIPS-Users] OPENSIPS_CP DIALPLAN

[Jeff Wilkie]

Yes.  After any edits followed by a save with the attribute field active as
text causes "Matching Regular Expression" to be deleted.

Thanks

Jeff

On Wed, Aug 24, 2016 at 5:15 PM, Bogdan-Andrei Iancu <bog...@opensips.org>
wrote:

> Jeff,
>
> You mean "Matching Regular Expression", right ? upon performing an edit +
> save where you only changed the attrs, the "Matching Regular Expression"
> gets to empty ?
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 24.08.2016 23:25, Jeff Wilkie wrote:
>
> Ok.  The value now displays but if you modify the value and hit save, it
> kills the regex value upon saving.  Also, you cannot add the regex value
> back into the row.  All other values appear to be kept.
>
> Thanks
>
> Jeff
>
> On Wed, Aug 24, 2016 at 11:35 AM, Bogdan-Andrei Iancu <bog...@opensips.org
> > wrote:
>
>> Hi Jeff,
>>
>> I spotted the issue and fixed it on GIT repo. Please give it a try and
>> let me know if it works for you too.
>>
>> Thanks and regards,
>>
>> Bogdan-Andrei Iancu
>> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>>
>> On 24.08.2016 17:46, Jeff Wilkie wrote:
>>
>> Yes, The text box is there but when you place a value in a preexisting
>> dial plan, the result in the DB is just the value in the text attribute
>> field with no dial plan information.  By editing or adding an attribute it
>> kills the rest of the dial plan that you were editing and you cannot add
>> the dial plan information back in via the CP as long as an attribute in
>> text form is added.  The same does not happen if using check box.  I can
>> provide pics if you'd like.  The only var changed is the
>>
>> $dialplan_attributes_mode = 1
>>
>> 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 Wed, Aug 24, 2016 at 5:20 AM, Bogdan-Andrei Iancu <bog...@opensips.org
>> > wrote:
>>>
>>> Hi Jeff, You mean you do not get the Attributes text area at all in the
>>> Edit section ? Regards,
>>>
>>> Bogdan-Andrei Iancu
>>> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>>>
>>> On 23.08.2016 00:56, Jeff Wilkie wrote:
>>>
>>> New small issue with DIALPLAN in the CP.  Running OSIPS 1.10 with CP 5.0
>>> It appears that when modifying the CP for Dialplan attributes as text,
>>> they do not appear in the edit section once applied.  The attributes do
>>> show up in the view list of dial plans but if you go back to edit the attrs
>>> again, they are not there.  I dot not have the same problem when using
>>> attrs as checkboxes.  Is there more code in the local files that require
>>> editing to display these values?  Also, if an entry in the Dialplan was
>>> once a checkbox value but I've not converted the mode to text, the value
>>> does not show up in the text box to be edited.
>>>
>>> # Attention : advanced options !!
>>>
>>>  //database tables
>>>
>>>  $config->table_dialplan = "dialplan";
>>>
>>>  $config->results_per_page = 20;
>>>
>>>  $config->results_page_range = 5;
>>>
>>>  $config->attrs_cb=array(
>>>
>>> // name , description
>>>
>>> array("a","Descr a"),
>>>
>>> array("b","Descr b"),
>>>
>>> array("c","Descr c"),
>>>
>>> array("d","Descr d"),
>>>
>>> array("e","Descr e"),
>>>
>>> array("f","Descr f"),
>>>
>>> );
>>>
>>>  $config->cb_per_row = 3;
>>>
>>>  $talk_to_this_assoc_id = 1 ;
>>>
>>> // Dialplan - Add/Edit new Translation Rule - Attributes input type
>>>
>>> // 0 - checkboxes
>>>
>>> // 1 - text
>>>
>>> $dialplan_attributes_mode = 1  ;
>>>
>>> ?>
>>> 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] OPENSIPS_CP DIALPLAN

[Jeff Wilkie]

Ok.  The value now displays but if you modify the value and hit save, it
kills the regex value upon saving.  Also, you cannot add the regex value
back into the row.  All other values appear to be kept.

Thanks

Jeff

On Wed, Aug 24, 2016 at 11:35 AM, Bogdan-Andrei Iancu <bog...@opensips.org>
wrote:

> Hi Jeff,
>
> I spotted the issue and fixed it on GIT repo. Please give it a try and let
> me know if it works for you too.
>
> Thanks and regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 24.08.2016 17:46, Jeff Wilkie wrote:
>
> Yes, The text box is there but when you place a value in a preexisting
> dial plan, the result in the DB is just the value in the text attribute
> field with no dial plan information.  By editing or adding an attribute it
> kills the rest of the dial plan that you were editing and you cannot add
> the dial plan information back in via the CP as long as an attribute in
> text form is added.  The same does not happen if using check box.  I can
> provide pics if you'd like.  The only var changed is the
>
> $dialplan_attributes_mode = 1
>
> 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 Wed, Aug 24, 2016 at 5:20 AM, Bogdan-Andrei Iancu <bog...@opensips.org>
> wrote:
>
>> Hi Jeff,
>>
>> You mean you do not get the Attributes text area at all in the Edit
>> section ?
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>>
>> On 23.08.2016 00:56, Jeff Wilkie wrote:
>>
>> New small issue with DIALPLAN in the CP.  Running OSIPS 1.10 with CP 5.0
>> It appears that when modifying the CP for Dialplan attributes as text,
>> they do not appear in the edit section once applied.  The attributes do
>> show up in the view list of dial plans but if you go back to edit the attrs
>> again, they are not there.  I dot not have the same problem when using
>> attrs as checkboxes.  Is there more code in the local files that require
>> editing to display these values?  Also, if an entry in the Dialplan was
>> once a checkbox value but I've not converted the mode to text, the value
>> does not show up in the text box to be edited.
>>
>> # Attention : advanced options !!
>>
>>  //database tables
>>
>>  $config->table_dialplan = "dialplan";
>>
>>  $config->results_per_page = 20;
>>
>>  $config->results_page_range = 5;
>>
>>  $config->attrs_cb=array(
>>
>> // name , description
>>
>> array("a","Descr a"),
>>
>> array("b","Descr b"),
>>
>> array("c","Descr c"),
>>
>> array("d","Descr d"),
>>
>> array("e","Descr e"),
>>
>> array("f","Descr f"),
>>
>> );
>>
>>  $config->cb_per_row = 3;
>>
>>  $talk_to_this_assoc_id = 1 ;
>>
>> // Dialplan - Add/Edit new Translation Rule - Attributes input type
>>
>> // 0 - checkboxes
>>
>> // 1 - text
>>
>> $dialplan_attributes_mode = 1  ;
>>
>> ?>
>> 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] OPENSIPS_CP DIALPLAN

[Jeff Wilkie]

Yes, The text box is there but when you place a value in a preexisting dial
plan, the result in the DB is just the value in the text attribute field
with no dial plan information.  By editing or adding an attribute it kills
the rest of the dial plan that you were editing and you cannot add the dial
plan information back in via the CP as long as an attribute in text form is
added.  The same does not happen if using check box.  I can provide pics if
you'd like.  The only var changed is the

$dialplan_attributes_mode = 1

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 Wed, Aug 24, 2016 at 5:20 AM, Bogdan-Andrei Iancu <bog...@opensips.org>
wrote:

> Hi Jeff,
>
> You mean you do not get the Attributes text area at all in the Edit
> section ?
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 23.08.2016 00:56, Jeff Wilkie wrote:
>
> New small issue with DIALPLAN in the CP.  Running OSIPS 1.10 with CP 5.0
>
> It appears that when modifying the CP for Dialplan attributes as text,
> they do not appear in the edit section once applied.  The attributes do
> show up in the view list of dial plans but if you go back to edit the attrs
> again, they are not there.  I dot not have the same problem when using
> attrs as checkboxes.  Is there more code in the local files that require
> editing to display these values?  Also, if an entry in the Dialplan was
> once a checkbox value but I've not converted the mode to text, the value
> does not show up in the text box to be edited.
>
> # Attention : advanced options !!
>
>
>
>  //database tables
>
>  $config->table_dialplan = "dialplan";
>
>  $config->results_per_page = 20;
>
>  $config->results_page_range = 5;
>
>
>  $config->attrs_cb=array(
>
> // name , description
>
> array("a","Descr a"),
>
> array("b","Descr b"),
>
> array("c","Descr c"),
>
> array("d","Descr d"),
>
> array("e","Descr e"),
>
> array("f","Descr f"),
>
> );
>
>  $config->cb_per_row = 3;
>
>  $talk_to_this_assoc_id = 1 ;
>
>
> // Dialplan - Add/Edit new Translation Rule - Attributes input type
>
> // 0 - checkboxes
>
> // 1 - text
>
> $dialplan_attributes_mode = 1  ;
>
>
> ?>
>
>
>
> 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

[OpenSIPS-Users] OPENSIPS_CP DIALPLAN

[Jeff Wilkie]

New small issue with DIALPLAN in the CP.  Running OSIPS 1.10 with CP 5.0

It appears that when modifying the CP for Dialplan attributes as text, they
do not appear in the edit section once applied.  The attributes do show up
in the view list of dial plans but if you go back to edit the attrs again,
they are not there.  I dot not have the same problem when using attrs as
checkboxes.  Is there more code in the local files that require editing to
display these values?  Also, if an entry in the Dialplan was once a
checkbox value but I've not converted the mode to text, the value does not
show up in the text box to be edited.

# Attention : advanced options !!



 //database tables

 $config->table_dialplan = "dialplan";

 $config->results_per_page = 20;

 $config->results_page_range = 5;


 $config->attrs_cb=array(

// name , description

array("a","Descr a"),

array("b","Descr b"),

array("c","Descr c"),

array("d","Descr d"),

array("e","Descr e"),

array("f","Descr f"),

);

 $config->cb_per_row = 3;

 $talk_to_this_assoc_id = 1 ;


// Dialplan - Add/Edit new Translation Rule - Attributes input type

// 0 - checkboxes

// 1 - text

$dialplan_attributes_mode = 1  ;


?>



Jeff
___
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

[Jeff Wilkie]

>From the CP gateway web GUI,

>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

But I am able to enable the gateway from both interfaces if they are
disabledthat's what's weird and why I started to look into the php to
see if there were errors but it appears to be deeper than that.  The one
thing I do notice is that to enable the gateways if they are disabled (from
the GUI drouting/gateways) after I've selected enable and hit okay, I then
have to hit "apply changes to server" for it to take place.

Testing like this:

# opensipsctl fifo dr_gw_status 2

Enabled:: yes

# opensipsctl fifo dr_gw_status 2 0

# opensipsctl fifo dr_gw_status 2

Enabled:: no

Then go to the GUI.  The red indicator shows GW2 was disabled.

I click on the red status, it asks me to enable, which I do.  After which,
the GUI shows no update of being enabled nor does ctl when I check its
status.

# opensipsctl fifo dr_gw_status 2

Enabled:: no

I then hit "apply changes to server" and update the page which then turns
the indicator green.  CTL now shows enabled.

# opensipsctl fifo dr_gw_status 2

Enabled:: yes

The same process does not work for disabling it though, only enabling.


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 Fri, Jun 10, 2016 at 6:34 AM, Bogdan-Andrei Iancu <bog...@opensips.org>
wrote:

> Hi Jeff,
>
> So, from CP, using the FIFO backend, the enabling works, but the disabling
> doesn't ?
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 09.06.2016 22:30, Jeff Wilkie wrote:
>
> 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 <http://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 <
> <bog...@opensips.org>bog...@opensips.org> 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 oth

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

[Jeff Wilkie]

I have a  more detailed message awaiting approval, but the answer is yes to
the question.  Although I do have to hit "Apply changes to server" before
it takes place.

Thanks

Jeff Wilkie

On Fri, Jun 10, 2016 at 6:34 AM, Bogdan-Andrei Iancu <bog...@opensips.org>
wrote:

> Hi Jeff,
>
> So, from CP, using the FIFO backend, the enabling works, but the disabling
> doesn't ?
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 09.06.2016 22:30, Jeff Wilkie wrote:
>
> 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 <http://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 <
> <bog...@opensips.org>bog...@opensips.org> 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>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 attachm

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

[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 <http://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 <bog...@opensips.org>
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>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>bog...@opensips.org> wrote:
>>
>>> Hi Jeff,
>>>
>>> What OpenSIPS Con

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

[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" <bog...@opensips.org> 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)
>>>
>>> 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*
>&g

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

[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 <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>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] Opensips CP DROUTING GATEWAY enable/disable issue

[Jeff Wilkie]

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

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

[Jeff Wilkie]

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

Re: [OpenSIPS-Users] Rely forbidden

[Jeff Wilkie]

Do you have a link to provide your config and confirm what modules are
compiled and loaded from install?  Receiving calls from outside to your
OPENSIPS should be straight forward.  I'm not sure how your RURI even
routes to you if the upstream provider is a real provider and not in a test
lab.  sip:opensips@localhost:5060 is very non specific and local.  I'm
assuming your trying to call to sip:0972550428@10.7.1.68.

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 Fri, Apr 15, 2016 at 6:03 AM, Francjos <35...@heb.be> wrote:

> Here is the output of :ngrep -d eth0 -t -W byline "$1" port 5060 -q
> Can you help me to understand the problem and how to resolve it?
>
> ^Croot@front-2:~# 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/04/15 09:59:46.445723 91.121.129.159:5060 -> 10.0.0.5:5060
> INVITE sip:opensips@localhost:5060;transport=udp SIP/2.0.
> Call-ID: 02023-ii-1b75f5ca-75e715...@sip3.ovh.fr.
> Contact: .
> Content-Type: application/sdp.
> CSeq: 426731554 INVITE.
> From: "003228800555"
> <sip:003228800...@sip3.ovh.fr;user=phone>;tag=02023-LB-1b75f5cb-77f5c7f17.
> Max-Forwards: 27.
> Record-Route: <sip:91.121.129.159:5060;lr>.
> To: <sip:0972550428@10.7.1.68;user=phone>.
> Via: SIP/2.0/UDP 91.121.129.159:5060
> ;branch=z9hG4bK-UXTN-2667384e-065369b8.
> Allow:
>
> REFER,INVITE,NOTIFY,ACK,UPDATE,OPTIONS,REGISTER,SUBSCRIBE,NOTIFY,CANCEL,BYE,PRACK.
> User-Agent: Cirpack/v4.70 (gw_sip).
> Content-Length: 315.
> .
> v=0.
> o=cp10 146071438652 146071438652 IN IP4 10.7.16.156.
> s=SIP Call.
> c=IN IP4 91.121.129.144.
> t=0 0.
> m=audio 31298 RTP/AVP 18 0 8 101.
> b=AS:21.
> a=rtpmap:18 G729/8000/1.
> a=fmtp:18 annexb=no.
> a=rtpmap:0 PCMU/8000/1.
> a=rtpmap:8 PCMA/8000/1.
> a=rtpmap:101 telephone-event/8000.
> a=fmtp:101 0-15.
> a=ptime:30.
> a=sendrecv.
>
>
> U 2016/04/15 09:59:46.446223 10.0.0.5:5060 -> 91.121.129.159:5060
> SIP/2.0 500 Service full.
> Call-ID: 02023-ii-1b75f5ca-75e715...@sip3.ovh.fr.
> CSeq: 426731554 INVITE.
> From: "003228800555"
> <sip:003228800...@sip3.ovh.fr;user=phone>;tag=02023-LB-1b75f5cb-77f5c7f17.
> To:
> <sip:0972550428@10.7.1.68
> ;user=phone>;tag=c97b4d1cb1f3d0da549e06a8d482ef63.57bb.
> Via: SIP/2.0/UDP 91.121.129.159:5060
> ;branch=z9hG4bK-UXTN-2667384e-065369b8.
> Server: OpenSIPS (2.1.2 (x86_64/linux)).
> Content-Length: 0.
> .
>
>
> U 2016/04/15 09:59:46.459264 91.121.129.159:5060 -> 10.0.0.5:5060
> ACK sip:opensips@localhost:5060;transport=udp SIP/2.0.
> Call-ID: 02023-ii-1b75f5ca-75e715...@sip3.ovh.fr.
> CSeq: 426731554 ACK.
> From: "003228800555"
> <sip:003228800...@sip3.ovh.fr;user=phone>;tag=02023-LB-1b75f5cb-77f5c7f17.
> Max-Forwards: 27.
> To:
> <sip:0972550428@10.7.1.68
> ;user=phone>;tag=c97b4d1cb1f3d0da549e06a8d482ef63.57bb.
> Via: SIP/2.0/UDP 91.121.129.159:5060
> ;branch=z9hG4bK-UXTN-2667384e-065369b8.
> Content-Length: 0.
> .
>
>
> U 2016/04/15 09:59:48.514025 91.121.129.159:5060 -> 10.0.0.5:5060
> INVITE sip:opensips@localhost:5060;transport=udp SIP/2.0.
> Call-ID: 25873-ax-1b75f716-0d45b7...@sip3.ovh.fr.
> Contact: .
> Content-Type: application/sdp.
> CSeq: 426731844 INVITE.
> From: "003228800555"
> <sip:003228800...@sip3.ovh.fr;user=phone>;tag=25873-BW-1b75f717-40cd751b1.
> Max-Forwards: 27.
> Record-Route: <sip:91.121.129.159:5060;lr>.
> To: <sip:0972550428@10.7.1.68;user=phone>.
> Via: SIP/2.0/UDP 91.121.129.159:5060
> ;branch=z9hG4bK-ZRXL-26673a19-1004fd6f.
> Allow:
>
> REFER,INVITE,NOTIFY,ACK,UPDATE,OPTIONS,REGISTER,SUBSCRIBE,NOTIFY,CANCEL,BYE,PRACK.
> User-Agent: Cirpack/v4.70 (gw_sip).
> Content-Length: 315.
> .
> v=0.
> o=cp10 146071438849 146071438849 IN IP4 10.7.16.156.
> s=SIP Call.
> c=IN IP4 91.121.129.145.
> t=0 0.
> 

Re: [OpenSIPS-Users] Rely forbidden

[Jeff Wilkie]

Can you use this to capture the signaling for reading and relaying here?
I'm assuming you are only listening on port 5060.  Your details on the
packets do not help with a resolution.

ngrep -d eth0 -t -W byline "$1" port 5060 -q

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, Apr 14, 2016 at 10:28 AM, Francjos <35...@heb.be> wrote:

> When i analyse the output of the command sngrep, there is something i don't
> understand,
> the sip to = 0972550428@10.7.1.68
> I recognize the 0972550428, but don't recognize the other part. What that
> mean?
> Since yesterday i'm searching why the INVITE is rejected in Opensips.
> Can somebody help please?
>
>
>
> --
> View this message in context:
> http://opensips-open-sip-server.1449251.n2.nabble.com/Rely-forbidden-tp7602608p7602616.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