Mistake during Outbound Routes creation

Status
Not open for further replies.

vkrt11

New Member
Apr 13, 2017
15
0
1
63
FusionPBX 4.2.2
Switch 1.6.16 (64bit)
I have prescribed Gateways - everything normally.
I prescribe Outbound Routes standard parameters which work at earlier installed systems. Also I receive a mistake:
Fatal error: Uncaught ArgumentCountError: Too few arguments to function dialplan_detail_add(), 7 passed in /usr/local/www/fusionpbx/app/dialplan_outbound/dialplan_outbound_add.php on line 385 and exactly 9 expected in /usr/local/www/fusionpbx/resources/switch.php:643 Stack trace: #0 /usr/local/www/fusionpbx/app/dialplan_outbound/dialplan_outbound_add.php(385): dialplan_detail_add('9f727bd8-9e0b-4...', '045e1944-3682-4...', 'condition', '005', '0', 'destination_num...', '1') #1 {main} thrown in /usr/local/www/fusionpbx/resources/switch.php on line 643

I put strictly to the description on the website.
The installed system on Debian in a similar situation leads to the same mistake.
The previous time put system on Debian and no problems in the course of control have arisen - everything normally works.
What can be made in this sistuation?
 

vkrt11

New Member
Apr 13, 2017
15
0
1
63
Good afternoon. For clarity, I took screenshots of each action. 1. Installed a clean system on FreeBSD 11.0 2. Login under ADMIN. 3. Create Gateways. 4. Create Outbound Routes.
 

Attachments

  • 001.jpg
    001.jpg
    89.8 KB · Views: 11
  • 002.jpg
    002.jpg
    60.5 KB · Views: 11
  • 003.jpg
    003.jpg
    95.6 KB · Views: 9
  • 004.jpg
    004.jpg
    58.6 KB · Views: 9
  • 005.jpg
    005.jpg
    84.9 KB · Views: 8
  • 006.jpg
    006.jpg
    115.7 KB · Views: 9

vkrt11

New Member
Apr 13, 2017
15
0
1
63
Between the cases I found another glitch. Create Extensions 6280. We assign it to Destinations inbound - Ok. Delete in the Destinations Extension 6280. On the screen we get the inscription: delete from v_destinations where destination_uuid = '3195b3f9-4c1a-447b-929f-41fac077bad5'

Strange is all. On a system installed a couple of months ago, there are no such glitches. I checked the situation on Vmware Debian 8 and FreeBSD 11 systems. Situations are similar.
 

vkrt11

New Member
Apr 13, 2017
15
0
1
63
Comparison of initial catalogs / www/fusionpbx after installation, on earlier installed system and new, has shown their full identity.
There is a feeling that a problem in structure of postresql base of the system created in the course of installation.
 

EasyBB

Active Member
Oct 23, 2016
240
33
28
Australia
Good afternoon. For clarity, I took screenshots of each action. 1. Installed a clean system on FreeBSD 11.0 2. Login under ADMIN. 3. Create Gateways. 4. Create Outbound Routes.

That dialplan expression in 003.jpg looks a bit strange.
 

vkrt11

New Member
Apr 13, 2017
15
0
1
63
It is taken for the purposes to show a system glitch. Believe registering in Dialplan Expression
the below-specified realistic number plan, mistake precisely same.
^([234].....|1(.*)|6[013456789]..|62[012345679].|7(.*)|8(.*)|9(.*))$
 

Attachments

  • 100.jpg
    100.jpg
    96.5 KB · Views: 7
  • 101.jpg
    101.jpg
    59.3 KB · Views: 7

EasyBB

Active Member
Oct 23, 2016
240
33
28
Australia
Could you show us the actual outbound dialplan block after it is saved?

Also please post the whole regex string that you use along with some test numbers that you normally dial.
 

vkrt11

New Member
Apr 13, 2017
15
0
1
63
Here result of one and same action by two cars, one is installed and the second works few months the other day.
Two screenshots result of creation of one and same number plan on these systems.
The number plan completely correct also works for two fusionpbx and two freebsd+freeswitch systems
 

Attachments

  • 102.jpg
    102.jpg
    199.8 KB · Views: 9
  • 103.jpg
    103.jpg
    75.2 KB · Views: 9

EasyBB

Active Member
Oct 23, 2016
240
33
28
Australia
Your regex has many mistakes in it. I would fix it first before looking elsewhere.....

Here is my way of writing your current regex:
Code:
^([2-4]\d{5}|[17-9](\d+)|6[^\D2]\d{2}|62[^\D8]\d)$

As I said, this may not be doing what you want it to do.
 
Last edited:

vkrt11

New Member
Apr 13, 2017
15
0
1
63
It seems to me that we misunderstand each other.
I try to inform of the fact that a problem not that we place in Dialplan Expression, and that the error arises in case of ANY entered parameters in this point.
To the line offered by you there is precisely the same error.
At what level a problem I пытась to understand now.
I see that from the moment of the previous installation changes are made to scripts of installation, in particular the separate PHP file of installation of the database appeared.
Now by the test machine Debian on which I will try to carry out installation of system by an old script of installation is put.
If it removes a problem, then a glitch in new scripts if isn't present then in the external installed programs.
If you have an opportunity and desire, then make test installation the last script and check at yourself.
 

EasyBB

Active Member
Oct 23, 2016
240
33
28
Australia
It seems to me that we misunderstand each other.
I understand your issue is not the dialplan regex. But it has mistakes so you need to fix them to avoid getting unpredictable results.
To the line offered by you there is precisely the same error.
That is because I haven't fixed your mistakes; my regex is exactly yours but written differently. I can't fix it without knowing what your expected outputs are.

Your issue is that a php function expects 9 input parameters and it is getting only 7. I don't know why and I haven't checked. Let me see if I have a 4.2.2 installation to test.
 

EasyBB

Active Member
Oct 23, 2016
240
33
28
Australia
My install is 4.3.0

What I am going to suggest is only as a test:

In the dial plan block on the first line (condition) please select Break -> Never and Inline -> false
 

vkrt11

New Member
Apr 13, 2017
15
0
1
63
I don't know why there is this glitch. My knowledge aren't so deep to investigate interaction of scripts of PHP with SQL base.
My idea was to transfer work of fusionpbx to FreeBSD as system more familiar to me.
All previous systems, except the last work at this system.
At that time the script even BSD adapted by me under the last changes of packages didn't want to put working system. It was necessary to put on Debian.
I will wait for the end of installation and result.
 

vkrt11

New Member
Apr 13, 2017
15
0
1
63
Unfortunately I haven't understood your question. Google Translator distorts sense a little.
 

EasyBB

Active Member
Oct 23, 2016
240
33
28
Australia
After installation, you need to run Advanced -> Upgrade. Select one step (tick one checkbox) at a time and execute.

Where are you from? if you don't mind me asking.
 

vkrt11

New Member
Apr 13, 2017
15
0
1
63
After installation I didn't update system. All actions are described in the 3rd post.
 
Status
Not open for further replies.