Avvisi di errore su Trunk e Telefoni

[Fabio A]

Ciao da un cliente circa una settimana fa senza eseguire nessuna modifica, si è verificato un problema sulla registrazione sip al provider risolta con un riavvio del PBX, ma sono rimarti due errori su Trunk e Telefoni che non riesco a rimuovere.

i messaggi sono
State utilizzando un trunk SIP non supportato che potrebbe causare errori.
Per un elenco dei trunk SIP supportati visitate questa pagina.

e

State utilizzando dei Telefoni Non Supportati oppure dei telefoni che utilizzano template personalizzati che potrebbero causare errori.
Per l' elenco dei Telefoni IP Supportati, visitate questa pagin

non è stata fatta nessuna modifica e il test firewall è ok

resolving 'stun-eu.3cx.com'... done
resolving 'stun2.3cx.com'... done
resolving 'stun3.3cx.com'... done
resolving 'sip-alg-detector.3cx.com'... done
testing 3CX SIP Server... done
stopping service... done
detecting SIP ALG... not detected
testing port 5060... done
starting service... done
testing 3CX Tunneling Proxy... done
stopping service... done
testing port 5090... done
starting service... done
testing 3CX Media Server... done
stopping service... done
testing ports [9000..9398]... done
testing port 9000... done
testing port 9002... done
testing port 9004... done
testing port 9006... done
testing port 9008... done
testing port 9010... done
testing port 9012... done
testing port 9014... done
testing port 9016... done
testing port 9018... done
testing port 9020... done
testing port 9022... done
testing port 9024... done
testing port 9026... done
testing port 9028... done
testing port 9030... done
testing port 9032... done
testing port 9034... done
testing port 9036... done
testing port 9038... done
testing port 9040... done
testing port 9042... done
testing port 9044... done
testing port 9046... done
testing port 9048... done
testing port 9050... done
testing port 9052... done
testing port 9054... done
testing port 9056... done
testing port 9058... done
testing port 9060... done
testing port 9062... done
testing port 9064... done
testing port 9066... done
testing port 9068... done
testing port 9070... done
testing port 9072... done
testing port 9074... done
testing port 9076... done
testing port 9078... done
testing port 9080... done
testing port 9082... done
testing port 9084... done
testing port 9086... done
testing port 9088... done
testing port 9090... done
testing port 9092... done
testing port 9094... done
testing port 9096... done
testing port 9098... done
testing port 9100... done
testing port 9102... done
testing port 9104... done
testing port 9106... done
testing port 9108... done
testing port 9110... done
testing port 9112... done
testing port 9114... done
testing port 9116... done
testing port 9118... done
testing port 9120... done
testing port 9122... done
testing port 9124... done
testing port 9126... done
testing port 9128... done
testing port 9130... done
testing port 9132... done
testing port 9134... done
testing port 9136... done
testing port 9138... done
testing port 9140... done
testing port 9142... done
testing port 9144... done
testing port 9146... done
testing port 9148... done
testing port 9150... done
testing port 9152... done
testing port 9154... done
testing port 9156... done
testing port 9158... done
testing port 9160... done
testing port 9162... done
testing port 9164... done
testing port 9166... done
testing port 9168... done
testing port 9170... done
testing port 9172... done
testing port 9174... done
testing port 9176... done
testing port 9178... done
testing port 9180... done
testing port 9182... done
testing port 9184... done
testing port 9186... done
testing port 9188... done
testing port 9190... done
testing port 9192... done
testing port 9194... done
testing port 9196... done
testing port 9198... done
testing port 9200... done
testing port 9202... done
testing port 9204... done
testing port 9206... done
testing port 9208... done
testing port 9210... done
testing port 9212... done
testing port 9214... done
testing port 9216... done
testing port 9218... done
testing port 9220... done
testing port 9222... done
testing port 9224... done
testing port 9226... done
testing port 9228... done
testing port 9230... done
testing port 9232... done
testing port 9234... done
testing port 9236... done
testing port 9238... done
testing port 9240... done
testing port 9242... done
testing port 9244... done
testing port 9246... done
testing port 9248... done
testing port 9250... done
testing port 9252... done
testing port 9254... done
testing port 9256... done
testing port 9258... done
testing port 9260... done
testing port 9262... done
testing port 9264... done
testing port 9266... done
testing port 9268... done
testing port 9270... done
testing port 9272... done
testing port 9274... done
testing port 9276... done
testing port 9278... done
testing port 9280... done
testing port 9282... done
testing port 9284... done
testing port 9286... done
testing port 9288... done
testing port 9290... done
testing port 9292... done
testing port 9294... done
testing port 9296... done
testing port 9298... done
testing port 9300... done
testing port 9302... done
testing port 9304... done
testing port 9306... done
testing port 9308... done
testing port 9310... done
testing port 9312... done
testing port 9314... done
testing port 9316... done
testing port 9318... done
testing port 9320... done
testing port 9322... done
testing port 9324... done
testing port 9326... done
testing port 9328... done
testing port 9330... done
testing port 9332... done
testing port 9334... done
testing port 9336... done
testing port 9338... done
testing port 9340... done
testing port 9342... done
testing port 9344... done
testing port 9346... done
testing port 9348... done
testing port 9350... done
testing port 9352... done
testing port 9354... done
testing port 9356... done
testing port 9358... done
testing port 9360... done
testing port 9362... done
testing port 9364... done
testing port 9366... done
testing port 9368... done
testing port 9370... done
testing port 9372... done
testing port 9374... done
testing port 9376... done
testing port 9378... done
testing port 9380... done
testing port 9382... done
testing port 9384... done
testing port 9386... done
testing port 9388... done
testing port 9390... done
testing port 9392... done
testing port 9394... done
testing port 9396... done
testing port 9398... done
testing ports [10600..10998]... done
testing port 10600... done
testing port 10602... done
testing port 10604... done
testing port 10606... done
testing port 10608... done
testing port 10610... done
testing port 10612... done
testing port 10614... done
testing port 10616... done
testing port 10618... done
testing port 10620... done
testing port 10622... done
testing port 10624... done
testing port 10626... done
testing port 10628... done
testing port 10630... done
testing port 10632... done
testing port 10634... done
testing port 10636... done
testing port 10638... done
testing port 10640... done
testing port 10642... done
testing port 10644... done
testing port 10646... done
testing port 10648... done
testing port 10650... done
testing port 10652... done
testing port 10654... done
testing port 10656... done
testing port 10658... done
testing port 10660... done
testing port 10662... done
testing port 10664... done
testing port 10666... done
testing port 10668... done
testing port 10670... done
testing port 10672... done
testing port 10674... done
testing port 10676... done
testing port 10678... done
testing port 10680... done
testing port 10682... done
testing port 10684... done
testing port 10686... done
testing port 10688... done
testing port 10690... done
testing port 10692... done
testing port 10694... done
testing port 10696... done
testing port 10698... done
testing port 10700... done
testing port 10702... done
testing port 10704... done
testing port 10706... done
testing port 10708... done
testing port 10710... done
testing port 10712... done
testing port 10714... done
testing port 10716... done
testing port 10718... done
testing port 10720... done
testing port 10722... done
testing port 10724... done
testing port 10726... done
testing port 10728... done
testing port 10730... done
testing port 10732... done
testing port 10734... done
testing port 10736... done
testing port 10738... done
testing port 10740... done
testing port 10742... done
testing port 10744... done
testing port 10746... done
testing port 10748... done
testing port 10750... done
testing port 10752... done
testing port 10754... done
testing port 10756... done
testing port 10758... done
testing port 10760... done
testing port 10762... done
testing port 10764... done
testing port 10766... done
testing port 10768... done
testing port 10770... done
testing port 10772... done
testing port 10774... done
testing port 10776... done
testing port 10778... done
testing port 10780... done
testing port 10782... done
testing port 10784... done
testing port 10786... done
testing port 10788... done
testing port 10790... done
testing port 10792... done
testing port 10794... done
testing port 10796... done
testing port 10798... done
testing port 10800... done
testing port 10802... done
testing port 10804... done
testing port 10806... done
testing port 10808... done
testing port 10810... done
testing port 10812... done
testing port 10814... done
testing port 10816... done
testing port 10818... done
testing port 10820... done
testing port 10822... done
testing port 10824... done
testing port 10826... done
testing port 10828... done
testing port 10830... done
testing port 10832... done
testing port 10834... done
testing port 10836... done
testing port 10838... done
testing port 10840... done
testing port 10842... done
testing port 10844... done
testing port 10846... done
testing port 10848... done
testing port 10850... done
testing port 10852... done
testing port 10854... done
testing port 10856... done
testing port 10858... done
testing port 10860... done
testing port 10862... done
testing port 10864... done
testing port 10866... done
testing port 10868... done
testing port 10870... done
testing port 10872... done
testing port 10874... done
testing port 10876... done
testing port 10878... done
testing port 10880... done
testing port 10882... done
testing port 10884... done
testing port 10886... done
testing port 10888... done
testing port 10890... done
testing port 10892... done
testing port 10894... done
testing port 10896... done
testing port 10898... done
testing port 10900... done
testing port 10902... done
testing port 10904... done
testing port 10906... done
testing port 10908... done
testing port 10910... done
testing port 10912... done
testing port 10914... done
testing port 10916... done
testing port 10918... done
testing port 10920... done
testing port 10922... done
testing port 10924... done
testing port 10926... done
testing port 10928... done
testing port 10930... done
testing port 10932... done
testing port 10934... done
testing port 10936... done
testing port 10938... done
testing port 10940... done
testing port 10942... done
testing port 10944... done
testing port 10946... done
testing port 10948... done
testing port 10950... done
testing port 10952... done
testing port 10954... done
testing port 10956... done
testing port 10958... done
testing port 10960... done
testing port 10962... done
testing port 10964... done
testing port 10966... done
testing port 10968... done
testing port 10970... done
testing port 10972... done
testing port 10974... done
testing port 10976... done
testing port 10978... done
testing port 10980... done
testing port 10982... done
testing port 10984... done
testing port 10986... done
testing port 10988... done
testing port 10990... done
testing port 10992... done
testing port 10994... done
testing port 10996... done
testing port 10998... done
starting service... done

 

