VoIP - Registration failed - I am willing to pay for real help

**Hello, I was, with a Belgian number (I live in Belgium), at Sewan (France) but they, without informing me, exploded their prices (the cheapest call that used to be 2c is now €5 plus VAT), plus the cost of the number; so I ported my number to OVH (France) which turned out to be a huge mistake: on their "support" email account they do not reply, creating a "ticket" is not possible because we are relegated to the "help" pages ("running in circles"), and their "chat" (with a bot, naturally) does not work for VoIP either, because instead of being able to ask a question you first have to choose a category, where VoIP obviously does not appear. So we are invited to use their paid telephone "support" where we would then pay hundreds of euros for nothing, since it is clear that any SIP‑parameter correction requires something "in writing", not a phone call, with a call‑center where foreigners struggle to understand each other, even more when you have to spell endless strings of cryptic characters – after already having paid €50 or €100 for nothing, I would end up back at square one, and that may well be their "business model"? Apparent very attractive prices – even national calls to landlines would be included, but with a "registration fail" I am not even reachable, and after 5 hours of attempts over 2 days I am at my wit’s end… – then they charge hundreds of euros just to get the services they sold to work a little?!

I would pay you €30 (to your account, PayPal or similar) if your help allows me to communicate with my OVH SIP (I don’t know if private messages are possible here but I would gladly pay, so we should find a solution).

So:

Instead of giving me the ported number, they gave me a (also Belgian) number of their choosing for the SIP line, and the ported number is extra; I first connected the ported number ("What is a number?") with this "SIP account", but since nothing works I then removed that connection, i.e. we now only talk about my OVH SIP number (assigned by them to this account), while the ported number is currently not connected to this account and therefore cannot be the cause of the problem? (As soon as their SIP number works I will reconnect the ported number to this SIP account.)

I have scrupulously followed their instructions:

  • login/username/authorization user name: always the SIP number assigned by them;
  • password: after trying other passwords of my choice I finally re‑assigned their password to them, and I made no mistake there either; I checked again and again;
  • domain/registrar: sip‑domain.io, as per their instructions, and outbound‑proxy also according to that, per their instructions;
  • additionally, on their page it says: Infrastructure: N11 = ??? and "Date of last recording / Local port/IP/Public port/IP" – all blank, but irrelevant, except possibly the Infrastructure N11 since I have no idea what it is and I cannot enter it in my SIP phone.

My SIP phone is a Siemens/Gigaset S685 IP, and I also have a SIP account on it with several numbers (including STUN) from a foreign operator to Belgium/France, and for those foreign SIP numbers everything works (but their monthly price for keeping my Belgian number is absurd), which is why I chose Sewan and now OVH to keep the number for the city where I live…

My SIP phone has settings for each line, and for the OVH line I entered all those OVH values for the number they assigned (as I said, my ported number will be added there as soon as their number works: first we have to solve the basic problem);

It is connected via static IP: 192.168.1.2;

For the OVH line settings there is "Telephony" → "Connections" – and there the OVH connection, as explained above, and:

"Personal Provider Data" with my password, username/authentication name (everything = perfect); then:

"General Provider Data":

  • "Proxy server port": 5060 (as indicated by OVH, and that is also the standard, and the setting for my other numbers);
  • 5060 for "Registrar server port" as well;
  • "Registration refresh time": 3600 seconds (it was 1800 seconds (without working), and OVH says 3600 is required – another thread here mentioned OVH asking for 3600);
  • "Domain", "Proxy server address"/"Registrar server": all three = sip‑domain.io (OVH instructions);

Then there is "Network":

  • Stun enabled: no (with: this also does not work, but maybe I will need it later to connect my own number, i.e. the ported number?)
  • stun server: (blank), stun port: 3478, stun refresh time: 240 seconds (since blank, these two values are probably irrelevant right now?)
  • NAT refresh time: 180 seconds
  • Outbound proxy mode: Always, Outbound proxy: I copied the OVH instructions, OVH requires this, and "Outbound proxy port": 5962 (also per their instructions).

