Request Method: GET
Request URL: http://127.0.0.1:8092/
Django Version: 1.2.3
Exception Type: DatabaseError
Exception Value:
relation "auth_user" does not exist
LINE 1: …ser"."last_login", "auth_user"."date_joined" FROM "auth_user…
^
Exception Location: /usr/lib/pymodules/python2.6/django/db/backends/postgresql_psycopg2/base.py in execute, line 44
Python Executable: /usr/bin/python

Thanks

Anyway, you can probably just add /usr/src/wikipbx/wikipbx to WSGIPythonPath setting in your apache config to get it to work.

Thanks
Aza

  Alias /soundclips /usr/src/wikipbx/soundclips Alias /site_media /usr/src/wikipbx/wikipbx/wikipbxweb/static 

Looks like it was missing in the docs, I've updated them.

Thanks
Aza

It should work on all django DB backends, as we don't use any hand-written SQL code. We haven't tested 0.8 on anything but postgres, so there's some possibility of getting issues with django ORM, but it's not very likely. I'm running trunk version on sqlite without any problems, but you should be awart that its write performance is not stellar, it's not something you'd want to run in production under heavy load.

i see that wikipbx depends on log4py and python-xml which looks like are dead projects. They also aren't in recent debian versions anymore. Is there a plan to remove them as dependency? Also does wikipbx work on any database django works, i.e. sqlite?

What OS distro and python version are you running? Is that the default python version for your OS? Did you install binary build of mod_wsgi or compile it yourself? You may need to build mod_wsgi if you've installed binary that doesn't work for unknown reason.

Also, if you've installed mod_python along with mod_wsgi, you may have some problems with running python code under apache.

PYTHONPATH=/usr/src/wikipbx python -c "from wikipbx import settings"

Comes right back with no messages.

root@freeswitch:/etc/apache2/sites-enabled# grep WSGIPythonPath *
wikipbx:WSGIPythonPath /usr/src/wikipbx:/usr/src/django:/usr/src/freeswitch/libs/esl/python

Full log contents at http://fayettedigital.com/wlog.txt

Thanks,
Jim.

 PYTHONPATH=/usr/src/wikipbx python -c "from wikipbx import settings" 

If it doesn't give you an error, make sure that your apache config has /usr/src/wikipbx as one of the values of WSGIPythonPath directive.

Can you be more specific? I did everything in that section as described. The only questionable part is the

modify FREESWITCH_URL_PORT and change the current value to http://wikipbx.yourserver.net, where yourserver.net MUST be replaced with the domain name you are planning on using.

Section. Since I'm behind a firewall I don't have a domain defined so I've set it to http://127.0.0.1. I fail to see how that affects the failure of python to find the settings.py file.

root@freeswitch:/usr/src/wikipbx/wikipbx# ls
authutil.py init.pyc settings.py urls.py
cdrutil.py ivr settings.pyc utils.py
dialplanbuilder.py logger.py settings_template.py utils.pyc
extensionutil.py logger.pyc sofiautil.py wikipbxweb
freeswitchxml mailutil.py sofiautil.pyc xmlconfig.py
fseventlogger.py manage.py statics.py xmlutil.py
fsutil.py migrate.py ttsutil.py
init.py modelutils.py twisted

Thanks,
Jim.

You've missed this part of install guide.

Stas.

os.environ['DJANGO_SETTINGS_MODULE'] = 'wikipbx.settings'

And I see in the /etc/apache2/sites-available/wikipbx file

WSGIScriptAlias / /usr/src/wikipbx/wikipbx.wsgi

But I fail to find where apache has been told where the wikipbx.settings file is located.

Hence the following message:

[Thu Aug 05 09:22:54 2010] [error] [client 192.168.2.90] mod_wsgi (pid=31296): Exception occurred within WSGI script '/usr/src/wikipbx/wikipbx.wsgi'.
…
[Thu Aug 05 09:22:54 2010] [error] [client 192.168.2.90] raise EnvironmentError, "Could not import settings '%s' (Is it on sys.path? Does it have syntax errors?): %s" % (self.SETTINGS_MODULE, e)
[Thu Aug 05 09:22:54 2010] [error] [client 192.168.2.90] EnvironmentError: Could not import settings 'wikipbx.settings' (Is it on sys.path? Does it have syntax errors?): No module named wikipbx.settings

