Command needs to be changed on this guide

Step 3: Restart the interface
You now need to restart your interface:
/etc/init.d/ipaliases restart

"/etc/init.d/ipaliases restart" returns :

[root@centos ~]# /etc/init.d/ipaliases restart
-bash: /etc/init.d/ipaliases: No such file or directory

Correct command:
[root@centos ~]# /etc/init.d/network restart
Restarting network (via systemctl):

Running this command in order to deploy a Jenkins intance:
helm install --set Master.ServiceType=NodePort stable/jenkins
I have a deprecation warning, the correct syntax is
helm install --set master.servicetype=NodePort stable/jenkins

Helm version: Client: &version.Version{SemVer:"v2.14.2", GitCommit:"a8b13cc5ab6a7dbef0a58f5061bcc7c0c61598e7", GitTreeState:"clean"} Server: &version.Version{SemVer:"v2.14.2", GitCommit:"a8b13cc5ab6a7dbef0a58f5061bcc7c0c61598e7", GitTreeState:"clean"}

Hi, I have found your tutorial « How to deploy a web service for YOLOv5 using your own weights with Flask » at https://docs.ovh.com/gb/en/ai-training/web-service-yolov5/ which is very interesting.
I am trying your code but it seems to me that index.html is missing. Would be great if you could add that file. Thank you in advance !

Hi,

your docs recommend using stash for backups. The docs fail to mention that stash can only be used free of charge for non-commercial projects.

Probably because the change is only a moth old, see https://blog.byte.builders/post/relicensing/

title: 'Entrer, automatiser et gérer le paiement ainsi que la facturation Entreprise'
excerpt: 'Gérer le paiement et la facturation de vos services OVH'
slug: ovh-api-service
section: 'OVH APIv6'

Dernière mise à jour le 06/11/2019

Objectif

Nous allons décrire une partie du cycle de gestion de votre paiement et de votre facturation Entreprise chez OVHcloud

Prérequis

• Être connecté aux API OVH{.external}.
• Avoir créé ses identifiants pour l'API OVH{.external}.
• Avoir créé des sous-comptes pour l'API OVH si nécéssaire{.external}.
• Avoir à minima le niveau de support de type Business ou Enterprise

En pratique

Ressources

• xxx : xxx
• xxx : xxx

Déroulement des opérations

Ajout du moyen de paiement de type virement SEPA

Contacter votre commercial en précisant le délai de paiement souhaité (exemple: 30 ou 45 ou 60 jours en France)

Des attributs supplémentaires seront rajoutés à votre compte pour autoriser le moyen de paiement de type virement SEPA, pour indiquer le délai de paiement et pour activer l'autorenew permanent

Dans l'APIv6, dans vos moyens de paiement apparaitra un nouveau de paiement appelé avec un nom du type : "PaymentEnterprisewithxxdaysdelays"

Récupérer les factures des sous-comptes

Utiliser l'id de votre sous-compte obtenu et la consumerkey afin de vous connecter sur l'APIv6.

Récupérer la liste des factures associées à ce sous-compte

[!api]

@api {GET} /me/bill

Récupérer la facture détaillé grâce l'identifiant de votre facture billID

[!api]

@api {GET} /me/bill/{billId}/details

Aller plus loin

Échangez avec notre communauté d’utilisateurs sur https://community.ovh.com/.

On this guide, when you execute the following command on a 5.5 MySQL :

mysqldump --host=adresse_du_serveur --user=nom_utilisateur --password=mot_de_passe_utilisateur nom_base_de_données > nom_fichier_sauvegarde.sql

the dump succeed but showing the following error :

'Access denied; you need (at least one of) the PROCESS privilege(s) for this operation' when trying to dump tablespaces

To prevent this error, add the option --no-tablespaces to the command, like this :

mysqldump --host=adresse_du_serveur --user=nom_utilisateur --password=mot_de_passe_utilisateur --no-tablespaces nom_base_de_données > nom_fichier_sauvegarde.sql

If I want to write new tutorials from github, I can't test if the rendering is good because all configuration of your grav is missing and documentation to help the compilation are missing :(

Can you add

• The doc of the doc
• Your customs code to compile specific guideslines?

It is not specified how to solve this "Indica il codice di autorizzazione successivamente nel tuo Spazio Cliente OVH".