I think I have done everything correctly here, except that if one day I want/need to enable Stun (enabled: yes) the two values stun port 3478 and stun refresh time 240 seconds will become relevant, but I could not find any information about Stun on OVH…

It should also be noted that the three sip‑domain.io settings above come from OVH instructions, while the "Outbound proxy" is something‑ovh‑1.sip‑proxy.io which does not seem very consistent, but both are from OVH instructions.

Now the GENERAL (!!!) "Advanced Settings" of my SIP phone, which are common (!) for all lines/connections, including the OVH one:

  • DTMF over VoIP connections – send settings – Auto
  • Call Transfer – Use the R key to initiate call transfer with the SIP Refer method: yes
  • Transfer call by on‑hook: no
  • Derive target address: from SIP URL (no) OR from SIP contact header (yes)
  • Find target address automatically: no
  • Hold on transfer target: for attended transfer yes, for unattended transfer no
  • Hook Flash (R‑key): R‑key settings are disabled because the R key is being used for call transfer
  • = All of this should have no impact?
  • Listen ports for VoIP connections: Use random ports: no, SIP port 5060, RTP port 30000‑40000 (set according to OVH instructions, previously it was 5004‑5020)

They added additional instructions here: https://docs.ovhcloud.com/fr/guides/web-cloud/phone-and-fax/voip/troubleshoot-local-network/ :

  • Traffic to the network 91.121.128.0/23 must be allowed. (I have not set limits)
Traffic must be allowed on ports 5060 and 5962 UDP. (done)

Traffic must be allowed on ports 2424 and 2427 UDP (only for MGCP phones of LG and Thomson series). (not applicable here)

Port range 30000‑40000 UDP must be opened (RTP ports, audio range). (done)

UDP session lifetime (Time/Timeout/NAT Session) must be ≥ 180 seconds. (done)

If available, SIP ALG must be disabled. (not found)

And now nothing works for their SIP number: "Registration failed"…

Even if we can solve this basic problem, perhaps later OVH will refuse the connection with my ported number…

I can say that my opinion of OVH is not communicable; I also transferred one of my many domains to them – probably it will no longer work either.

OVH = total fail, and their "support" system is fake, because relevant information is missing and then also unavailable via Google, their bot, or their "ticket" system, since those two do not give access, their multiple‑choice menus push you out before you can ask a question.

Just the phone "support"… which will end up costing you €500 for nothing.

On the other hand, if a fellow user knows the solution to my problem, I would be happy to take advantage of OVH’s seemingly very low prices. In the end I would have two problems, because I would then need to connect the ported number, but I suppose that would be possible, or we could swap their number (which I don’t need) with my ported number? The whole point is to be reachable via a "fixed line".

I don’t know how this will turn out, but if your / your help solves the issue I will keep my word.

(It is quite curious that a business model like OVH’s, with only paid "support" (since mail, "chat" = bot, and "ticket" are all fictitious), and paid‑by‑the‑minute phone support that costs you money without delivering a result, is legal in France… )

Hello,
I am also Belgian.

I have a "connected doorbell" that is a Mobotix system which includes a SIP server and a SIP client.
I've owned it since 2014 and I had a subscription with 3StarsNet for outbound calls to mobile phones.
3StarsNet was absorbed by Sewan and I am also a victim of the new tariff plan that is blowing up the bills.

I also have discovered SIP accounts with OVH since the very beginning of OVH's SIP offering.
The connection of my Mobotix with OVH has never worked satisfactorily. I never understood why. From memory it would randomly throw 502 errors, registration errors, etc.

Here are the SIP parameters that were provided to me at the time by OVH:

From: support@ovh.com
To: xx@xx.net
Sent: Wednesday, March 20, 2013 4:41 PM
Subject: [OVH-VoIP] Votre forfait est opérationnel 023 18xxxx

OVH
2 rue Kellermann
BP 80157
59100 Roubaix

Bonjour,

Vous avez souscrit aux services de téléphonie d'OVH et nous vous remercions de
votre confiance.

