Search results for query: *

Wie gesagt, es gibt einen Header. Es ist nicht nötig, zusätzlichen (add/append) Header hinzuzufügen. As mentioned… there is already a header available from IPO. No need to add another contact header (add/append).

It's not a problem to have ports 60000-60100 even if the provider uses 50000-59999.

Then the registration has to be disabled. And probably some tweaks in sip domain and it should work. Inbound OPTIONS arrive so I guess the firewall is not too bad configured. Or the IPO is connected to a cpe device directly.

Do you need to register? You send register messages but they are not answered. Instead you receive OPTIONS messages where the IPO sometimes answers with OK and sometimes with 503. I guess registration is not needed. Check your config to match the carriers need

Again… they use that wide RTP range. What you can configure is the range that IPO uses. Their information is just for you to ensure that you have your firewall towards the needed provider ports open.

What is not working? I’m on mobile so not really able to read the trace.

It shouldn’t be a problem if it is an Avaya provided server. I guess R620 has been sold with IPO 11.0 and I don’t remember that upgrading from 11.0 to 11.1 and 11.1 to 12.0 has any restrictions on server hardware. So generally it should be supported even if the R620 might be EoS by Dell.

You can do a fresh installation. Load the image to a USB drive and boot from it and let the installation run. Afterwards it’s a factory default installation.

That's not correct! An 9600 phone (9620/30/40/50) will load 96xxupgrade.txt first and then 46xxsettings.txt. An 96x1 phone (9608/11/21/41) will load 96x1Hupgrade.txt first and then 46xxsettings.txt. The upgrade files have this line, that tells the phone to load the settings file: GET...

What @Alfalis tells you is that this piece of the sigma script set the user part of the contact header to the CompanyFlex Username. Regardless what is received by IPO. As the header is already there it makes no sense to add or append anythin.

@Madil You only define what port range you use in your IPO. The provider tells you what port he wants you to send your RTP packages to. It can be that they use such a big port range. But you don't have to know it really (except if you wnat to nail it down in the firewall).

Hard to say from here... It depend on where the call comes in, mybe the URI matching, destination. This has to match with the failover flow. It can also be that the routing profile doesn't match. Do you see incidents?

I have no system available to test. But I never changed RTP range to such a wide range. Be aware that you need two ports for each parallel call. I guess not that you want to handle 30000 calls at once.

But IP Office usually sends a contract header. So no need to append one.

What exactly is needed in the contact header?

Check the mailbox folders. It contains a text file with some information. Maybe this helps you. I have no to check it myself currently.

First of all it all depends on what solution you want to install. If it is a server edition solution it only supports fallback VMPro on primary and secondary server. If a SCN of IP 500 control units only you can distribute multiple VMPro servers. Two servers can be built to have redundancy. It...

LG: 4 Incoming Number 80055512xx Destination 12#

Additionally... The SIP messages you posted is normal. Each registration is answered with 401 in the first step and the endpoint has to register again with a message containing the given "WWW-Authentication" together with password.

I found out that the links within the signature don't work