[MarcelloL_3CX]

Ciao,
ma stai usando trunk e telefoni non supportati?

 

[Fabio A]

No hanno dei yealink w56h e un T46s, sempre usati mai modificato nulla, volevo solo segnalare che un collega ha iniziato a utilizzare l'app dal cellulare ma l' abbiamo testata altre volte senza problemi, ma ora la stiamo usando piu' intensamente.

Il trunk è quello che funziona ormai da anni senza problemi

 

[MarcelloL_3CX]

ma i telefoni in questione come appaiono nella schermata Telefoni? segnalano template personalizzati o firmware "scaduto"?
e il trunk fa parte della lista dei supportati?
do anche per scontato che centralino, template e firmware siano aggiornati, confermi?

 

[Fabio A]

il trunk è di un fornitore dove ho quasi tutti i clienti che gestiamo in azienda, unico errore su tutti gli interni ho un simbolo triangolare rosso che dice CODICE ROSSO - Interno non sicuro e Registrazione Esterna consentiti. Risolvere immediatamente . Requisiti Minimi : 10 caratteri, 1 lettera minuscola, 1 maiuscola e 1 cifra. controlla queste aree: ID Autore, Password autore, Password Webclient.

Grazie

 

[MarcelloL_3CX]

quindi hai un trunk non supportato...e i telefoni hanno firmware aggiornato e template 3CX?

 

