Toggle sidebar Toggle sidebar

Problemi di registrazione Trunk SIP

A

anonymous

Well-Known Member
Registrato
14 Gennaio 2008
Messaggi
19.170
Ciao a tutti e colgo l'occasione per augurare Buon Anno,
stiamo provando una versione (11) Demo del prodotto con l'attivazione della licenza avuta dopo il dowload, abbiamo due grossi problemi, il primo che non riusciamo a far partire le trunk voip (eutelia e exsorsa) nello stato Porte/tronvhi si vede il pallino verde registrato na non attiva, escluderei un problemi di firewall in quanto dalla diagnostica del sistema le varie nat sono tutte regolari, latro problema sui interni Yealink T26, se cade il collegamento ethernet per qualsiasi motivo si perde la registrazione e bisogna fare un reboot al telefono !!
Stiamo provando questo prodotto per ipotizzarlo di sostiture a dei vecchi PBX WILDIX, s qualcuno può fornirci supporto (anche a pagamento) contattatemi pure ai recapiti sotto.

Allego log del centralino.


WITEL S.r.l.
Maurizio Di Cintio
346.3382292
[email protected]

02-gen-2013 03:17:53.288 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
02-gen-2013 03:08:35.292 [CM504001]: Endpoint Extn:100: new contact is registered. Contact(s): [sip:[email protected]:5062 / 100]
02-gen-2013 02:57:53.236 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
02-gen-2013 02:37:53.140 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
02-gen-2013 02:17:53.029 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
02-gen-2013 01:57:52.990 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
02-gen-2013 01:37:52.866 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
02-gen-2013 01:17:52.820 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
02-gen-2013 01:14:42.294 PBX has dropped a message with 'User-Agent: friendly-scanner' from IP 195.49.62.5 because it is on blocked UAs list
02-gen-2013 00:57:52.722 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
02-gen-2013 00:37:52.634 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
02-gen-2013 00:17:52.551 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
01-gen-2013 23:57:52.514 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
01-gen-2013 23:37:52.387 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
01-gen-2013 23:17:52.290 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
01-gen-2013 22:57:52.172 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
01-gen-2013 22:37:52.106 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
01-gen-2013 22:17:52.052 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
01-gen-2013 21:57:51.954 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
01-gen-2013 21:37:51.899 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
01-gen-2013 21:17:51.831 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
01-gen-2013 20:57:51.777 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
01-gen-2013 20:37:51.723 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
01-gen-2013 20:17:51.672 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
01-gen-2013 20:05:57.660 PBX has dropped a message with 'User-Agent: friendly-scanner' from IP 195.81.177.21 because it is on blocked UAs list
01-gen-2013 19:57:51.634 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
01-gen-2013 19:55:10.360 PBX has dropped a message with 'User-Agent: friendly-scanner' from IP 199.188.101.212 because it is on blocked UAs list
01-gen-2013 19:37:51.509 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
01-gen-2013 19:34:19.754 PBX has dropped a message with 'User-Agent: friendly-scanner' from IP 199.19.105.224 because it is on blocked UAs list
01-gen-2013 19:34:17.618 PBX has dropped a message with 'User-Agent: friendly-scanner' from IP 199.19.105.224 because it is on blocked UAs list
01-gen-2013 19:17:51.414 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
01-gen-2013 18:57:51.347 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
01-gen-2013 18:37:51.196 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
01-gen-2013 18:17:51.101 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
01-gen-2013 17:57:50.969 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
01-gen-2013 17:37:50.864 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
01-gen-2013 17:23:48.755 PBX has dropped a message with 'User-Agent: friendly-scanner' from IP 203.126.210.51 because it is on blocked UAs list
01-gen-2013 17:17:50.766 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
01-gen-2013 17:13:35.015 PBX has dropped a message with 'User-Agent: friendly-scanner' from IP 128.36.43.241 because it is on blocked UAs list
01-gen-2013 16:57:50.634 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
01-gen-2013 16:38:21.122 [CM504001]: Endpoint Ivr:RecordFile: new contact is registered. Contact(s): [sip:[email protected]:40600 / RecordFile]
01-gen-2013 16:38:21.120 [CM504001]: Endpoint Ivr:PlayFile: new contact is registered. Contact(s): [sip:P[email protected]:40600 / PlayFile]
01-gen-2013 16:38:21.118 [CM504001]: Endpoint Ivr:MakeCall: new contact is registered. Contact(s): [sip:[email protected]:40600 / MakeCall]
01-gen-2013 16:38:21.116 [CM504001]: Endpoint Ivr:IVRForward: new contact is registered. Contact(s): [sip:[email protected]:40600 / IVRForward]
01-gen-2013 16:38:21.114 [CM504001]: Endpoint Ivr:EndCall: new contact is registered. Contact(s): [sip:[email protected]:40600 / EndCall]
01-gen-2013 16:38:21.097 [CM504001]: Endpoint Ivr:802: new contact is registered. Contact(s): [sip:[email protected]:40600 / 802]
01-gen-2013 16:38:21.057 [CM504001]: Endpoint Ivr:801: new contact is registered. Contact(s): [sip:[email protected]:40600 / 801]
01-gen-2013 16:38:21.024 [CM504001]: Endpoint Ivr:770: new contact is registered. Contact(s): [sip:[email protected]:40600 / 770]
01-gen-2013 16:38:20.964 [CM504001]: Endpoint Ivr:HOL: new contact is registered. Contact(s): [sip:[email protected]:40600 / HOL]
01-gen-2013 16:38:20.940 [CM504001]: Endpoint VMail:999: new contact is registered. Contact(s): [sip:[email protected]:40600 / 999]
01-gen-2013 16:38:16.516 [CM504001]: Endpoint ParkOrb:SP9: new contact is registered. Contact(s): [sip:[email protected]:40000 / SP9]
01-gen-2013 16:38:16.513 [CM504001]: Endpoint ParkOrb:SP8: new contact is registered. Contact(s): [sip:[email protected]:40000 / SP8]
01-gen-2013 16:38:16.474 [CM504001]: Endpoint ParkOrb:SP7: new contact is registered. Contact(s): [sip:[email protected]:40000 / SP7]
01-gen-2013 16:38:16.392 [CM504001]: Endpoint ParkOrb:SP6: new contact is registered. Contact(s): [sip:[email protected]:40000 / SP6]
01-gen-2013 16:38:16.309 [CM504001]: Endpoint ParkOrb:SP5: new contact is registered. Contact(s): [sip:[email protected]:40000 / SP5]
01-gen-2013 16:38:16.300 [CM504001]: Endpoint ParkOrb:SP4: new contact is registered. Contact(s): [sip:[email protected]:40000 / SP4]
01-gen-2013 16:38:16.246 [CM504001]: Endpoint ParkOrb:SP3: new contact is registered. Contact(s): [sip:[email protected]:40000 / SP3]
01-gen-2013 16:38:16.242 [CM504001]: Endpoint ParkOrb:SP2: new contact is registered. Contact(s): [sip:[email protected]:40000 / SP2]
01-gen-2013 16:38:16.062 [CM504001]: Endpoint ParkOrb:SP1: new contact is registered. Contact(s): [sip:[email protected]:40000 / SP1]
01-gen-2013 16:38:16.047 [CM504001]: Endpoint ParkOrb:SP0: new contact is registered. Contact(s): [sip:[email protected]:40000 / SP0]
01-gen-2013 16:38:16.010 [CM504001]: Endpoint ParkOrb:*1: new contact is registered. Contact(s): [sip:*[email protected]:40000 / *1]
01-gen-2013 16:38:15.892 [CM504001]: Endpoint ParkOrb:*0: new contact is registered. Contact(s): [sip:*[email protected]:40000 / *0]
01-gen-2013 16:38:15.883 [CM504001]: Endpoint ParkOrb:*777: new contact is registered. Contact(s): [sip:*[email protected]:40000 / *777]
01-gen-2013 16:38:11.547 [CM504001]: Endpoint Ivr:DialCode: new contact is registered. Contact(s): [sip:D[email protected]:5488 / DialCode]
01-gen-2013 16:38:06.759 [CM504001]: Endpoint Conf:704: new contact is registered. Contact(s): [sip:[email protected]:40300 / 704]
01-gen-2013 16:38:06.679 [CM504001]: Endpoint Conf:703: new contact is registered. Contact(s): [sip:[email protected]:40300 / 703]
01-gen-2013 16:38:06.667 [CM504001]: Endpoint Conf:702: new contact is registered. Contact(s): [sip:[email protected]:40300 / 702]
01-gen-2013 16:38:06.626 [CM504001]: Endpoint Conf:701: new contact is registered. Contact(s): [sip:[email protected]:40300 / 701]
01-gen-2013 16:38:06.586 [CM504001]: Endpoint Conf:700: new contact is registered. Contact(s): [sip:[email protected]:40300 / 700]
01-gen-2013 16:38:03.973 [EC200002]: Media server is connected:
application:user-PC:0/MediaServer
local:127.0.0.1:5482
remote:127.0.0.1:49174
01-gen-2013 16:38:01.074 [CM504008]: Fax Service: Fax.888 registered as sip:[email protected]:5060 with contact sip:[email protected]:5100;user=phone
01-gen-2013 16:37:57.807 IP(s) added:[10.10.0.8]
01-gen-2013 16:37:50.634 [CM506002]: Resolved SIP external IP:port (89.97.149.98:5060) on Transport 10.10.0.8:5060
01-gen-2013 16:37:50.500 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 199.192.206.228:3478 over Transport 10.10.0.8:5060
01-gen-2013 16:37:48.560 [CM501006]: Default Local IP address: [10.10.0.8]
01-gen-2013 16:37:48.555 [CM501002]: Version: 11.0.27565.0
01-gen-2013 16:37:48.555 [CM501001]: Start 3CX PhoneSystem Call Manager
01-gen-2013 16:37:48.555 [CM501009]: License Info: Loaded Succeeded
01-gen-2013 16:37:47.841 [CM501007]: *** Started Calls Controller thread ***
 
