bintec elmeg bietet unterschiedliche Router mit vielen Funktionen (inklusive der zunehmend wichtigen IPv6 und DSLite Konnektivität) zu einem guten Preis an. Mit diesen Routern ist es zum Beispiel möglich, eine VPN Infrastruktur aufzubauen, wenn ein zentraler Standort mit verschiedenen Filialen verbunden werden soll.
Als Zentralrouter bietet bintec elmeg die Router der RXL Serie an. Für die Filialen wäre die günstigste Variante ein RS123 Router, der eine Verbindung über Ethernet oder den integrierten SFP Port herstellen kann. Soll der Router an einem DSL Anschluss betrieben werden, sind die Router der RS353 Reihe oder die be.IP Plus mit ihrer eingebauten Telefonanlage die bessere Option. Darin sind zwei ISDN-Schnittstellen und vier analoge Ports verbaut, an denen analoge Telefone oder Faxgeräte angeschlossen werden können. Dadurch kann auf die Anschaffung eines zusätzlichen ATAs verzichtet werden.
bintec elmeg offers several routers that offer a good feature set (including the more and more important IPv6 and DSLite) for a good price. Those routers can be used for example to build a VPN infrastructure, if you have to connect a central site with several branch offices.
For the central site bintec elmeg offers RXL series routers. For the branch offices the cheapest option is a RS123 router that can connect through ethernet connection or by using the inbuilt SFP port. If there is a DSL line in place, the better option is RS353 or be.IP Plus with it‘s inbuilt PBX. It comes with four analogue interfaces to connect analogue phones or fax devices. No need to buy an extra ATA.
Update: Ich habe den Hinweis entfernt, dass die Regionaleinstellungen auf “de_DE.UTF-8”, da ich die Information bekommen habe, dass die Host ID beim Booten des Servers generiert wird. Daher ist es wahrscheinlich nicht die beste Idee, andere Regionaleinstellungen als “en_US.UTF-8” zu verwenden.
Update 2: Ich habe den Link zum offiziellen Dokument ergänzt, das Avaya veröffentlicht hat.
Wie in dem Verlinkten Beitrag beschrieben, sind wir auf ein Problem gestoßen, dass der WebLM nach dem Upgrade von einer frühren Version auf 11.0 nicht mehr funtkioniert hat. Zwar startet er wie erwartet, scheint aber nicht mehr in der Lage zu sein, aus der MAC-Adresse die Host ID zu generieren.
Das fürht zu der Situation, dass die Seite “Properties” exact nichts anzeigt:
Update: I removed the hint that the locale can be changed back to “de_DE.UTF-8” because I got the information that the host ID is generated during boot of the server. So it is probably not the best idea to use a locale different to “en_US.UTF-8”.
Update 2: I added the link to the official solution document provided by Avaya.
As described in the linked article we came over an issue that after upgrading IP Office Server Edition from earlier releases to 11.0 the WebLM stops doing it’s job. It starts well but is not able anymore to pull the MAC address and to generate the host ID.
This leads into the situation that the WebLM properties page shows exactly nothing:
After about six month of absence from Avaya I recently started to do some support again. My first job was to update a solution of two IP Office IP500 chassis together with two application servers to release 11.0 and the SBC used to connect mobile workers and a new SIP trunk to the latest 7.2 version.
From IP Office Server Edition I heard about issues with the WebLM delivered in release 11 not showing the server properties page. Without the WebLM’s Host-ID it is not possible to generate valid licenses and so IP Office itself will not work. Continue reading →
I found out that the real issue was that the provided data from IP Office came as UTF8 but PowerShell tries to treat that as local format. We can tell PowerShell to treat the data as UTF8 while reading. Continue reading →
With the end of the year 2017 the self signed certificates of many IP Office PBXs expired. Compare my last post from July 2017. Hopefully you were able to renew the certificates of all your systems in the meantime.
If not you will get a warning if you try to login the next time.
You will get this warning, if you connect to an IP Office that uses an expired certificate.
In this case it is now the time to react. To get access to the IP Office security settings you have to adjust the IP Office Manager preferences. You have to allow secure access without any certificate checks:
This images shows how to disable certificate checks in IP Office Manager preferences
Now you are able to login into security settings and to issue a new certificate.
Recently after upgrading IP Office to release 10.1 we got calls from different customers who told us that they have about two seconds of silence at the beginning of a call. After researching with one of our customers we figured out that only 9608G phones are affected while other models (9611G, 9641GS) has no problems. In our tests showed that only outbound calls are affected and only calls with direct media (no VCM calls and no RTP relay calls) are affected.
The phone were running different firmware versions and we did an upgrade to 6.6401 as it is the latest firmware that ships with IP Office 10.1. But that didn’t help. Due to the fact that 9611 phones that run the same firmware have no issues we thought of a bad series of hardware. Continue reading →
This is an update to my previous post describing the steps to create backups ESTOS applications. The older post handled backing up the earlier release 3.5 of MetaDirectory.
In the meantime MetaDirectory 4.0 has been released and with the new release ESTOS changed the installation path and the name of the service so that the current backup script will not work anymore.
So it’s time for a small update.
In order to not adjust the script every time I want to deploy it again on another server, I want a script that works for the older and the actual version. So I have to check and adjust the values for service name and paths used within the script. Continue reading →
IP Office is very strong in building a network of multiple systems that feels like a single PBX for the end user. Users can call each other between sites as if they are local. You can build hunt groups with members from different sites and users can have remote users on their phone’s buttons and many more. Technically you just have to build a SCN (Small Community Network) connection between the systems and you are done. The systems exchange all relevant data of the remote systems (like users, hunt groups) and know the best way to reach a remote user.
Most times each site has it’s own PSTN connection but internal calls are handled through the SCN connection. But what happens if the connection between sites is lost? That can happen easily if the VPN fails.
Even if it is not officially documented, Avaya built in a fallback mechanism that can help you to manage such situations. There you can define what should be dialed by IPO over PSTN to reach a user if the SCN trunk is down. Continue reading →