So where did I miss the relationship?

Thanks,
Jim.

http://wikipbx.wikidot.com/forum/t-233617/problems-getting-0-8-running-on-debian

but because I am new to all this, I get all kinds of errors maybe someone could shed some light on how to implement the solution correctly. Here is what I have done so far:

1)Downloaded Swig and unzipped into /usr/src/swig-2.0.0
2)Ran ./configure ( I am not sure what options if any I should put when running configure, I just ran without any)
3)When I try to run "make install" I get:

/usr/src/swig-2.0.0/Tools/config/install-sh: swig does not exist.
make: *** [install-main] Error 1

4)So I went to /usr/src/freeswitch/src/mod/languages/mod_python and tried to run "make reswig" here is what I got:
wikipbx:/usr/src/freeswitch/src/mod/languages/mod_python# make reswig
rm -f mod_python_wrap.* freeswitch.py
which swig 2>&1 »/dev/null && swig -python -c++ -I../../../../src/include -oh mod_python_wrap.h -o mod_python_wrap.cpp mod_python.i
make: *** [mod_python_wrap.cpp] Error 1

I'm sure I missed a step or a few steps, but any and all help is greatly appreciated.

thanks a lot

1)yes I have,

wikipbx:/etc/apache2/sites-enabled# ls -al
total 2
drwxr-xr-x 2 root root 1024 Jul 11 13:21 .
drwxr-xr-x 7 root root 1024 Jul 11 02:31 ..
lrwxrwxrwx 1 root root 36 Dec 20 2009 000-default -> /etc/apache2/sites-available/default
lrwxrwxrwx 1 root root 26 Jul 11 13:21 wikipbx -> ../sites-available/wikipbx
wikipbx:/etc/apache2/sites-enabled#
*

2)Done that and restarted and
***
3)No errors in Apache, see the tail log below

[Thu Jul 15 21:56:40 2010] [error] [client 61.178.187.181] client sent HTTP/1.1 request without hostname (see RFC2616 section 14.23): /w00tw00t.at.ISC.SANS.DFind:)
[Fri Jul 16 05:42:22 2010] [error] [client 74.63.218.250] client sent HTTP/1.1 request without hostname (see RFC2616 section 14.23): /w00tw00t.at.ISC.SANS.DFind:)
[Fri Jul 16 06:00:16 2010] [notice] caught SIGTERM, shutting down
[Fri Jul 16 06:00:17 2010] [notice] Apache/2.2.9 (Debian) mod_wsgi/3.1 Python/2.5.2 configured — resuming normal operations
[Fri Jul 16 06:02:01 2010] [error] [client 127.0.0.1] File does not exist: /var/www/xml_dialplan
[Fri Jul 16 06:02:01 2010] [error] [client 127.0.0.1] File does not exist: /var/www/xml_dialplan
[Fri Jul 16 06:02:01 2010] [error] [client 127.0.0.1] File does not exist: /var/www/xml_dialplan

-The last 3 lines happens when I actually load Freeswitch, not when restarting apache
-Also I actually compiled Python 2.5.5 but its shown here as 2.5.2, don't know if that makes a difference at all

2. Add these lines to the end of VirtualHost section in /etc/apache2/sites-available/wikipbx:

  <Directory /usr/src/wikipbx-0.8> Order allow,deny Allow from all </Directory> 

Restart apache.

3. Are there any errors displayed when apache is started?

Here are my configuration files, the only parts not real are "myserver" and "PASSWORD" :

/usr/local/freeswitch/conf/autoload_configs/xml_curl.conf.xml ,

/etc/apache2/sites-available/wikipbx

???????????????????????????????????????????????????????????????????????????

<configuration name="xml_curl.conf" description="cURL XML Gateway">
<bindings>
<binding name="example">
<!— The url to a gateway cgi that can generate xml similar to
what's in this file only on-the-fly (leave it commented if you dont
need it) >
<! one or more |-delim of configuration|directory|dialplan >
<param name="gateway-url" value="http://wikipbx.myserver.net/xml_dialplan" bindings="configuration,dialplan,directory"/>
<! set this to provide authentication credentials to the server >
<!<param name="gateway-credentials" value="muser:mypass"/>>
<!<param name="auth-scheme" value="basic"/>—>

