Issues with DECT R4 on releases 11

[t3rm3y]

Im hoping Intrigrant can help
Below is a reply he gave on another thread(

https://www.tek-tips.com/viewthread.cfm?qid=1779078)

regarding pre-configuring users on Dect and how easy it is.
This is the way we usually configure DECT, but on release 11 we are getting users unsubscribed anytime a change is made (name change, or adding them to a hunt group). how can we fix this please?


intrigrant (Systems Engineer)19 Jul 17 18:31
I wonder if anyone does DECT R4 a lot.
1 No need to delete a user.
2 No need to delete a phone if it is in provision mode, just change the IPEI number and save, click on the IPEI number in the DECT R4 users web page to enable registration.
3 If in non-provision mode go in the DECT R4 web page, edit the user settings and change the IPEI number, it will automaticly unregister the old phone. Then register the phone and enter the full PARI number to be able to register.
4 In SSA you cannot enable registration or delete users if it is a DECT R4 (I did ask but still uncertain if we really talk about a DECT R4)

I do this a lot remote with the customer on the phone, to add a new DECT phone or to replace a broken one (the 3720 is really a poor designed phone).
It takes 10 minutes with the customer help to get the phone going, so what is the big problem here?

 

[intrigrant]

Just do not use the release 10 which comes with R11, use DECT R7.2.28.
We have had the same issues with DECT at R10.x and no issues with R7.z so we only use that version untill it is proven the R10 release does what it is supposed to do.
Wn did not report to Avaya because if they think it is "design intend" we get a bill for the time they spend on it while they broke it in the first place.

 

[t3rm3y]

Thanks mate, brilliant. Works well on one of the sites as only 4 basestations.
The main site we are installing on has 9 slaves and this version 7 software is limited and only shows 4 slaves.
We will have to raise it to avaya and get a fix for 10.x as any changes the customer makes seems to knock the dect phones out of subscription.

 

[intrigrant]

The max Compacts used is five within a install and the master must be a large base station.
Each site needs its own syncmaster as well (do not confuse that with a Master station, you can only have one Master and one Backup Master)

 

[tlpeter]

With release 11.0 (or from 11.0.1) there is no limit anymore for the compacts.

BAZINGA!

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

 

[t3rm3y]

Problem is that even if the avaya is version 11 you seem to need the master basestation to be on at least version 10 software for the additional slaves to appear.
We tried with the version 7 software and only 4 slaves appeared.
Even with the master on v.10 and the slaves all v.7 it still drops the subscription if you change the name, or add the user or remove from a group (after it is subscribed).
Slight work around appears to be to get provisioning to be inactive (mismatched password) so it doesn't update changes. Hopefully this will remain subscribed until a fix is released.

 

[janni78]

Which v10 DECT version are you using?

"Trying is the first step to failure..." - Homer

 

[t3rm3y]

We used 10.0.7 initially. Then downgraded to 10.0.5 but both do the same thing.
Version 7 works well bit only if fewer then 5 basestations.

 

[tlpeter]

I have done an install with 50 in IPO version 10.0 and sexy in 7.2.28
So of this doesn’t work then something have changed.

BAZINGA!

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

 

[t3rm3y]

Hi Peter. The IPO was version 10? As we have version 11.0
What version was the base stations on?
We will have to try v.10 in office but I think we had done that when first had the issues..

 

[intrigrant]

We run R11 in the office and we ru n DECT on 7.2.28, never had a issue.
Setup if with provision - pre setup phones and users.
We also have a backup master dect, tested and working.
Although we can cover all with thre base stations I have placed seven of them, two compact base stations.

the same we have done for some customers, the only complain is that the 3720/3730 handsets have poor buttons, these are quicly unreadable or broken.

 

[t3rm3y]

We do set up that way, pre configured, users created on system. Ipei added to the extensions.
Master then sees them so we click the ipei on the base and then register the phone as ipdect, park and a.c. code and they subscribe.
As said early for our smaller site on v11 IPO we used your v7.2.28 for the base stations and worked with no reported issues . But on the larger site it had more 10 slaves and we had to upgrade the basestations to minimum of v10.0.5 for all the slaves to appear. And this is where it stops working. All users configured the same as before on smaller site (your way) but as soon as you make a change to the dect user on the IPO or add the dect user to a hunt group they become unsubscribed.

 

[intrigrant]

Just a remark:
When I register a phone I only enter the ac code, the rest can be skipped.

 

[gwebster]

http://support.avaya.com/kb/ext/SOLN325486

 

[tlpeter]

So basicly, version 10.0.0x sucks.


BAZINGA!

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