[Fabio A]

il fornitore del trunk è nella lista dei certificati essendo il principale fornitore dei servizi di fonia del cliente in questione.

ho altri clienti con stessa versione di 3cx e stessi telefoni senza problemi, potrebbe essere una soluzione aggiornare alle versione New 16.0 Update 6a

nel log degli eventi ho i seguenti errori:

• SIP request (REGISTER) from 95.111.253.64 was rejected. Reason: Block WAN requests is ON. Message: REGISTER sip:81.63.154.161 SIP/2.0 Via: SIP/2.0/UDP 10.10.10.16:7579;branch=z9hG4bK9022d741-c157-4eb2-9977-5494f3ad8480;rport=7579;received=95.111.253.64 Max-Forwards: 70 Contact: <sip:[email protected]:7579;rinstance=a5cb4b3b4aee8546> To: "311"<sip:[email protected]> From: "311"<sip:[email protected]>;tag=fsvwhyiq Call-ID: rbksoryvfajubfmovkctprrscfewurylixtnygipfhciflmyaf CSeq: 2 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE Proxy-Authorization: Digest username="311",realm="3CXPhoneSystem",nonce="414d535c163f2ff164:639b443a5e0b947d37eb364fdcb83c0b",response="da3dc5d321696e3622b0edbd974dcf73",uri="sip:81.63.154.161",algorithm=MD5 Supported: 100rel User-Agent: PolycomVVX-VVX_401-UA5.4.1.18405 Content-Length: 0
  SIP Server ID: 12291 18/02/2021 18:08:01