docs/pages/web/domains/transfer_incoming_generic_domain/guide.it-it.md

When we run step by step this guide, we run a problem

Events:
  Type     Reason              Age                   From                         Message
  ----     ------              ----                  ----                         -------
  Warning  ProvisioningFailed  81s (x26 over 7m25s)  persistentvolume-controller  storageclass.storage.k8s.io "cinder-high-speed" not found

because

storageClassName: cinder-high-speed

does not work, (not found).
I think it should be replaced by:

 storageClassName: csi-cinder-high-speed

Bonjour,

Dans la page pages/telecom/voip/asterisk_configuration_et_utilisation/guide.fr-fr.md, les sauts de ligne dans les sorties du terminal ou les configurations manquent, rendant la lecture du document difficile.

Le cookbook affirme « Via la méthode PUT /sms/{serviceName} vous allez pouvoir mettre en place un appel Callback à chaque réponse reçu, vous serez notifié en temps réel des réponses. » mais ne décrit pas de quelle manière c'est possible en utilisant l'API. La méthode PUT sur /sms/{serviceName} possède un grand nombre de paramètres, y compris 2 paramètres de callback.

Hi,

Will reading the documentation about 'order your metrics project' on the following page: https://docs.ovh.com/fr/metrics/order/, I found a broken link shortly after 'step 5 Grab your endpoints'. The link points to: https://docs.ovh.com/fr/metrics/protocol-overview, which is currently 404

Cheers,
W.

I tried to contact OVH support about this, but not answer :

In https://docs.ovh.com/gb/en/storage/pca/swift-commands-memo/ , nothing is said about the possibility to put a wildcard (*) in X-Container-Meta-Access-Control-Allow-Origin , but in https://docs.ovh.com/fr/storage/pcs/cors/ , it is said : " L’utilisation des wildcard est autorisé mais non recommandé : http://*.example.com "

Actually, I tested it, and wildcard DOES NOT seem to work in X-Container-Meta-Access-Control-Allow-Origin ( we can only set an exhaustive list of sub domains and the root domain, which is very annoying ).

Could we mention it in the documentation ? Why is it not possible to use wildcard ?

Regards.

Issue

Product NASHA had different names depending the documentation's language