Votre compte client est validé et votre forfait est dès à présent opérationnel.

Un ensemble de guides, vous accompagne pas à pas dans la gestion de vos services téléphonies :





Pour profiter pleinement de votre offre, voici les paramètres de votre téléphone SIP :
Numéro de téléphone : 023 18xxxx

Paramètres de connexion :

Login / User name : 00322318xxxx
Mot de passe : xxxx
Authorization user name : 00322318xxxx
Domain / Registrar : sip.ovh.be

Cordialement,

L'équipe Téléphonie d'OVH

I am willing to communicate together. I'll send you my phone number in a private message.

I'm not Belgian and I don't have the same user experience with OVH, which I find a bit confusing sometimes, and I don't understand these issues with phone support, which is a bit hard to reach but resolves problems without extra cost.

Regarding VoIP:

  1. Indeed, you first need to get the number that belongs to OVH working before tackling the ported number(s).
  2. OVH's SIP server(s) have protection mechanisms that can trigger when you try with wrong settings, so when you use the correct ones they may not work right away and can be frustrating – just wait a bit.
  3. The useful settings (login, domain, proxy…) are on the "management" → "general information" page of the SIP account (the number belonging to OVH), except for the password. Could you provide a screenshot of this page (masking the last digits if you wish)?
  4. The password is set by you on the "management" → "SIP password" page of the SIP account (the number belonging to OVH) – if you lose it, you won't be able to retrieve it; you'll need to set a new one.
  5. The SIP account usage can be limited to one or more IP addresses or IP ranges on the "management" → "SIP restrictions by IP" page; the simplest way to start is to set no restrictions.

The Gigaset 685 IP configuration looks a bit cryptic, and Gaston will soon suggest trying it with Zoiper on a desktop computer or a smartphone to make sure everything is fine on the OVH side.

Also note that on the "Call Management" → "Call Forwarding" page you can redirect incoming calls to another number (mobile, for example). I don’t understand "prices that appear very advantageous – even national calls to landlines would be included, but with "registration fail", I’m not even reachable"… which also mixes outgoing and incoming calls.

That's what I did three hours ago.

https://wordetweb.com/word-et-web/Softphones-zoiper-android-exemple-configuration-FR.htm in a private message

I had missed that in your long prose.
I have a Gigaset C470IP.
Here are settings that work. I set this up many years ago and haven't touched it since.

Hello everyone, and many thanks for your very kind engagement. Sorry for my delay, which was due to my health condition; I am in my seventies.

I spent another 3 hours on additional testing, and I give up now, for the Siemens‑Gigaset with OVH.

Here are my results (i.e. not opinions/ideas but results, after relevant tests; I’ll spare you the bulk of the details):

I had already read and reread the page https://wordetweb.com/word-et-web/Telephone-VoIP-SIP-OVH-A510IP-echec-enregistrement-FR.htm since it had also been referenced on another help request here, from a user of a Siemens‑Gigaset phone; obviously, replacing sip-domain.io (in my case) with 91.121.129.20 yields no expected result, and I obviously don’t know whether it worked back then for sipp.ovh.net (or maybe sip.ovh.net? typo?) or not.

.

Installing Zoiper (free, otherwise it’s more than 70 € including VAT) on my PC was successful, but I want to be reachable via a landline = physical device, not by leaving my PC on 24 hours a day; Zoiper’s indications:

"testing possible configurations"

sip tls > pro

sip tcp > not found

sip udp found

aix udp not found

Accounts: my sip‑ovh number, "Add" > pro (and therefore, for my ported number, I would need Pro anyway)

"Advanced":

use stun: YES

stun server: stun.zoiper.com (sic! zoiper, not OVH; on my Siemens I therefore tried stun.sip-domains.io, stun.sip.ovh.net, etc., but without positive result, see below)

stun port: 3478

stun refresh period: 30 (=seconds I suppose)

"TLS Options" > Pro

"Network" (so on the client side):

sip options: port 5060 (open random available ports YES)

IAX options: port 4569 (open random... YES)

