search

nwaycn / fusionpbx

Automatically exported from code.google.com/p/fusionpbx
0 stars 0 forks source link

Creating inbound route fails to add 2 necessary actions in multi-tenant setup #537

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?

In a multi-tenant setup for 2nd and further tenants: 
1. Create new sip-gateway 
2. Create new extension 
3. Create new destination
4. Create new dialplan to connect to extension

What is the expected output? What do you see instead?
Dialplan detail seems to mis two crucial actions: 
action set domain=tenantdomain.ext 40
action set domain_name=tenantdomain.ext 50

What version of the product are you using? On what operating system?
dev 5103 ubuntu 12.04LTS

Please provide any additional information below.
found why I could not receive inbound calls with help of aecardeg in #fusionpbx 
IRC channel

Original issue reported on code.google.com by jean-p...@ottonet.nl on 19 Jan 2014 at 6:02

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
As I had various other problems (504 gateway timeouts) with this setup I chose 
to fire up a new VPS and do a reinstall, this time with PostgresQL instead of 
SQLite.

In this setup some screens look a bit different -- Dial plan now shows a 
Conditions and Actions screen where the correct domain and domain_name are set. 

Attached screenshots from dev 5103 with sqlite and dev 5127 with postgresql..

Original comment by jean-p...@ottonet.nl on 24 Jan 2014 at 8:27

Attachments:

GoogleCodeExporter commented 9 years ago 
This was intentional please upgrade and make sure you define your DID/DDI 
numbers in dialplan -> destinations. And run some tests. The domain name are 
determined automatically by looking up the Dialplan Destinations and setting 
the domain name and domain uuid according to which tenat the number was 
assigned.

Mark

Original comment by markjcrane@gmail.com on 4 Feb 2014 at 11:31

GoogleCodeExporter commented 9 years ago 
This is definitely not broken. It's simply a matter of making sure the lua 
scripts are up to date, run advanced -> upgrade schema, and make sure to define 
your DID/DDI numbers in dialplan destinations.

Original comment by markjcrane@gmail.com on 30 Apr 2014 at 8:11