Erreur 403 trunck OVH - Asterix
... / Erreur 403 trunck OVH - A...
BMPCreated with Sketch.BMPZIPCreated with Sketch.ZIPXLSCreated with Sketch.XLSTXTCreated with Sketch.TXTPPTCreated with Sketch.PPTPNGCreated with Sketch.PNGPDFCreated with Sketch.PDFJPGCreated with Sketch.JPGGIFCreated with Sketch.GIFDOCCreated with Sketch.DOC Error Created with Sketch.
Question

Erreur 403 trunck OVH - Asterix

by
BenjaminL16
Created on 2018-10-24 09:06:15 (edited on 2024-09-04 13:54:16) in Forfaits VoIP

Bonjour à vous,
Cela fait maintenant plusieurs semaines que je fais le ping pong sans succès entre OVH et mon fournisseur de call center Ladesk.

Nous suivons pourtant les demandes de OVH :

- Le trafic vers les réseaux 91.121.128.0/24 et 91.121.129.0/24 doit être autorisé.
- Pour le protocole SIP : le trafic doit être autorisé sur les ports 5060 et 5962 en UDP.

- La durée de vie des sessions UDP (Time/Timeout/NAT Session) doit être supérieure ou égale à 180 secondes.
- La fonction SIP ALG doit être désactivée sur les équipements actifs (si possible).
- Pour une ligne sans Plug&Phone : le client SIP utilisé doit avoir une durée d'enregistrement de 1800 secondes.

Pour obtenir une qualité de communication optimale, assurez vous que les valeurs suivantes sont bonnes :
- Le débit disponible recommandé est de 100kbps par ligne (envoi ET réception).

- La gigue* idéale est inférieure à 5ms (La gigue est la variation de la latence : la téléphonie est extrêmement sensible à ce paramètre.).


Les techniciens de Ladesk ne comprennent pas pourquoi les appels entrant et sortant sont rejetés alors que la ligne est bien enregistré. OVH ne retourne aucune information de leur coté...
"Registration - OK
KeepAlive - OK
Incoming calls - OK
Outbound call - still the same error from ovh 403 - not registered, despite the fact that registration was successful, and keepalive packets go smoothly. And incoming call was successful 10 sec before.
"
Ci joint les logs :

INVITE sip:00421233057090@siptrunk.ovh.net:5060 SIP/2.0
Via: SIP/2.0/UDP 85.159.211.124:5060;rport;branch=z9hG4bKPjca6d74f3-1b6f-4f97-a135-17ffa58c268c
From: ;tag=3b2e84aa-4329-47e1-b72f-64c7534b4a18
To:
Contact:
Call-ID: c90abe06-5548-4f50-9002-08d2b6bf7bcd
CSeq: 1403 INVITE
Route:
Allow: OPTIONS, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, REGISTER, MESSAGE, REFER
Supported: 100rel, timer, replaces, norefersub
Session-Expires: 1800
Min-SE: 90
Remote-Party-ID: "0033972585551" ;privacy=off;screen=no
Max-Forwards: 70
User-Agent: Ladesk Media GW
Content-Type: application/sdp
Content-Length: 209

v=0
o=- 2044981830 2044981830 IN IP4 85.159.211.124
s=Asterisk
c=IN IP4 85.159.211.124
t=0 0
m=audio 14584 RTP/AVP 0 8
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=ptime:20
a=maxptime:150
a=sendrecv
INVITE sip:00421233057090@siptrunk.ovh.net:5060 SIP/2.0
Via: SIP/2.0/UDP 85.159.211.124:5060;rport;branch=z9hG4bKPjca6d74f3-1b6f-4f97-a135-17ffa58c268c
From: ;tag=3b2e84aa-4329-47e1-b72f-64c7534b4a18
To:
Contact:
Call-ID: c90abe06-5548-4f50-9002-08d2b6bf7bcd
CSeq: 1403 INVITE
Route:
Allow: OPTIONS, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, REGISTER, MESSAGE, REFER
Supported: 100rel, timer, replaces, norefersub
Session-Expires: 1800
Min-SE: 90
Remote-Party-ID: "0033972585551" ;privacy=off;screen=no
Max-Forwards: 69
User-Agent: Ladesk Media GW
Content-Type: application/sdp
Content-Length: 209