RTP options: port 8000 (open random... YES)

= these settings obviously DO NOT match OVH’s instructions (see above) BUT the line with Zoiper seemed to be set that way indeed (I didn’t try to call but Zoiper would have given an error otherwise, I guess).

.

No attempt to copy these settings, or any variants of them, onto my OVH account in Siemens was successful, but most of those attempts = settings in the OVH Siemens account caused even my other lines (=foreign) to stop working (!), even though in their respective Siemens accounts they work with/rely on STUN; the STUN settings in the OVH account of the device therefore invalidated/affected the STUN settings of the other accounts in the device, as did the SIP‑port (sip, rtp) settings in the "Advanced settings" range of the device: changing them never did anything good for my OVH account, but most of the time they invalidated/disconnected the other accounts as well.

.

This obviously also applies to the settings (and variants of them) that you, fritz2cCat, kindly attached: no chance in my case; I took the trouble to mention all my settings at the top because I can’t erase/cover the "private" information in my screenshots, which is why I didn’t attach any, otherwise I would have obviously done so; of course I could have taken screenshots, then printed them, then erased that information, then scanned the result, then attached the scans here, but the readability of such a scan would probably have been a bit doubtful, all those "gray" areas in the scan not being very well resolved...

.

The results so far, and their comparison with OVH’s original information, already show without any discussion that OVH’s information is partially false and anyway insufficient: there are very important gaps in it, and the fact that they SELL you the rest over the phone is a legal loophole, close to fraud… – selling you those relevant pieces of information over the phone would nevertheless imply that at least the people in their call centre = "first line", point their experts, and for example, call‑centres for technical support (!) Apple employ people at the minimum rate (or was it 15 cents above per hour?), after a (paid) one‑month training, and that’s no joke, I can name such a call‑centre ("outsourced", obviously) Apple uses here in Western Europe: in short, it’s total nonsense, but that said, I don’t know the quality of OVH’s call‑centre support, yet in any case, ALL technical information = technical access conditions for the paid service to be provided by OVH MUST be communicated for free, legally, and OVH does not do that, as the comparison between the data freely disclosed by OVH (=email, website) and the data revealed by Zoiper proves immediately:

OVH is therefore at fault, legally, but that’s another matter to win against OVH before a French court… and if we also enjoy comparing photos of Ivo Livi (=Yves Montand) with those of the (then‑young) daughter of the woman who had been in a relationship with the gentleman, but who (the daughter again now) was denied any possible "filial" relationship by the French justice system in the final instance, of all "possible" parentage… but most likely, I’m the only one who has a completely skewed view of things (and of physiognomies, and of French affairs)…

.

My Siemens‑Gigaset is about 15 years old (the build quality was still impeccable in Germany back then, but those days are over...), and then Gigaset was no longer Siemens, and then it disappeared completely (=bankruptcy); the apparent success with the Zoiper software (=modern) gave me the idea that a modern SIP phone (=hardware) could also be "smart" enough to connect with OVH;

so I plan to buy (not from OVH at probably double price, nor rent from them) a SIP phone (around €230 in Germany, €250 in France, two months ago €190!!! – probably €350 in Belgium...), and redo my tests again, with that, before returning it to the seller in case of failure – that’s the ONLY advantage of the EU for us consumers.

.

I also found an operator where I could park my ported number for €2.50 per month (=in case even a modern SIP phone fails to connect to OVH), plus the communications obviously, no free calls to landlines in 40 countries…;

in this context, one must know – but again, "no one" actually knows, before falling into the trap themselves – that using a foreign outbound number (in my case, the operator of my foreign numbers), just by hiding the number when calling, the Belgian/French number being reachable (almost "for free") inbound, has been made impossible by the aforementioned EU because for several years now – total EU policing (and yeah yeah yeah, total EU chat censorship will soon be just for our own good too, but of course Madame President!) – it forces operators to CUT cross‑border calls with hidden numbers after a few seconds… which makes most of your "official" calls (administrations, sellers, craftsmen, doctors, etc.) impossible because then their own systems refuse to take the call, for an unsuitable number, or you end up in lengthy discussions… hence the need for a "national" number = Belgian in my case, even outbound; I might even be interested in subscribing to a mobile plan, instead of fixating so much on a / my "fixed" number… :wink:

.

So I’ve given you some info you didn’t know yet, instead of receiving the info I’m missing, but it seems obvious that OVH sits on that information, disclosing it only for money. ;-(

.

Happy Pentecost weekend everyone! :slight_smile:

1300 words just to end up concluding nothing, … sorry, I’m giving up on this conversation.

Using STUN is generally unnecessary.

That's all I had to say, I'm also giving up on the conversation.

Problem solved = Help for others, with recent or soon‑to‑be‑created "accounts":

My current settings (on Gigaset S685 IP) that work fine:
1)
Telephony - Advanced Settings = for all lines, OVH and others:
Use random ports NO
SIP port 5064
RTP port 5004‑5020
2)
Telephony - Connections - OVH = the specific line:
Authentication Name and Username = identical (entered twice), as recommended by OVH
Authentication password = same
Domain, Proxy server address and Registrar server: sip‑domain.io (entered three times)
Proxy server port and Registrar server port: identical, both 5064 !!!!!
Registration refresh time: 180 s
Network - Stun enabled No
Stun server left empty, stun port 3478 but seems irrelevant, same for stun refresh time 240 s
NAT refresh time 180 s (I'm not sure if this is related to Stun and may also be irrelevant)
Outbound proxy: xxx (the proxy indicated by OVH)
Outbound proxy port: 5060 !!!

Possible additional help under c) below:

Comments:

a) Obviously, OVH changes the prerequisites/settings that need to be set, perhaps even, to some extent, for existing installations after a while, and especially for new servers – compare the sip‑domain.io above with your older servers: unfortunately, your information about those is no longer relevant for the latest ones.

b) Compare my data also with the information provided by OVH: https://docs.ovhcloud.com/fr/guides/web-cloud/phone-and-fax/voip/faq-voip/ and https://docs.ovhcloud.com/fr/guides/web-cloud/phone-and-fax/voip/troubleshoot-local-network/ – I have saved screenshots as possible proof: it shows that OVH does NOT keep the information – which is necessary for customers – up to date, let alone specifying which settings apply to which generation of servers; this, combined with their policy of selling every bit of assistance (charged by the minute on the phone), means they do NOT answer emails requesting the current information – which is unacceptable.

c) I don't know how I ended up here in my random trials: by pure chance, or with the secret help of the Zoiper application (which, as discussed above, is installed on my PC AND worked) because during my "old" tests Zoiper was installed but not active; this time when I tried on the physical phone it was active: it is therefore not impossible that it was involved somehow, having changed things deliberately or, more likely, as a "side effect" the data of the physical‑phone software – the phone not only being, like the PC, turned on (and thus the Zoiper app active), connected to the same router, but also the phone software was open and "on" the OVH line settings screen in my browser on that same PC; so there is a chance that Zoiper "infected" (independently of the fact that its own connection settings are totally different) the Gigaset software, either on my PC or via the router.

If the data above does not help other OVH VoIP users – for example because OVH keeps changing the required values without communicating them – the test with Zoiper "running" during their trials with the phone software on the same PC would not be completely far‑fetched; moreover, my data seem to show that OVH's indications are not only wrong (see the links) but partly absurd ("30000‑40000"): trying with much more "normal" values would therefore be the strategy to follow.

d) Since they assign the ported number as the number associated with the number they give you anyway, there's no need to repeat my mistake, but it would be much better to first ask them for the line, try to install it on your phone, and only then, if and when that OVH SIP line works, request the number porting: its attachment to the line will then take only half a minute.

Hello @ovhnogood

I’m glad to see that the trials with Zoiper worked very quickly and allowed you to then make the proper adjustments on the other equipment.

The solutions that work well with OVH SIP: Zoiper or Linphone. On Android, you need to properly configure the power‑saver so it rings without the app stopping.