<!— optional: this will enable the CA root certificate check by libcurl to
verify that the certificate was issued by a major Certificate Authority.
note: default value is disabled. only enable if you want this! >
<!<param name="enable-cacert-check" value="true"/>>
<! optional: verify that the server is actually the one listed in the cert >
<! <param name="enable-ssl-verifyhost" value="true"/> —>

<!— optional: these options can be used to specify custom SSL certificates
to use for HTTPS communications. Either use both options or neither.
Specify your public key with 'ssl-cert-path' and the private key with
'ssl-key-path'. If your private key has a password, specify it with
'ssl-key-password'. >
<! <param name="ssl-cert-path" value="$${base_dir}/conf/certs/public_key.pem"/> >
<! <param name="ssl-key-path" value="$${base_dir}/conf/certs/private_key.pem"/> >
<! <param name="ssl-key-password" value="MyPrivateKeyPassword"/> >
<! optional timeout >
<! <param name="timeout" value="10"/> —>

<!— optional: use a custom CA certificate in PEM format to verify the peer
with. This is useful if you are acting as your own certificate authority.
note: only makes sense if used in combination with "enable-cacert-check." >
<! <param name="ssl-cacert-file" value="$${base_dir}/conf/certs/cacert.pem"/> —>

<!— optional: specify the SSL version to force HTTPS to use. Valid options are
"SSLv3" and "TLSv1". Otherwise libcurl will auto-negotiate the version. >
<! <param name="ssl-version" value="TLSv1"/> —>

<!— optional: enables cookies and stores them in the specified file. >
<! <param name="cookie-file" value="/tmp/cookie-mod_xml_curl.txt"/> —>

<!— one or more of these imply you want to pick the exact variables that are transmitted >
<!<param name="enable-post-var" value="Unique-ID"/>—>
</binding>
</bindings>
</configuration>

**
WSGIPythonPath /usr/src/wikipbx-0.8:/usr/src/django:/usr/src/freeswitch/libs/esl/python

<VirtualHost *:80>
ServerAdmin ten.revresym.xbpikiw|retsambew#ten.revresym.xbpikiw|retsambew
WSGIScriptAlias / /usr/src/wikipbx-0.8/wikipbx.wsgi
ServerName wikipbx.myserver.net
ErrorLog /var/log/apache2/wikipbx.myserver.net-error.log
CustomLog /var/log/apache2/wikipbx.myserver.net.log common
</VirtualHost>
**
INSTRUCTIONS

1. 1. Change DATABASE_USER
2. 2. Change DATABASE_PASSWORD
3. 3. Customize FREESWITCH_URL_PORT

import os

1. settings.py lives in the wikipbx subdir, eg, the "source" directory
2. (/usr/src/wikipbx/wikipbx)

INSTALL_SRC = os.path.dirname(file)

1. the parent of the source directory is the installation root, eg, the
2. dir the user checked out to (eg, /usr/src/wikipbx)

INSTALL_ROOT = os.path.split(INSTALL_SRC)[0]

DEBUG = True
TEMPLATE_DEBUG = DEBUG

ADMINS = (
# ('Your Name', 'moc.niamod|liame_ruoy#moc.niamod|liame_ruoy'),
)

MANAGERS = ADMINS

DATABASE_ENGINE = 'mysql' # 'postgresql_psycopg2', 'postgresql', 'mysql', 'sqlite3' or 'ado_mssql'.
DATABASE_NAME = 'wikipbx' # Or path to database file if using sqlite3.
DATABASE_USER = 'wikipbxuser' # Not used with sqlite3.
DATABASE_PASSWORD = 'PASSWORD' # Not used with sqlite3.
DATABASE_HOST = '' # Set to empty string for localhost. Not used with sqlite3.
DATABASE_PORT = '' # Set to empty string for default. Not used with sqlite3.

1. Local time zone for this installation. Choices can be found here:
2. http://www.postgresql.org/docs/8.1/static/datetime-keywords.html#DATETIME-TIMEZONE-SET-TABLE
3. although not all variations may be possible on all operating systems.
4. If running in a Windows environment this must be set to the same as your
5. system time zone.

TIME_ZONE = 'UTC'

1. Language code for this installation. All choices can be found here:
2. http://www.w3.org/TR/REC-html40/struct/dirlang.html#langcodes
3. http://blogs.law.harvard.edu/tech/stories/storyReader$15

