Mobile twinning not working for any user created after user 275.

[NLPeterK]

Hi guys,

I think I found a bug in 8.1. We're running 8.1(69) but I've also managed to reproduce this on 67 en 63.

We're running a system with 338 users (and probably expanding to some more) and 218 physical extensions.

Users were imported from CSV, so imported in exact the order they were listed in this CSV. When creating a user I assume it gets assigned some kind of unique ID in the IPO (which we can't see).

I found out that for some users mobile twinning woulnd't work. I won't activate from a phone and when enabled through Manager (phone status changes) the actual twinning will not happen. Monitor would say "Mobile twinning ignored (no licence)" (note the spelling error ). Mind you: mobile twinning is unlicensed since 8.1.

I started testing (and sweating because I already had nightmares about having to rebuild this whole config) and I think I figured it out:

Any user created after user 275 is not allowed to twin. So the first 275 users can use mobile twinning, any user after that cannot.

Funny thing: when I delete ALL users and create one single user, this user can also not use twinning. Apparently although deleting all users, the order of unique user IDs is somehow retained.

This kinda feels like the 256-ip-phones we had in 8.0.

Thoughts?

 

[amriddle01]

No spelling mistake, it was a British/English system originally ....and we invented the language after all.

Do not confuse licence with license. Licence is a noun which means 'a permit to do something' (a driving licence), whereas license is a verb meaning 'give a permit to someone; allow something' (the loggers are licensed to cut mahogany trees). In American English, both the noun and the verb are spelled license

"No problem monkey socks

 

[NLPeterK]

Ah, I grew up with American English. I blame tv!

 

[intrigrant]

If you export the whole config (csv) then it will show the record IDs for all users used internally.
So you can check your theory with that.

 

[NLPeterK]

Theory has already proven false but may have figured it out

After posting the original message I realized that not all users had Mobility enabled so my theory regarding 'user 275' must somehow be false or at least the number was incorrect.

Then I started disabling Mobility for users and found out that the number actually shifted upwards!

My new working theory is that there's a maximum amount of users that can actually have Mobility (mind you, not Twinning actually active, just the 'Mobility Features' checkbox) enabled. Could there be a correlation between the amount of trunk channels and the max amount of Mobility Features users? We have a 60 channel SIP trunk, but also a 60 channels PRI on board (which is unused).

I have been unable to find an official statement whether this is true or not.

 

[tlpeter]

Peter, the amount of trunks should not matter at all.
Is it an issue you see in monitor or in the config itself?
It could an error in manager itself.
Can you try with a 9.0 manager and see if it still happens. ( i know that your company is in the trials too)
Perhaps if this also happens on 9.0 then please log this issue!

BAZINGA!

I'm not insane, my mother had me tested!

 

[NLPeterK]

tlpeter,

it's an issue we see in the monitor. There are no errors in Manager. I specifically programmed this system with a R8.1 manager to avoid potential shit like this but also with R9 just to see what would happen. No difference.

We stil have to try this on R9 but we ourselves don't have enough users

 

[tlpeter]

We don't either


BAZINGA!

I'm not insane, my mother had me tested!

 

[DutchRonald]

Hi Peter,

Can't you import the 275+ users in our own IPO just to see if you still can't enable the Mobility for those users? You can set the No Directory checkbox from the CSV file.

Hope this helps!

Grtz,
Ronald (from vacation )

 

[NLPeterK]

As mentioned, enabling the checkbox Mobility Features is not the issue. It enables just fine. It's just that after a certain (unknown) amount of users have been enabled for Mobility, it doesn't seem to work anymore.

It's not random, the problem shifts to users with a higher extension number (ie imported/created last).