• SIP request (REGISTER) from 193.29.106.22 was rejected. Reason: Block WAN requests is ON. Message: REGISTER sip:81.63.154.161 SIP/2.0 Via: SIP/2.0/UDP 10.10.10.13:8243;branch=z9hG4bK7a77b79d-e5d5-459f-83ab-63be11a8d870;rport=8243;received=193.29.106.22 Max-Forwards: 70 Contact: <sip:[email protected]:8243;rinstance=dc8996febd01f145> To: "301"<sip:[email protected]> From: "301"<sip:[email protected]>;tag=agfpsybo Call-ID: cxlgrtmplcalnsrelfkmxcvvauwnligjlxwhpamvyyvyuwdbko CSeq: 2 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE Proxy-Authorization: Digest username="301",realm="3CXPhoneSystem",nonce="414d535c163f2dc479:9b5289e5326c577bef2429ddc92b1cef",response="dee3203b39e49b7a4611be7ec499f139",uri="sip:81.63.154.161",algorithm=MD5 Supported: 100rel User-Agent: PolycomVVX-VVX_401-UA5.4.1.18405 Content-Length: 0
  SIP Server ID: 12291 18/02/2021 17:58:44
• Lost Call in Queue Coda Davesco (900) from Caller ID '0763217171' Queue: 900 [Coda Davesco] caller: 0763217171
  3CXQueueManager ID: 105 18/02/2021 17:34:24
• The IP 37.49.229.192 has been blacklisted for 50001 sec. Reason: requests rate is too high!
  SIP Server ID: 12292 18/02/2021 17:21:50
• SIP request (REGISTER) from 185.59.220.152 was rejected. Reason: Block WAN requests is ON. Message: REGISTER sip:81.63.154.161 SIP/2.0 Via: SIP/2.0/UDP 10.10.10.16:1908;branch=z9hG4bKf2dda8d5-24df-4dfa-af76-2c11821e7bae;rport=1908;received=185.59.220.152 Max-Forwards: 70 Contact: <sip:[email protected]:1908;rinstance=d3c7706aee8e2b40> To: "304"<sip:[email protected]> From: "304"<sip:[email protected]>;tag=tesshsqf Call-ID: culqierfvfbecredlkmdmiegmtbpopgmexlllxbbcbwpanngib CSeq: 2 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE Proxy-Authorization: Digest username="304",realm="3CXPhoneSystem",nonce="414d535c163f251c04:f4fd371ed6d3b85f68c152fb36472ff6",response="da31374622c23f17232c37d249071f7a",uri="sip:81.63.154.161",algorithm=MD5 Supported: 100rel User-Agent: PolycomVVX-VVX_401-UA5.4.1.18405 Content-Length: 0
  SIP Server ID: 12291 18/02/2021 17:21:48