LANGUAGE_CODE = 'en-us'

SITE_ID = 1

1. If you set this to False, Django will make some optimizations so as not
2. to load the internationalization machinery.

USE_I18N = True

1. Absolute path to the directory that holds media.
2. Example: "/home/media/media.lawrence.com/"

1. Example: "http://media.lawrence.com"

MEDIA_URL = ''

1. URL prefix for admin media — CSS, JavaScript and images. Make sure to use a
2. trailing slash.
3. Examples: "http://foo.com/media/", "/media/".

ADMIN_MEDIA_PREFIX = '/media/'

1. Make this unique, and don't share it with anybody.

SECRET_KEY = '_#5%!uu1rgn9qu80ewht&8y96lqu2_r9s09*g(94$smx#xc*!o'

1. List of callables that know how to import templates from various sources.

TEMPLATE_LOADERS = (
'django.template.loaders.filesystem.load_template_source',
'django.template.loaders.app_directories.load_template_source',

1. 'django.template.loaders.eggs.load_template_source',

)

MIDDLEWARE_CLASSES = (
'django.middleware.common.CommonMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.middleware.doc.XViewMiddleware',
)

ROOT_URLCONF = 'wikipbx.urls'

TEMPLATE_DIRS = (
# Put strings here, like "/home/html/django_templates" or "C:/www/django/templates".
# Always use forward slashes, even on Windows.
# Don't forget to use absolute paths, not relative paths.
os.path.join(INSTALL_SRC, "/usr/src/wikipbx-0.8/wikipbx/wikipbxweb/templates"),
os.path.join(INSTALL_SRC, "/usr/src/wikipbx-0.8/wikipbx/freeswitchxml"),
)

INSTALLED_APPS = (
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.sites',
'django.contrib.admin',
'wikipbx.wikipbxweb',
)

TEMPLATE_CONTEXT_PROCESSORS = (
'django.core.context_processors.auth',
'wikipbx.wikipbxweb.context_processors.global_processor',
)

AUTH_PROFILE_MODULE = 'wikipbxweb.UserProfile'

STATIC_TTS_ENGINE = "cepstral"

1. you must manually create directories and subdirectories, eg:
2. mkdir -p /var/log/wikipbx/cdr/err
3. and set permissions according to user freeswitch process will run under

LOG_DIR_ROOT = "/var/log/wikipbx"
CDR_LOG_DIR = os.path.join(LOG_DIR_ROOT, "cdr")
CDR_ERR_LOG_DIR = os.path.join(LOG_DIR_ROOT, "cdr", "err")

1. should the entire raw cdr xml be saved in the db? (uses lots of db
2. space but useful when the extracted fields aren't enough information)

CDR_SAVE_XML = False

1. the url (including port if non-default) where freeswitch can contact
2. the wikipbx server for things like posting XML_CDR records.
3. this value completely depends on how you have your webserver
4. setup. Can be ip or hostname, depends on webserver

FREESWITCH_URL_PORT = "http://wikipbx.myserver.net"
???????????????????????????????????????????????????????????????????????????

When I type :echo $PYTHONPATH

here is what I get back
:/usr/src/wikipbx-0.8:/usr/src/freeswitch/scripts/python:/usr/local/lib/python2.5/site-packages
wikipbx:/usr/src/wikipbx-0.8/wikipbx#

I'm hoping someone might see an obvious error somewhere in the config files.

[ERR] mod_xml_curl.c:304 Received HTTP error 404 trying to fetch http://wikipbx.myserver.net/xml_dialplan data: [hostname=wikipbx.myserver.net&section=configuration&tag_name=configuration&key_name=name&key_value=post_load_switch.conf]

I don't seem to be getting any errors when loading apache. Any more pointers would be appreciated. I have scoured the net for similar issues but non seems to apply to my situation. Help por favor!

As for your questions:

1. You don't need to copy anything to /var/www dir. The "templates" directory is used by wikipbx internally, it's not meant to be displayed by the web server directly.

2. You don't need to create that file. Once you have mod_wsgi and wikipbx configured, freeswitch would be receiving necessary configs from that URL.

I noticed a folder called "templates" inside of wikipbx-0.8/wikipbx/wikipbxsweb.
1)which steps when installing wikipbx does the files inside this templates folder get copied to maybe a /var/www/ folder? Or I have to do that manually? I am finding that after I followed all the steps, when I go to my wikipbx.myserver.net, I'm still loading the default "It works".
However for just the heck of it, I copied all the files from this templates folder into a /var/www/xml_dialplan and when I go to wikipbx.myserver.net, something does come up, its just that there are errors, which leads me to believe that there is a step I am missing or I am doing wrong.

