Montreux: Display which line is being called

Bietschhorn · Jul 9, 2015

Montreux: Display which line is being called

Initial situation

We have an Internet Box. There are two Montreux telephones directly connected to it via WLAN, i.e. without a base station
We have two different telephone numbers (landline with 2 numbers and 2 lines)
The answering machines are separated per number. Incoming calls ring on the respective Montreux (not on both)

problem

The call lists are not separated by number, i.e. incoming, outgoing and missed calls from both numbers are always displayed on both Montreux devices

Ask

How can we display the call lists separated by number on the respective Montreux telephones, i.e. assigned to the numbers?

Greetings Jürg

FlySmurf · Jul 10, 2015

Hi

I think this will be fixed with the next IB release

Greek

jicubef · Jul 15, 2015

This promise has existed for several months…

In the meantime you can use the Rousseau devices. The identification function on Multiline works.

But Rousseau also has his problems. The call lists (no answer, etc. are poor and full of fantasy; nobody is perfect…)

AAnonymous1 · Jul 16, 2015

And we will keep the promise. We are currently working on a new firmware for the Internet box and also on a corresponding update for the Montreux. At the end of Q3 I hope we will have finished this.

Bietschhorn · Jul 17, 2015

@Anonymous: If that’s the case, then I can live with it. Even if the “error” is rather illogical and the functionality has not been fully thought through.

Bietschhorn · Jul 17, 2015

@jicubef: Thanks for the tip - but it can’t be the solution that I have to get new devices. So we’ll be surprised to see whether the remedy/solution will come in Q3 (see answer below).

CyberEarth · Jul 22, 2015

@Anonymous: Then I hope that the Locarno will also be taken into account.

I still don’t understand how you can “forget” something like that. With ISDN it was also possible.

Or maybe someone wrote the firmware who no longer knows Fixnet?

AAnonymous1 · Jul 22, 2015

It is planned to also adapt the Locarno firmware. Then the second generation Locarno, which can be updated, will receive the update promptly.

And briefly about your question about “forgotten”.

We try to consistently adhere to standards. Multiline and associated functions are not yet standardized for the IP world. There are some solutions per manufacturer, but they are not compatible. This makes life more difficult and ultimately leads to a poor user experience. We have now found a solution and are pushing forward its standardization.

Another reason was that we wanted to provide basic functions first and then see what was really needed. That’s why we also provide additional functions for the Internet box and our telephones. Of course, hardware limitations must also be taken into account. We don’t want to build software where 99% of users use 10% of the features and 1% of users use the remaining 90%. This doesn’t necessarily make software more stable and makes further development pointlessly more difficult.

And as it is in other areas too. E.g. with cars or cell phones, the experiences with one generation of hardware will be incorporated into the development of the next generation. I hope you never make a mistake twice.

CyberEarth · Jul 22, 2015

@Anonymous

GuidoT wrote:

It is planned to also adapt the Locarno firmware. Then the second generation Locarno, which can be updated, will receive the update promptly.

Aha. Thanks for the reply.

I always have to smile a little when the following post comes to mind:

---———————————

Swisscom Community - HD-Phone Locarno – Page 2 - Swisscom Community - on June 19, 2014 9:40 p.m. - GuidoT

Yes, no FW update can be done on the Locarno. It’s not necessary because the device is so sophisticated that everything works very well.

---———————————

AAnonymous1 · Jul 22, 2015

That’s true and I’ll stick with it. For 99% of customers there is no need for this function. And the first generation Locarnos work the way we wanted. We never promised an update for the devices. But things evolve. And if you can do something that makes sense, then we will do it. 🙂

CyberEarth · Jul 22, 2015

So I see it differently.

If the date is displayed instead of the time in the call list, this is a bug and should not happen (as long as it has been seriously tested).

This bug could only be solved with the new devices thanks to a FW update…

Sorry, but there are things that shouldn’t be delivered like this…

Okay, now it’s over.

I’m looking forward to the new FW and otherwise I’m happy with everything:smileyhappy:

AAnonymous1 · Jul 22, 2015

I agree with you that something like that shouldn’t be the case. Of course we test seriously, but we are all human and mistakes happen. I’m glad you’re otherwise satisfied. We will continue to develop everything over the next few months/years. Let yourself be surprised.

And feel free to express your wishes here in the forum. I always look at everything.

jicubef · Jul 22, 2015

@Anonymous wrote:

And as it is in other areas too. E.g. with cars or cell phones, the experiences with one generation of hardware will be incorporated into the development of the next generation. I hope you never make a mistake twice.

Comparison with cell phones: unfortunately OK…

But comparison with cars???: I would never consciously get into a car that was launched onto the market with the quality criteria of cell phones…How many acceptable number of deaths would there be between releases????

AAnonymous1 · Jul 22, 2015

It’s all about the hardware. And cars are even more vulnerable than, for example, routers or telephones. There are so many recalls for a reason.

hed · Jul 22, 2015

Consumers want newer features more and more quickly and at ever lower prices. Of course, no one wants to bear the consequences (decreasing reliability/quality, relocation of development to low-wage countries).