• SIP request (REGISTER) from 95.111.253.64 was rejected. Reason: Block WAN requests is ON. Message: REGISTER sip:81.63.154.161 SIP/2.0 Via: SIP/2.0/UDP 10.10.10.16:8627;branch=z9hG4bK4c76d78c-4a2f-447b-b98d-b47a606b761f;rport=8627;received=95.111.253.64 Max-Forwards: 70 Contact: <sip:[email protected]:8627;rinstance=1a49f9b6e059474d> To: "108"<sip:[email protected]> From: "108"<sip:[email protected]>;tag=jbgxwpew Call-ID: obvjcmtcafoegkblijvhyxwylusntoearnnmqjjjafvybuplwy CSeq: 2 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE Proxy-Authorization: Digest username="108",realm="3CXPhoneSystem",nonce="414d535c163effa998:d9217ce72d3bb188c4c84adc3f5c79fb",response="48104c084bcd7c5905b6dea8a777ee0e",uri="sip:81.63.154.161",algorithm=MD5 Supported: 100rel User-Agent: PolycomVVX-VVX_401-UA5.4.1.18405 Content-Length: 0
  SIP Server ID: 12291 18/02/2021 14:42:01
• SIP request (REGISTER) from 193.29.106.22 was rejected. Reason: Block WAN requests is ON. Message: REGISTER sip:81.63.154.161 SIP/2.0 Via: SIP/2.0/UDP 10.10.10.13:8066;branch=z9hG4bK1debf75c-b2ad-4ec5-85e0-c215c7515022;rport=8066;received=193.29.106.22 Max-Forwards: 70 Contact: <sip:[email protected]:8066;rinstance=651ee6de05428440> To: "108"<sip:[email protected]> From: "108"<sip:[email protected]>;tag=wqimpckt Call-ID: ognpolfahryvwleywsajdluslhytmlturxiurrattgpeajsuue CSeq: 2 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE Proxy-Authorization: Digest username="108",realm="3CXPhoneSystem",nonce="414d535c163ef10f61:db9a0eb24c52c8b67112ca5bc7346d94",response="0b2dbddb20c6e1a56c8b779efb3b458f",uri="sip:81.63.154.161",algorithm=MD5 Supported: 100rel User-Agent: PolycomVVX-VVX_401-UA5.4.1.18405 Content-Length: 0
  SIP Server ID: 12291 18/02/2021 13:39:43
• SIP request (REGISTER) from 185.59.220.152 was rejected. Reason: Block WAN requests is ON. Message: REGISTER sip:81.63.154.161 SIP/2.0 Via: SIP/2.0/UDP 10.10.10.16:1655;branch=z9hG4bKbac4cfd4-b54f-4890-88af-63092faba8cc;rport=1655;received=185.59.220.152 Max-Forwards: 70 Contact: <sip:[email protected]:1655;rinstance=81c439c762131448> To: "900"<sip:[email protected]> From: "900"<sip:[email protected]>;tag=ryepaqhh Call-ID: hnvedhqftojshxnkymqduqfohvstgfjegitkctvncdqnvoksmd CSeq: 2 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE Proxy-Authorization: Digest username="900",realm="3CXPhoneSystem",nonce="414d535c163eefbd50:2547b2b7f48b556df05f747f53a9254b",response="29bcbdefc1de391d395583f4cf7f13aa",uri="sip:81.63.154.161",algorithm=MD5 Supported: 100rel User-Agent: PolycomVVX-VVX_401-UA5.4.1.18405 Content-Length: 0
  SIP Server ID: 12291 18/02/2021 13:34:06