❯ grep "title: " ./pages/cloud/storage/file_storage/nas_get_started/*
./pages/cloud/storage/file_storage/nas_get_started/guide.de-de.md:title: Erste Schritte mit einem HA-NAS
./pages/cloud/storage/file_storage/nas_get_started/guide.en-asia.md:title: Getting started with a HA-NAS solution
./pages/cloud/storage/file_storage/nas_get_started/guide.en-au.md:title: Getting started with a HA-NAS solution
./pages/cloud/storage/file_storage/nas_get_started/guide.en-ca.md:title: Getting started with a HA-NAS solution
./pages/cloud/storage/file_storage/nas_get_started/guide.en-gb.md:title: Getting started with a HA-NAS solution
./pages/cloud/storage/file_storage/nas_get_started/guide.en-ie.md:title: Getting started with a HA-NAS solution
./pages/cloud/storage/file_storage/nas_get_started/guide.en-sg.md:title: Getting started with a HA-NAS solution
./pages/cloud/storage/file_storage/nas_get_started/guide.en-us.md:title: Getting started with a HA-NAS solution
./pages/cloud/storage/file_storage/nas_get_started/guide.es-es.md:title: Primeros pasos con un NAS-HA
./pages/cloud/storage/file_storage/nas_get_started/guide.es-us.md:title: Primeros pasos con un NAS-HA
./pages/cloud/storage/file_storage/nas_get_started/guide.fr-ca.md:title: Premiers pas avec un NAS-HA
./pages/cloud/storage/file_storage/nas_get_started/guide.fr-fr.md:title: Premiers pas avec un NAS-HA
./pages/cloud/storage/file_storage/nas_get_started/guide.it-it.md:title: Iniziare a utilizzare un NAS-HA
./pages/cloud/storage/file_storage/nas_get_started/guide.pl-pl.md:title: Pierwsze kroki z usługą NAS HA
./pages/cloud/storage/file_storage/nas_get_started/guide.pt-pt.md:title: Primeiros passos com um NAS-HA

Side note

• www.ovhcloud.com is impacted too.
• Mentioned in ovh/docs !3484

In docs/pages/cloud/dedicated/network_ipv6/guide.en-ca.md it says every dedicated server gets a /64 IPv6 block, but on suggested Debian configuration it has net_mask 128.
I've checked my Debian servers (using OVH/Kimsufi's image) and my server IPv6 block is configured to /128 after a ip -6 addr list dev enp1s0.
The docs also does not use Debian's systemd configuration (systemd is the default init system on Debian since Jessie).
Between my servers inside OVH network I can ping the IPv6 addresses, but can't connect from outside using IPv6. What should I do?

Issue

The file storage section had a lot of mentions related to the legacy product NAS/miniNAS

Todo

Remove those references

Reference

A mention related to path was already made here: ovh/docs !3484

Toutes les src des images ne fonctionnent pas sur la page : https://docs.ovh.com/fr/dedicated/services-backup-storage/

Exemple : https://vgy.me/xpHA2M.png et https://vgy.me/aJf7Gr.png

Hi there,

In https://docs.ovh.com/de/publiccloud/databases/mysql/tutorial-connect-kubernetes-to-managed-mysql/#step-5-configure-your-options , you're recommending using a public network for the interconnection between Mysql and the Kubernetes cluster.

But In Discord, Bastien Verdebout mentioned:

Hello Sebastian Wagner indeed so far you need to select a private network option during DB creation. you cannot modify it once the clsuter is running. About best practices, having a private network will allow you to secure a bit more your infra, and benefit from more bandwidth. but you will need a gateway to connect to your DB (for example you cannot do laptop (postgre CLI ==> DB). you will need a vm inside you vrack with postgre CLI. that's not worse, it' in fact better since you can log this machine like a bastion, but it's something to know)

So, you should probably decide on a best practice.

https://docs.ovh.com/gb/en/kubernetes/vrack-k8s-custom-gateway/ also gave me some insights.

The guide to resize the partition (guide.fr-fr.md) is well explained and following up is easy, but just after creating the partition with 'p' in fdisk this message appears:

Created a new partition 1 of type 'Linux' and of size 20 GiB.
Partition #1 contains a ext4 signature.

Do you want to remove the signature? [Yes/[N]o: |

It would be great to add a line explaining what implies to remove or not the signature.

In your doc using_docker_on_public_cloud_instances, when using docker-machine create i had an error You must provide exactly one of DomainID or DomainName to authenticate by Username. Using openrc file exported from the ovh console is missing the OS_DOMAIN_NAME var.

When I create dns zone records they are assinged a nameserver with a number prefix.
So far for me it is always 12 (dns12.ovh.net and ns12.ovh.net)

The only place I found this mentioned is the warning in this section: https://github.com/ovh/docs/blob/develop/pages/web/domains/dns_server_general_information/guide.en-gb.md#modifying-dns-servers

My usecase is that we hand these nameservers out to custumers so we can setup their domain config for them.
It would be nice to always have the same address (or ip), that we can use for all our dns zones, so we can include it in our documentation.

So I have two questions:

• how are these servers assinged when I create a new dns zone (will I always get the same for all my dns zones that I create in the future)?
• can I somehow change the assinged servers?

Exposing services as LoadBalancer

- ### Exposing services as LoadBalancer
+### Exposing services as LoadBalancer

Hello,

In order to have endpoints specified in ~/.aws/config file working, you have to add the following lines in the file:

[plugins]
endpoint = awscli_plugin_endpoint

Hello,
Zonemaster developer here, I see that the Zonemaster related documentation has been removed in commit 430aff7 because it was flagged being deprecated. While the documentation (mainly the screenshots) was outdated the tool is very much still in development and can be used to test dns zones configuration.
Members of the Zonemaster team are willing to update the documentation if that can help to have it back.
Thanks,
Gaël Berthaud-Müller

https://github.com/ovh/docs/blob/develop/pages/cloud/dedicated/configuring-the-vrack-between-the-public-cloud-and-a-dedicated-server/guide.en-gb.md

These options aren't the same as the updated interface. I can only add a new private network and do not see options to add an existing vrack.

This page:

https://github.com/ovh/docs/blob/master/pages/cloud/storage/pca_dev/guide.en-gb.md

has a rendering bug at the middle of the page:

https://docs.ovh.com/gb/en/storage/pca/dev/

I am trying to send SMS using OVH'SMS service , following this docs.

when i test the send with post methode for the url https://eu.api.ovh.com/1.0/sms/sms-zj16668-1/jobs

i get an

errorCode:INVALID_SIGNATURE

the signature is calculated as below :

        String signature = "$1$" + HashSHA1(AS + "+" + CK + "+" + METHOD + "+" + QUERY + "+" + BODY + "+" + TSTAMP);

with Get method(no Body) i get a successful result , however when i change to use a Post method with a Body ,the above error is triggered.

this is the Body i pass to signature :

        string BODY = @"{  ""receivers"": [ ""+33601020304"" ], ""message"": ""Test SMS OVH"", ""senderForResponse"": true}";

what i m doing wrong ?

#update
i found in the ovh community a similar issue and the solution where to use TLS1.2 PROTOCOL , however even after adding this proposed line of code:

 ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls | (SecurityProtocolType)768 | (SecurityProtocolType)3072;

I am still getting the same error ! ?

Issue

We introduced a limit on NASHA partitions size. The sum of all partition size cannot exeed the NASHA size. This information is not mentionned in documentation.

#2388 was unfortunately rather incomplete leaving a huge gap in the docs:

From: https://docs.ovh.com/gb/en/kubernetes/using-lb/

Now users don't know how to deduce the automatically generated service-url form the IP. Took me a while to figure out that the advertised URL in the screenshot no longer exists.

Would also be good to at least mention the stability of the IPv4 as we no longer have a CNAME we can point to.

Refering to the discussion with the SoYouStart support, the IP list on page https://docs.ovh.com/fr/dedicated/monitoring-ip-ovh/ need to be updated.

Also, could you add a descripton for any IP of the list, please ?

It's unclear if all ip must be added or only some of them are required (depending of the client server localization such as rbx, gra, sbg etc)

I've gotten S3 working on my forums, but unfortunately I am unable to set up a cdn subdomain for my bucket. OVH is not clear about how this should be done. For reference, I've followed this guide: https://havecamerawilltravel.com/amazon-s3-bucket-cname/

I have a bucket named cdn.dyescape.com. I have created cdn.dyescape.com as a CNAME pointing to cdn.dyescape.com.s3.gra.perf.cloud.ovh.net. When accessing an image through the CDN subdomain (example https://cdn.dyescape.com/data/avatars/h/0/1.jpg?1676290270) I am seeing the below error;

<Error>
  <Code>InvalidRequest</Code>
  <Message>Invalid Request.</Message>
  <RequestId>txd90f03b160454969803b9-0063ea3e6a</RequestId>
  <Reason>Not S3 request</Reason>
</Error>

Accessing the same resource through the OVH provided URL works fine. Example: https://cdn.dyescape.com.s3.gra.perf.cloud.ovh.net/data/avatars/h/0/1.jpg?1676290270

I found this page which talks about subdomains for object storage on swift; https://docs.ovh.com/gb/en/storage/object-storage/pcs/link-domain/#with-cname. However, I don't know if this also refers to S3 buckets. The English on this page is also very poor and the overall writing makes it very difficult to follow or understand what's being done.

Further more, I cannot find the meaning of Not S3 request error anywhere. The only thing I found was some Python code for Swift where this error is thrown, but this doesn't clarify much either. https://github.com/openstack/swift/blob/master/swift/common/middleware/s3api/s3request.py#L686

Would appreciate some help getting this working. I'm willing to help rewrite / write new English documentation once I have it working. The current documentation is either missing, or not understandable.

Hello,

there is a typo in the exhaustiv list of authorized language suffixes in docs-guideline.md (l. 169)
must be cs-cz for czech guides, actual cz-cs

Hi,

For a customer who wants to deploy a big number of dedicated servers on OVH I am researching automating the process, and I am interested in taking advantage of the BYOI feature. Sadly, I have not been able to find any documentation on how to create those images, or even what are the technical specifications.

I would like to be able to control exactly how the servers are installed, ideally including disk partitioning. But I have no clue how to even start.

Thank you.

Bonjour,

Le lien https://eu.api.ovh.com/1.0/auth/credential est mort. Il se trouve sur cette page : https://docs.ovh.com/gb/en/customer/first-steps-with-ovh-api/ au deuxième paragraphe.

Merci d'avance !

Hi,

as I have a PCA account, I was waiting for duplicity 0.8 release since 8 months as it is supposed to handle PCA.
However in your article I see you use both a PCS and PCA account. Does this mean that we need to buy another PCS account just to make our PCA backups working with duplicity?

If this is the case, please state it clearly in the article content.

Hello,

The following page:

https://www.ovhcloud.com/en/public-cloud/object-storage/

states that:

Your data is distributed within clusters that have triple replication for each object. These replicas are placed on both different disks and servers, to ensure their longevity.

[...]

What SLA does OVHcloud offer for accessing the Object Storage service?

The SLA guarantees 99.9% monthly availability for accessing the Object Storage service. For further information, please refer to the Terms & conditions.
What SLA does OVHcloud offer for data resilience on the Object Storage service?

The data resilience rate is 100% for the Object Storage service. For further information, please refer to the Terms & conditions.

But it doesn't explain where the replication happens.

• If I create a bucket in the GRA region, is the replication happening in GRA? What if GRA burns down entirely?
• How is the 100% resilience guaranteed in this case? Is there an off-site cold storage? How much time to restore it?

I think those questions needs to be addressed in order to better understand the benefits/risks involved with the OVH Object Storage service, plan accordingly and avoid data loss.

Regards,

Issue

Available storage capacity are not up to date and do not list legacy capacity.

Proposal

Add a mention about legacy capacities and a link to the configurator

For 0xC004F074 error, add instruction from https://techcommunity.microsoft.com/t5/Windows-Server-for-IT-Pro/Server-2016-Activation/m-p/192788/highlight/true#M666

Hello

Issue

In : https://github.com/ovh/docs/blob/develop/pages/platform/kubernetes-k8s/getting-source-ip-behind-loadbalancer/guide.en-gb.md#1a-public-network-only-get-the-list-of-the-egress-load-balancer-ips

When your Managed Kubernetes cluster is attached to a vRack, load balancers will take two random IP addresses each. Your egress IP list is your subnet range.

For the rest of this documentation, we consider our subnet uses the 10.0.0.0/20 range. Don't forget to replace it with your own!

• When a user do not have access to the OVH console (my case), is there a way to know with only kubectl commands the "subnet range" that is expected ?

Todo

• Clarify the pre-requisites (OVH console?)
• Or provide a command to get the required info ( kubectl get nodes -o wide ? add external IP and internal IP ? Trying.. )

Reference

https://github.com/ovh/docs/blob/develop/pages/platform/kubernetes-k8s/getting-source-ip-behind-loadbalancer/guide.en-gb.md#1a-public-network-only-get-the-list-of-the-egress-load-balancer-ips

Regarding this tutorial:
https://docs.ovh.com/gb/en/kubernetes/installing-kubernetes-dashboard/

At least in version 1.6 the link should be:
http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard:/proxy/.
instead of:
http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/

So seems like the namespace was changed in the meantime from kube-system to kubernetes-dasboard.

File pages/web/domains/dns_dynhost/guide.en-ie.md doesn't explain any error(s) and etc. of the mentioned endpoint.

Right now I'm stuck pulling my hair out and trying to figure out what badsys response with HTTP status code of 200 mean. There isn't even a curl command example given.

The IP of my subdomain didn't change in the panel, dig still points to the old IP I've set manually in the panel and google returns no useful results.

Java code (okHttp library) that repoduces my issue:

    public void updateDnsOkHttp(String name, String target) throws Exception {
        log.info("Creating okHttp request");
        OkHttpClient client = new OkHttpClient();

        RequestBody body = RequestBody.create(null, new byte[0]);
        final String url = baseUrl.replaceFirst("HOSTNAME", name + "." + configuration.BASE_DOMAIN).replaceFirst("IP", target);
        Request request = new Request.Builder()
                .url(url)
                .post(body)
                .header("Content-Length", "0")
                .header("Authorization", Credentials.basic(configuration.OVH_USER, configuration.OVH_PASSWORD))
                .build();

        log.info("Executing request to: {}", url);
        Response response = client.newCall(request).execute();

        final String str = response.body().string();
        log.info("Got response: {}", str);

        final int code = response.code();
        log.info("Got response code: {}", code);

        if(code != 200) {
            throw new Exception("Couldn't update DNS record, response code: " + code);
        }
        if(str.startsWith("badsys")) {
            throw new Exception("Couldn't update DNS record");
        }
    }
    ```

Hi there,

I'm reading https://docs.ovh.com/gb/en/dedicated/secondary-dns/ but it doesn't say which IP address to whitelist for AXFR transfers.

I think this documentation should contain a network to whitelist for zone transfers.

Cheers

I wanted to try out stash followed the instructions here: https://docs.ovh.com/ca/en/kubernetes/backing-up-volumes-using-stash/
Getting the credentials via openstack ec2 credentials create worked fine - but the credentials won't work. aws cli: SignatureDoesNotMatch

Interestingly if I rename the profile [profile default] to for example [profile ovh], the error changes to:

aws --profile ovh s3 mb s3://s3-stash
make_bucket failed: s3://s3-stash An error occurred (InternalError) when calling the CreateBucket operation (reached max retries: 4): unexpected status code 500

I do believe that there cannot be a profile default and the default config would be under [default] and not [profile default] but I am not sure about that :]

Some images and markdown files have the executable flag.

Les anciennes docs relatives à vxml ne sont pas intégrées, je pense par exemple aux pages suivantes :

• http://aide.ovh.com/TelFaqSVIVXMLCreation
• http://aide.ovh.com/TelFaqSVIVXMLBalises

I recently deployed an K8s cluster with an internal network, this all works great but getting the source IP for HTTP requests is not documented.

1. The annotation lb.k8s.ovh.net/egress-ips is not added to the service
2. The egress IPs are also not accessible through the OVH api (or I couldn't figure out how)

After some trial and error and stumbling upon the following "known limitation" in the vRack docs

You will still see a public IPv4 address on your worker nodes. This IP won’t be reachable from the Internet, and used exclusively for the administration of your nodes and its link to the Kubernetes control plane.

I realized I should use my internal IP range as CIDR for setting this up correctly, so using the nginx helm chart as example I now have the following config stanza which works out for me.

controller:
  service:
    externalTrafficPolicy: "Local"
    annotations:
      service.beta.kubernetes.io/ovh-loadbalancer-balance: source
      service.beta.kubernetes.io/ovh-loadbalancer-proxy-protocol: "v2"
  config:
    use-proxy-protocol: "true"
    # Use subnet from internal network
    proxy-real-ip-cidr: "10.0.0.0/20" 

Please update the documentation accordingly, but if not, I hope the following helps other people out who run into the same issue.

I've downloaded the openrc.sh file from my ovh account. Using source openrc.sh reported me publicURL endpoint for compute service in GRA region not found. I had to edit the file and use GRA7. May be you should indicate to verify the OS_REGION_NAME var.

after identifing , in order to generate a token to be able to call the api from c#, we 've filled this form , but we didn't get the token informations :

• Application Key (identifie votre application)
• Application Secret (authentifie votre application)
• Consumer Key (autorise l’application à accéder aux méthodes choisies)

where can i find this generated fields ?

I'm using the proxmox7 template on my dedicated server.
The first thing I did after install is apt update && apt upgrade, this resulted in an error with grub-pc unable to write on /dev/md

The support directed me to this guide, and it was helpful, but not quite enough. What worked for me was :

--- boot en mode rescue64-pro ----

root@rescue:~# mount /dev/md126 /mnt
root@rescue:~# mount /dev/md125 /mnt/boot
root@rescue:~# mount -o bind /proc /mnt/proc
root@rescue:~# mount -o bind /sys /mnt/sys
root@rescue:~# mount -o bind /dev /mnt/dev
root@rescue:~# chroot /mnt /bin/bash
root@rescue:/# mount /dev/sda1 /boot/efi
root@rescue:/# grub-install --efi-directory=/boot/efi/
root@rescue:/# umount /boot/efi     
root@rescue:/# mount /dev/sdb1 /boot/efi
root@rescue:/# grub-install --efi-directory=/boot/efi/
root@rescue:/# reboot

---- boot sur hd -----

Bonjour,

Lorsque je recherche le terme "répondeur" dans la recherche de la doc, la page suivante https://docs.ovh.com/fr/voip/configurer-consulter-repondeur-ligne-ovh/ n'apparait pas.

Pouvez vous corriger cela ?