2)In this file:
/usr/local/freeswitch/conf/xml_curl.conf.xml,
I see this line:
<param name="gateway-url" value="http://wikipbx.yourserver.net/xml_dialplan/" bindings="configuration,dialplan,directory"/>
do I create this "xml_dialplan" manually or it should be created on one of the steps when setting up wikipbx?

This is probably quite easy for you guys, but I have tried different novice tricks that I know with no luck, any and all help is sincirely appreciated.

Since there are more than two people working on wikipbx codebase, I think that we should stick to a bit more disciplined approach for commits. There are various ways to organize workflows, I'm thinking about something inbetween "Decentralized with shared mainline" and "Decentralized with human gatekeeper". Unless it's a trivial change that can be committed directly to trunk by anyone, it should go through the following stages:

1. Create or select existing bug or blueprint. If it's been created, wait for some feedback.
2. Make a branch for this task. Link the related bug/blueprint to it in LP interface.
3. Hack, hack, hack.
4. When it's ready, it should be reviewed by someone (not the person who wrote the code). If there's something to be improved, go to #3.
5. Merge with trunk and/or stable branch.

Things to look for during code review:

1. Python coding style violations.
2. Things that can be improved.
3. Errors, typos.
4. Possible unexpected effects from the new code.

 Each sip profile is its own ip/port bindings, so yes, you must use different ip or port for each profile. 

Looks like it's sufficient for each profile to listen on its own socket. It's rather uncommon to have such configuration as most people just use different port numbers for different profiles, but it's not hard to implement.

But we can get another issue here. After adding multi-tenancy to wikipbx Traun noticed that that one of the gateways was using his server's IP instead of domain name for making incoming calls. We've got a workaround for authenticating such calls - domain name is specified in SIP request parameters that are received in SIP invite later. However, we won't be able to use that parameters for filtering channels as they aren't available in freeswitch command's response. In this case, it's still better to be too restrictive than too permissive, but I'd prefer to have something that always works correctly. One thing I haven't thought before is replacing IP with domain in channel variable after applying domain hack - this could work in theory.

uuid,direction,created,created_epoch,name,state,cid_name,cid_num,ip_addr,dest,application,application_data,dialplan,context,read_codec,read_rate,write_codec,write_rate,secure,hostname,presence_id,presence_data

41b249f8-7a0f-11df-971d-674148912bd7,inbound,2010-06-17 15:52:58,1276779179,sofia/DCext/13.1.861.291|101#13.1.861.291|101,CS_EXECUTE,Dimaa M 1234,101,192.168.1.13,103,bridge,sofia/gateway/My_DC_gw/441,XML,enum,default,PCMU,8000,PCMU,8000_ast

41c6b1c2-7a0f-11df-971f-674148912bd7,outbound,2010-06-17 15:52:59,1276779179,sofia/DCext/441,CS_EXCHANGE_MEDIA,Dimaa M 1234,101,192.168.1.13,441,playback,local_stream://moh,XML,enum,default,PCMU,8000,PCMU,8000_ast

4c05a792-7a0f-11df-9725-674148912bd7,outbound,2010-06-17 15:53:16,1276779196,sofia/DCext/441,CS_REPORTING,Dimaa M 1234,101,192.168.1.13,441_{,XML,enum,default,PCMU,8000,PCMU,8000}ast,,

5796698e-7a0f-11df-9728-674148912bd7,inbound,2010-06-17 15:53:35,1276779215,sofia/DCext/13.1.861.291|101#13.1.861.291|101,CS_EXECUTE,Dimaa M 1234,101,192.168.1.13,106,echo_{XML,enum,default,PCMU,8000,PCMU,8000}ast,,

4 total.

It seems to me the only common part in these channels is DCext profile name. So if every tenant has its own profile, channels can be filtered by profile.

Channels 1 and 4 can be filtered by domain name, but then channels 2 and 3 wont be visible in any Account.