v=0
o=- 2044981830 2044981830 IN IP4 85.159.211.124
s=Asterisk
c=IN IP4 85.159.211.124
t=0 0
m=audio 14584 RTP/AVP 0 8
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=ptime:20
a=maxptime:150
a=sendrecv
SIP/2.0 100 Giving a try
Via: SIP/2.0/UDP 85.159.211.124:5060;received=85.159.211.124;rport=5060;branch=z9hG4bKPjca6d74f3-1b6f-4f97-a135-17ffa58c268c
From: ;tag=3b2e84aa-4329-47e1-b72f-64c7534b4a18
To:
Call-ID: c90abe06-5548-4f50-9002-08d2b6bf7bcd
CSeq: 1403 INVITE
Server: Ladesk SIP Proxy
Content-Length: 0

SIP/2.0 100 Giving a try
Via: SIP/2.0/UDP 85.159.211.124:5060;received=85.159.211.124;rport=5060;branch=z9hG4bKPjca6d74f3-1b6f-4f97-a135-17ffa58c268c
From: ;tag=3b2e84aa-4329-47e1-b72f-64c7534b4a18
To:
Call-ID: c90abe06-5548-4f50-9002-08d2b6bf7bcd
CSeq: 1403 INVITE
Server: Ladesk SIP Proxy
Content-Length: 0

INVITE sip:00421233057090@siptrunk.ovh.net:5060 SIP/2.0
Record-Route:
Via: SIP/2.0/UDP 80.85.84.25:5060;branch=z9hG4bK0ec9.d874d372.0
Via: SIP/2.0/UDP 85.159.211.124:5060;received=85.159.211.124;rport=5060;branch=z9hG4bKPjca6d74f3-1b6f-4f97-a135-17ffa58c268c
From: ;tag=3b2e84aa-4329-47e1-b72f-64c7534b4a18
To:
Contact:
Call-ID: c90abe06-5548-4f50-9002-08d2b6bf7bcd
CSeq: 1403 INVITE
Allow: OPTIONS, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, REGISTER, MESSAGE, REFER
Supported: 100rel, timer, replaces, norefersub
Session-Expires: 1800
Min-SE: 90
Remote-Party-ID: "0033972585551" ;privacy=off;screen=no
Max-Forwards: 69
User-Agent: Ladesk Media GW
Content-Type: application/sdp
Content-Length: 209
P-hint: outbound

v=0
o=- 2044981830 2044981830 IN IP4 85.159.211.124
s=Asterisk
c=IN IP4 85.159.211.124
t=0 0
m=audio 14584 RTP/AVP 0 8
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=ptime:20
a=maxptime:150
a=sendrecv
SIP/2.0 403 not registered
Call-ID: c90abe06-5548-4f50-9002-08d2b6bf7bcd
CSeq: 1403 INVITE
From: ;tag=3b2e84aa-4329-47e1-b72f-64c7534b4a18
Record-Route:
To: ;tag=06-32093-0bb876d4-0c7f4b8d6
Via: SIP/2.0/UDP 85.159.211.124:5060;received=85.159.211.124;rport=5060;branch=z9hG4bKPjca6d74f3-1b6f-4f97-a135-17ffa58c268c
Content-Length: 0

SIP/2.0 100 Trying
Call-ID: c90abe06-5548-4f50-9002-08d2b6bf7bcd
CSeq: 1403 INVITE
From: ;tag=3b2e84aa-4329-47e1-b72f-64c7534b4a18
To:
Via: SIP/2.0/UDP 80.85.84.25:5060;received=80.85.84.25;rport=5060;branch=z9hG4bK0ec9.d874d372.0,SIP/2.0/UDP 85.159.211.124:5060;received=85.159.211.124;rport=5060;branch=z9hG4bKPjca6d74f3-1b6f-4f97-a135-17ffa58c268c
Content-Length: 0

