date:20160824

Re: [OpenSIPS-Users] OPENSIPS_CP DIALPLAN

2016-08-24 Thread Jeff Wilkie

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

>>>

Re: [OpenSIPS-Users] OPENSIPS_CP DIALPLAN

2016-08-24 Thread 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"  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  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 > > 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 <
 b

Re: [OpenSIPS-Users] OPENSIPS_CP DIALPLAN

2016-08-24 Thread Jeff Wilkie

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  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 
> 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 Dialpla

Re: [OpenSIPS-Users] OPENSIPS_CP DIALPLAN

2016-08-24 Thread 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 
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  > 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 > > 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

2016-08-24 Thread Bogdan-Andrei Iancu


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 Developer
http://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 
mailto: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 Developer
http://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
mailto: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 Developer
http://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 list
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



___
Users mailing list
Users@lists.opensips.

Re: [OpenSIPS-Users] OPENSIPS_CP DIALPLAN

2016-08-24 Thread 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 
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 
> 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

2016-08-24 Thread Bogdan-Andrei Iancu


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 Developer
http://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 
mailto: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 Developer
http://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 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] Too many warnings in opensips log

2016-08-24 Thread Ramachandran, Agalya (Contractor)

Hi team,

Am using opensips 2.1.4 version and trying to do load test. When running the 
test cases, am getting too many warnings in OpenSIPS log.
These warnings are coming continuously and its more than 2 page in log file.
Below are the warnings.

Aug 24 15:27:34 sturn-test /usr/local/sbin/opensips[12015]: 
WARNING:core:handle_timer_job: utimer job  has a 3945 us delay 
in execution
Aug 24 15:27:34 sturn-test /usr/local/sbin/opensips[12015]: 
WARNING:core:handle_timer_job: utimer job  has a 3945 us delay 
in execution
Aug 24 15:27:34 sturn-test /usr/local/sbin/opensips[12015]: 
WARNING:core:handle_timer_job: utimer job  has a 3945 us delay 
in execution
Aug 24 15:27:34 sturn-test /usr/local/sbin/opensips[12015]: 
WARNING:core:handle_timer_job: utimer job  has a 3945 us delay 
in execution
Aug 24 15:27:34 sturn-test /usr/local/sbin/opensips[12015]: 
WARNING:core:handle_timer_job: utimer job  has a 3945 us delay 
in execution
Aug 24 15:27:34 sturn-test /usr/local/sbin/opensips[12015]: 
WARNING:core:handle_timer_job: utimer job  has a 3945 us delay 
in execution

When I get this Warning, calls are getting failed.
Why am getting this warning and what could be done to avoid it?

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

Re: [OpenSIPS-Users] OPENSIPS_CP DIALPLAN

2016-08-24 Thread 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 
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] dispatcher module call limit

2016-08-24 Thread Bogdan-Andrei Iancu


OK, in this case you should use the dialog module with call profile support.

Regards,

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

On 24.08.2016 13:11, Owais Ahmad wrote:

Hello Bogdan,

I should have specified earlier that I want to limit the *concurrent 
*calls per destination.

I don't think ratelimit can be used for that.

I want to have calls get dropped with a 503 at the dispatcher server 
if a defined concurrent call limit is met; not traversing any nodes 
deeper down the network.




On Wed, Aug 24, 2016 at 2:22 PM, Bogdan-Andrei Iancu 
mailto:bog...@opensips.org>> wrote:


Hi Owais,

The dispatcher module is just dispatching traffic between multiple
destinations. The restrict (CPS limitation) traffic use the
ratelimit module:
http://www.opensips.org/html/docs/modules/2.2.x/ratelimit.html


Regards,

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

On 24.08.2016 08:16, Owais Ahmad wrote:

Hi guys,
Can we use dispatcher module to restrict the number of INVITEs
relayed to a specific destination?
Regards,
Owais

___
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] dispatcher module call limit

2016-08-24 Thread Owais Ahmad

Hello Bogdan,

I should have specified earlier that I want to limit the *concurrent *calls
per destination.
I don't think ratelimit can be used for that.

I want to have calls get dropped with a 503 at the dispatcher server if a
defined concurrent call limit is met; not traversing any nodes deeper down
the network.

On Wed, Aug 24, 2016 at 2:22 PM, Bogdan-Andrei Iancu 
wrote:

> Hi Owais,
>
> The dispatcher module is just dispatching traffic between multiple
> destinations. The restrict (CPS limitation) traffic use the ratelimit
> module:
> http://www.opensips.org/html/docs/modules/2.2.x/ratelimit.html
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 24.08.2016 08:16, Owais Ahmad wrote:
>
> Hi guys,
>
> Can we use dispatcher module to restrict the number of INVITEs relayed to
> a specific destination?
>
> Regards,
> Owais
>
>
> ___
> 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] dispatcher module call limit

2016-08-24 Thread Bogdan-Andrei Iancu


Hi Owais,

The dispatcher module is just dispatching traffic between multiple 
destinations. The restrict (CPS limitation) traffic use the ratelimit 
module:

http://www.opensips.org/html/docs/modules/2.2.x/ratelimit.html

Regards,

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

On 24.08.2016 08:16, Owais Ahmad wrote:

Hi guys,

Can we use dispatcher module to restrict the number of INVITEs relayed 
to a specific destination?


Regards,
Owais


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


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