Probably the same approach should be applied to CDRs for the cases where right now we raise an error:
"Cannot associate this CDR with an account. Did not find either a valid account_id or domain_name channel variable"

<profile>
<name>TestProf</name>
<type>profile</type>
<data>sip:53.1.861.291|aifos_dom#53.1.861.291|aifos_dom:5080</data>
<state>RUNNING (0)</state>
</profile>

<profile>
<name>external</name>
<type>profile</type>
<data>sip:13.1.861.291|aifos_dom#13.1.861.291|aifos_dom:5080</data>
<state>RUNNING (0)</state>
</profile>

On a serious note, github is intended for hosting code rather than developing software projects, so it doesn't offer much besides a fancy UI for forking git repos. What's missing: release planning and localization. This also leads to oversimplified issue tracker that most people don't use.

As a bonus, you can host packaged software in PPA, which I'll probably do for 0.9.

I mean github has a ton of momentum, it seems like a better time investment to learn git/github.. what do you think? What are the major benefits of launchpad over github?

I've already created a branch there a few days ago, although I was going to use it only for translations initially. I'll post a message with more details in this forum when it'll be ready for development, stay tuned.

Is there any particular targets set for the new version?
What new functionality are planed for the new version?

The next version will work with a recent version of Django plus some other minor tweaks like UI improvements

How far are the project right now from the next release?

Its about 90% there

What is the best way to contribute to wikipbx project?

There's currently not really a good way .. if you have code patches send me a private message and we can discuss over email. Eventually I think DVCS might be the best approach.

How stable is the current trunk version? Can it be used in production, if not what areas are not stable yet.

Its stable, I can't think of any areas where it will blow up on you..

I'm also thinking that DVCS is much more appropriate, because that way people don't have to send in patches which puts pressure on us to review .. with DVCS people who want to submit patches can just fork it and we will pull the (good) changes.

I think it makes sense to move everything somewhere else :)

Someplace that ..

• Free for open source projects
• provides DVCS, ideally git IMO
• Nice issue tracker
• Forum / Wiki

As there are just two developers and we work on it in our free time, we don't have any deadlines except "when it's ready".

The primary goal for the next release was to get wikipbx running on modern version of django and it's been completed. However, we don't consider trunk production ready yet as it hasn't been extensively tested and there are some more features planned.

However, there must be other less obvious ways for malicious user to exploit freeswitch server as he has direct access to generated dialplan. We plan to have a WYSIWYG interface for editing dialplan extensions in the future that would let user to use only safe commands.

 sofia/gateway/<gateway_name>/<dialstring> 

Note that gateway name doesn't have to be the host name for the SIP gateway. It can be any string identifier. The host name is taken from the "realm" field that is set to gateway name by default. In your case, every user should have unique gateway name, but they can have the same realm name with different username/password.

There's some chance that freeswitch docs are incorrect and it requires a unique socket rather than port as you suggest. You could test it by removing "unique=True" from wikipbx.wikipbxweb.models.SipProfile.sip_port, creating a new database with wikipbx models and running freeswitch with multiple SIP profiles sharing the same port number but with different IPs.

I'm new to this project and would like to find more about its development.
Could developers share the current status of wikipbx development. I'm interested in the following aspects:

Is there any particular targets set for the new version?
What new functionality are planed for the new version?

How far are the project right now from the next release?

What is the best way to contribute to wikipbx project?

How stable is the current trunk version? Can it be used in production, if not what areas are not stable yet.

Thanks!

Is there any plans to adjust this?

It configures extensions with the line like this:
<action application="bridge" data="sofia/gateway/myprovider.com/$1"/>

After that it's possible to edit this line and specify another gateway (e.g. gateway of another account)

Is there any control that every account can use only his own gateways and not gateways of other accounts?

It seems to me that in multi tenant install accounts should not be able to see and control calls of other accounts.

Is it a bug or feature?

I'm looking on this system from multi-tenant point of view.
In this case one account should be able to name his gateways as he wants. And should not depend from the names that already in use by other accounts.

E.g. When some provider provides hosted PBX service it's expectable that he'll be a gateway for them too.
They'll be using the same "Gateway Name:" "providername" and different "Username:".

May be I miss something and it was done intentionally?

If tenants have their own IPs it should be possible to allow them to have own profiles and to accept connection on 5060.