• SIP request (REGISTER) from 193.29.106.22 was rejected. Reason: Block WAN requests is ON. Message: REGISTER sip:81.63.154.161 SIP/2.0 Via: SIP/2.0/UDP 10.10.10.13:8275;branch=z9hG4bKe4617a8a-b616-4a07-b537-e824784a66a7;rport=8275;received=193.29.106.22 Max-Forwards: 70 Contact: <sip:[email protected]:8275;rinstance=b080537c98393f41> To: "402"<sip:[email protected]> From: "402"<sip:[email protected]>;tag=jfjuebrh Call-ID: kfrxdayajxohdgkghafuvjnjgiiomrlrghjpwejgtpxqyjwnxg CSeq: 2 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE Proxy-Authorization: Digest username="402",realm="3CXPhoneSystem",nonce="414d535c163eea6063:7353d10bd44e28ff46abc7c85f7f1bf4",response="8264a603f1345aea9dd22f1e8110fc8d",uri="sip:81.63.154.161",algorithm=MD5 Supported: 100rel User-Agent: PolycomVVX-VVX_401-UA5.4.1.18405 Content-Length: 0
  SIP Server ID: 12291 18/02/2021 13:11:12
• SIP request (REGISTER) from 89.187.175.170 was rejected. Reason: Block WAN requests is ON. Message: REGISTER sip:81.63.154.161 SIP/2.0 Via: SIP/2.0/UDP 10.10.10.27:7287;branch=z9hG4bKd939abea-e829-46bc-b129-65cb35649d96;rport=7287;received=89.187.175.170 Max-Forwards: 70 Contact: <sip:[email protected]:7287;rinstance=750e411798ca774f> To: "304"<sip:[email protected]> From: "304"<sip:[email protected]>;tag=okjckwcv Call-ID: knikpmiwvhkwhfmmpakdinllohljlahximngqxvexefmskkphl CSeq: 2 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE Proxy-Authorization: Digest username="304",realm="3CXPhoneSystem",nonce="414d535c163ee4f051:4840c99a65d3111742d548fe9b0ea927",response="c7baba555175e74d58586bf1a1d41e76",uri="sip:81.63.154.161",algorithm=MD5 Supported: 100rel User-Agent: PolycomVVX-VVX_300-UA/4.1.6.4835 Content-Length: 0
  SIP Server ID: 12291 18/02/2021 12:48:00

 

[MarcelloL_3CX]

se, come forse ho inteso, hai il centralino non aggiornato, per cortesia per prima cosa aggiornalo al SP8 (è uscito ieri sera) e poi vediamo

 

[Fabio A]

Ciao ho aggiornato all'ultima versione il PBX i trunk sono tutti funzionanti con pallino verde ma sul pannello di controllo ho sempre un errore rosso sui trunk che mi dice che :

State utilizzando un trunk SIP non supportato che potrebbe causare errori.
Per un elenco dei trunk SIP supportati visitate questa pagina.

i trunk sono supportati da 3cx perchè nella lista, cosa posso fare?

 

[MarcelloL_3CX]

ma li hai registrati usando il template originale 3CX? e li hai configurati tu?

 

[Fabio A]

Sono dei trunk creati qualche anno fa da dei miei colleghi non so come li abbiano creati.

 

[MarcelloL_3CX]

allora il punto è lì:
probabilmente il template è personalizzato o hanno usato in origine il template generico e non stai usando quello originale, da quì l'errore.
A questo punto hai due strade:
1 - li elimini e li ri-crei usando il template 3CX (e allora l'errore scompare)
2 - visto che tutto funziona, li tieni così come sono e intervieni nel rifarli solo in caso compaiano problemi

 

[Fabio A]

ok grazie mille puoi darmi una dritta come ricreare template 3cx corretti.

buona giornata ci vediamo al corso

 

[MarcelloL_3CX]

registrare un trunk supportato è semplicissimo:
Pannello di controllo > SIP trunk > scegli il paese e il provider supportato dal Menu e inserisci le tue credenziali, ma in tutta sincerità nel tuo caso farei screenshot di tutti i parametri attualmente in uso e sentirei anche il supporto del provider in caso sui tuoi trunk ci siano specifiche particolari, prima di cancellare un trunk funzionante