Hello all,
does anyone knows why 8242 dect terminals does not support conference, on hold call swap and many other features when registered on smart IP-DECT 8340 antennas?
http://www.memoriofone.pt/images/features.png
Thank you so much!
I really need to solve this problem
Pedro
Basic features on 8242 are disabled!! Anyone knows why?
Re: Basic features on 8242 are disabled!! Anyone knows why?
DECT terminal created as AGAP or SIP set?
Re: Basic features on 8242 are disabled!! Anyone knows why?
Hello Vad,
thank you sou much for your reply, i'm really desperate...
Could you please check the screenshots (attachments) and help me to identify the mode?
In subscriber panel it appears as 8242 DECT, but shows the info "Sip registration OK"...
Thanks in advance Vad, i really appreciate.
Pedro
thank you sou much for your reply, i'm really desperate...
Could you please check the screenshots (attachments) and help me to identify the mode?
In subscriber panel it appears as 8242 DECT, but shows the info "Sip registration OK"...
Thanks in advance Vad, i really appreciate.
Pedro
You do not have the required permissions to view the files attached to this post.
Re: Basic features on 8242 are disabled!! Anyone knows why?
The answer is simple - just read documentation:
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.
Re: Basic features on 8242 are disabled!! Anyone knows why?
Hello Alex,
not so simple thought...!!
My question is if it is possible to register 8242 DECTs terminals on 8340 IP-DECT AP's to work with GAP or AGAP protocol, similar to 4070 IBS system.
I really need the dect terminals with same services as within an ibs sytem...
Thanks in advance!!
Pedro
not so simple thought...!!
My question is if it is possible to register 8242 DECTs terminals on 8340 IP-DECT AP's to work with GAP or AGAP protocol, similar to 4070 IBS system.
I really need the dect terminals with same services as within an ibs sytem...
Thanks in advance!!
Pedro
Re: Basic features on 8242 are disabled!! Anyone knows why?
No. See what is written by ALU above.
You see - ALU even supplied the comparison table what is working and what is not. You can't get the same service level in IP-DECT as that of IBS (at least in the current SW versions).
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.
Re: Basic features on 8242 are disabled!! Anyone knows why?
Hello again Alex, you see, i'm having so many problems with IP-DECT and 8242 terminals. Likewise,
1) Sometimes the 8242 sets have an incorrect date and time information ("07-02-2036"), but 8038 deskphones have always the correct date and time data;
2) User A (8242) is in a conversation, user B (8242) calls to user A and does not get the waiting tone, which means that he thinks that user A is idle, but in fact he is in a busy state. But if user C (8038) calls user A he gets the waiting tone.
Please help!
1) Sometimes the 8242 sets have an incorrect date and time information ("07-02-2036"), but 8038 deskphones have always the correct date and time data;
2) User A (8242) is in a conversation, user B (8242) calls to user A and does not get the waiting tone, which means that he thinks that user A is idle, but in fact he is in a busy state. But if user C (8038) calls user A he gets the waiting tone.
Please help!
Re: Basic features on 8242 are disabled!! Anyone knows why?
Hi there
Just keep in mind that IP-DECT is just an external SIP-server. So it is not integrated in OXE as IBS solution.
Just keep in mind that IP-DECT is just an external SIP-server. So it is not integrated in OXE as IBS solution.
For 1st question I would check for latest SW for OXE and DAP. For 2nd just assing User A the same phone feature category as for User C.Eppetiano wrote: ↑08 Mar 2017 06:04 1) Sometimes the 8242 sets have an incorrect date and time information ("07-02-2036"), but 8038 deskphones have always the correct date and time data;
2) User A (8242) is in a conversation, user B (8242) calls to user A and does not get the waiting tone, which means that he thinks that user A is idle, but in fact he is in a busy state. But if user C (8038) calls user A he gets the waiting tone.
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.