"Non attivo" significa semplicemente che non vi è conversazione in corso.
Per quanto concerne gli Yealink è normale che i telefoni ci mettano del tempo per rieffettuare la registrazione se viene a mancare il collegamento Ethernet. Il tempo necessario al ripristino è dato dal parametro di rinnovo della registrazione SIP. E' possibile modificarlo agendo sul template di provisioning del telefono in oggetto. Gli Yealink andrebbero configurati in autoprovisioning utilizzando la revisione firmware certificata da 3CX.
Per quanto concerne Router e Firewall indico di seguito un link ad un articolo appositamente pubblicato per permettere di comprendere i requisiti e le indidcazioni di massima per un PBC 3CX:
http://shop.eurylink.com/blog/48-news3cx/140-quale-routero-firewall-scegliere-per-3cx-phone-system-.html
E' importante notare che il semplice fatto di superare il test del firewall è una condizione necessaria ma non sufficiente affinché poi tutto funzioni correttamente.
 
scusa ma come ti trovi con exorsa ??? e sopratutto con eutelia ?
 
You must log in or register to reply here.

Inizia con 3CX – Admin

Forum statistics

Discussioni
44.659
Messaggi
233.415
Membri
78.445
Ultimo Iscritto
NordNico
3CX Logo Footer Copyright © Sitemap Privacy
Alto Basso