6 posts / 0 new
Last post
eherr
eherr's picture
Joined: 2011/11/11
Points: 0

I know going into the mysql DB is frowned upon.

However, what breaks if I were to make the tenant with capital letters to help ease a migration?

I thought I read somewhere that connect breaks but none of my end users know about connect and will not being using it in the near future.

I would like to migrate all users to the box with the normal naming convention and then hit each tenant/customer and migrate their config files to lower case and then put the mysql DB tenant back to lowercase.

Thoughts?

mcampbell@1poin...
mcampbell@1pointcom.com's picture
Joined: 2015/05/20
Points: 10

From the Thirdlane Docs accessible at https:// www dot thirdlane dot com /docs/platform/tenants:
"Tenant name. Unique lowercase alphanumeric name for the Tenant (no spaces or dashes are allowed)."

Uppercase will not work - we migrated from v7 to v9 and had to do it manually. If anyone knows a better way please chime in.

eherr
eherr's picture
Joined: 2011/11/11
Points: 0

I know the docs say uppers are not allowed but I am more questioning what breaks and if we are not using it, can I survive a cutover and then move each tenant back down to lower; not keep it there as an upper tenant. I can easily test it out face value but you never know those hidden configs that creep up whenever you try to execute.

mcampbell@1poin...
mcampbell@1pointcom.com's picture
Joined: 2015/05/20
Points: 10

Go for it.

biznet
biznet's picture
Joined: 2016/01/19
Points: 40

When they outlawed new tenants with Caps all of mine were caps. Thirdlane promised they would be backwards compatible. Sure seems like something could be added in the backend to change caps (especially on registrations) Matt, are you saying that "connect" may be broken in newer versions (10??). we have not upgraded because of issues folks are seeing, you for one. Is this yet another reason not to Upgrade? No mention of fixing upgrade issues in 10.1.2.

Did you finally get 10.1 working in production?

Connect is such a good idea, which works poorly in the phone versions, and backward compatibility is non existent. I wish this could be fixed. Basing a business on something where you need to chase around upgrade changes system wide... no fun.

We've gone to helping our customers with Mizu Droid and other simple SIP clients instead of Connect Mobile, which work great and is really mostly all folks want; Mobile SIP extensions. Yes you have to create them a dedicated extension, extension licensing is cheap and they won't be using both simultaneously, so resource usage is small. A pain but it works a lot better for remote workers than Connect. I Hope they fix it, but I can see where the difficulty lies when you are trying to make an app that does so much.

netriplex
netriplex's picture
Joined: 2012/01/24
Points: 140

biznet,

As an fyi, you can get around the need to license extensions for these extra sip connections, by using a special line configuration and changing the users main extension to be a multi-device extension. This allows a user to register a separate SIP device and have both ring at the same time and only need 1 extension number and 1 voicemail box.