Re: [OpenSIPS-Users] OPENSIPS_CP DIALPLAN

2016-08-24 Thread Bogdan-Andrei Iancu


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 Developer
http://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 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] accessing to branch data

2016-08-24 Thread Чалков Артём

Ok, i found my mistake with 2nd part (deleting branches) - it seems like i cant delete branches from failure_route by $T_branch_idx because outside branch_route it always have value 0. Okay, so, can i somehow delete "expired" branches (to not reach branch limit. yes, i cnow that i can extend the limit, but i think its a bad idea) or its totally impossible?Also, first part of my question (about accessing data) is still actual.23.08.2016, 17:21, "Чалков Артём" :Hi all!Could you tell me how can i get access to the data of branches, generated by lookup()?I have something like that:...route[LOOKUP] {...lookup("location");t_on_branch("ON_BRANCH");...}branch_route["ON_BRANCH"] {...xlog("L_INFO", "[ON_BRANCH] Current branch data: idx = $T_branch_idx, uri = $(branch(uri)[$T_branch_idx])");...}...When lookup found more than 1 contact it appending a new branches, but i could read any data only from first of them:Aug 23 16:56:03 opensips-test /usr/sbin/opensips[18629]: [ON_BRANCH] Current branch data: idx = 0, uri = sip:name@domainAug 23 16:56:03 opensips-test /usr/sbin/opensips[18629]: [ON_BRANCH] Current branch data: idx = 1, uri = Aug 23 16:56:03 opensips-test /usr/sbin/opensips[18629]: [ON_BRANCH] Current branch data: idx = 2, uri =  So, i can't access to any data of any branch except first one. Even more:I need to delete branches after they fires fr_times (local 408 is received). To do that, i trying to call remove_branch($T_branch_idx) from failure_route:...failure_route[ON_FAIL] {...if (t_check_status("408")) {...remove_branch($T_branch_idx);route(LOOKUP);}...}but after that, all branches still on their places. So, can i somehow delete these "expired" branches?version: opensips 2.1.4 (x86_64/linux)___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] B2BUA parameter parsing

2016-08-24 Thread Bogdan-Andrei Iancu


Please see my previous reply:
http://lists.opensips.org/pipermail/users/2016-August/035349.html

Regards

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

On 24.08.2016 00:50, Adrian Fretwell wrote:


Can anyone help?  Setting up a call from the middle with B2BUA I pass 
RURI as a parameter via MI interface.  RURI has some header values:


param1 = sip:al...@abc.net?header1=qaz&header2=wsx

param2 = sip:b...@abc.net?header1=qaz&header2=wsx

Problem is B2BUA puts the whole parameter string in the From and To 
headers where really only the parameter string up to the ? is required 
and valid for the From and To headers.


Will I need to patch the source code in b2b_entities to solve this?  
I'm guessing it is when the t_client structure gets populated, can 
someone put me on the right track please?


Kind regards,

Adrian Fretwell


___
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] B2BUA RURI with headers

2016-08-24 Thread Bogdan-Andrei Iancu


Hi Adrian,

Do you have a pcap with the SIP traffic ? also the opensips log (with 
the parsing error) will help.


Regards,

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

On 21.08.2016 11:05, Adrian Fretwell wrote:


Hello,

I have put together a very simple scenario that bridges two clients, 
it is called from the MI (datagram) interface.  I want the two SIP 
messages that go out to the clients to contain some header values, so 
I specify these in the two parameters sent in the MI call.  Please 
note, I am using the bash shell, /dev/udp... does not actually exist:


/bin/echo -e 
":b2b_trigger_scenario:\nahf1\nsip:al...@abc.net?header1=qaz&header2=wsx\n...@abc.net?header1=qaz&header2=wsx" 
> /dev/udp/192.168.126.72/9061


This works but the problem I have is that the B2BUA includes the 
header part of the RURI in both the To and From headers.  When the UAC 
responds with a 200 OK, B2BUA sees the extra information in the To and 
From headers and throws a "unable to parse", "bad header" error.


Is there any way to stop B2BUA from including the RURI header 
information in the To and From headers?  Can headers be specified 
separately in the  xml tag?


Kind regards,

Adrian Fretwell


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


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

Re: [OpenSIPS-Users] OPENSIPS_CP DIALPLAN

Re: [OpenSIPS-Users] OPENSIPS_CP DIALPLAN

Re: [OpenSIPS-Users] OPENSIPS_CP DIALPLAN

Re: [OpenSIPS-Users] OPENSIPS_CP DIALPLAN

Re: [OpenSIPS-Users] OPENSIPS_CP DIALPLAN

Re: [OpenSIPS-Users] OPENSIPS_CP DIALPLAN

Re: [OpenSIPS-Users] OPENSIPS_CP DIALPLAN

[OpenSIPS-Users] Too many warnings in opensips log

Re: [OpenSIPS-Users] OPENSIPS_CP DIALPLAN

Re: [OpenSIPS-Users] dispatcher module call limit

Re: [OpenSIPS-Users] dispatcher module call limit

Re: [OpenSIPS-Users] dispatcher module call limit

Re: [OpenSIPS-Users] OPENSIPS_CP DIALPLAN

Re: [OpenSIPS-Users] accessing to branch data

Re: [OpenSIPS-Users] B2BUA parameter parsing

Re: [OpenSIPS-Users] B2BUA RURI with headers

16 matches

Site Navigation

Mail list logo

Footer information