[OpenSIPS-Users] Dialplan module is not connecting to Database

Richard Robson rrobson at greenlightcrm.com
Wed Mar 23 12:37:00 CET 2016


Hi Guys,

I've got this working now.

Here's a couple of things I've found.

You appear to need partitions, despite the documentation to the contrary.
The MI command dp_translate does not accept the partition:dpid as a
valid input it seems to want just the dpid
the New book has " in its examples. These don't get added to the
database entries

regards,

Richard



On 22/03/2016 16:13, Bogdan-Andrei Iancu wrote:
> Hi Richard,
>
> Have you provided the partition name while firing the MI command ?
>
> See
> http://www.opensips.org/html/docs/modules/2.1.x/dialplan.html#id294353
> (1.8.2. dp_translate)
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> http://www.opensips-solutions.com
>
> On 22.03.2016 14:28, Richard Robson wrote:
>> Hi,
>>
>> I'm trying to use the dialplan module, but every time I get a "400 Wrong
>> db connection para"
>>
>> the connection is the same for all other modules, which are working fine
>> and I can connect via opensipsCP, mysql and phpmyadmin.
>>
>> I'm using version 2.1
>>
>> Mar 22 12:22:13 gl-sip-01 opensips: ERROR:dialplan:mi_translate: Unable
>> to get connection
>> Mar 22 12:22:13 gl-sip-01 opensips: DBG:mi_datagram:mi_datagram_server:
>> command process (dp_translate)succeded
>> Mar 22 12:22:13 gl-sip-01 opensips: DBG:mi_datagram:mi_datagram_server:
>> the response: 400 Wrong db connection para#012 has been sent in 29
>> octets
>>
>> Dialplan table:
>>
>> +----+------+------+----------+------------------+-------------+-----------+----------+---------+----------+-------+
>>
>> | id | dpid | pr   | match_op | match_exp        | match_flags |
>> subst_exp | repl_exp | timerec | disabled | attrs |
>> +----+------+------+----------+------------------+-------------+-----------+----------+---------+----------+-------+
>>
>> |  1 |   10 |    1 |        1 | "^0[1-9][0-9]+$" |           0 |
>> "^0(.*)$" | "44\0"   |         |        0 |       |
>> +----+------+------+----------+------------------+-------------+-----------+----------+---------+----------+-------+
>>
>>
>>
>> #### Dialplan ####
>> loadmodule "dialplan.so"
>> modparam("dialplan", "db_url",
>>          "mysql://root:opensips@127.0.0.1:3306/opensips")
>>
>> I also tried with the same results:
>> modparam("dialplan", "partition", "   default : table_name = dialplan ;
>> db_url = mysql://root:opensips@127.0.0.1:3306/opensips")
>>
>> does anyone know why this is happening for this module only
>>
>> Regards,
>>
>


-- 
Richard Robson
Greenlight Support
01382 843843
support at greenlightcrm.com




More information about the Users mailing list