SIP/2.0 403 not registered
Call-ID: c90abe06-5548-4f50-9002-08d2b6bf7bcd
CSeq: 1403 INVITE
From: ;tag=3b2e84aa-4329-47e1-b72f-64c7534b4a18
Record-Route:
To: ;tag=06-32093-0bb876d4-0c7f4b8d6
Via: SIP/2.0/UDP 80.85.84.25:5060;received=80.85.84.25;rport=5060;branch=z9hG4bK0ec9.d874d372.0,SIP/2.0/UDP 85.159.211.124:5060;received=85.159.211.124;rport=5060;branch=z9hG4bKPjca6d74f3-1b6f-4f97-a135-17ffa58c268c
Content-Length: 0

sip:00421233057090@siptrunk.ovh.net:5060 SIP/2.0
Via: SIP/2.0/UDP 80.85.84.25:5060;branch=z9hG4bK0ec9.d874d372.0
From: ;tag=3b2e84aa-4329-47e1-b72f-64c7534b4a18
Call-ID: c90abe06-5548-4f50-9002-08d2b6bf7bcd
To: ;tag=06-32093-0bb876d4-0c7f4b8d6
CSeq: 1403 ACK
Max-Forwards: 70
User-Agent: Ladesk SIP Proxy
Content-Length: 0

SIP/2.0 403 not registered
Call-ID: c90abe06-5548-4f50-9002-08d2b6bf7bcd
CSeq: 1403 INVITE
From: ;tag=3b2e84aa-4329-47e1-b72f-64c7534b4a18
Record-Route:
To: ;tag=06-32093-0bb876d4-0c7f4b8d6
Via: SIP/2.0/UDP 85.159.211.124:5060;received=85.159.211.124;rport=5060;branch=z9hG4bKPjca6d74f3-1b6f-4f97-a135-17ffa58c268c
Content-Length: 0

sip:00421233057090@siptrunk.ovh.net:5060 SIP/2.0
Via: SIP/2.0/UDP 85.159.211.124:5060;rport;branch=z9hG4bKPjca6d74f3-1b6f-4f97-a135-17ffa58c268c
From: ;tag=3b2e84aa-4329-47e1-b72f-64c7534b4a18
To: ;tag=06-32093-0bb876d4-0c7f4b8d6
Call-ID: c90abe06-5548-4f50-9002-08d2b6bf7bcd
CSeq: 1403 ACK
Route:
Max-Forwards: 70
User-Agent: Ladesk Media GW
Content-Length: 0

sip:00421233057090@siptrunk.ovh.net:5060 SIP/2.0
Via: SIP/2.0/UDP 85.159.211.124:5060;rport;branch=z9hG4bKPjca6d74f3-1b6f-4f97-a135-17ffa58c268c
From: ;tag=3b2e84aa-4329-47e1-b72f-64c7534b4a18
To: ;tag=06-32093-0bb876d4-0c7f4b8d6
Call-ID: c90abe06-5548-4f50-9002-08d2b6bf7bcd
CSeq: 1403 ACK
Route:
Max-Forwards: 69
User-Agent: Ladesk Media GW
Content-Length: 0

sip:00421233057090@siptrunk.ovh.net:5060 SIP/2.0
Via: SIP/2.0/UDP 85.159.211.124:5060;rport;branch=z9hG4bKPjca6d74f3-1b6f-4f97-a135-17ffa58c268c
From: ;tag=3b2e84aa-4329-47e1-b72f-64c7534b4a18
To: ;tag=06-32093-0bb876d4-0c7f4b8d6
Call-ID: c90abe06-5548-4f50-9002-08d2b6bf7bcd
CSeq: 1403 ACK
Route:
Max-Forwards: 69
User-Agent: Ladesk Media GW
Content-Length: 0


En vous remerciant pour votre aide :)


1 Reply ( Latest reply on 2018-11-30 10:16:18 by
AlainB17
)

Diantre, cela ressemble bigrement à mon https://community.ovh.com/t/impossible-dappeler-un-numero-avec-pjsua/12518 problème.
Avez-vous trouvé une solution?

Alain