Problème avec GrandStream GXW-4024 V0.2C [résolu]

Général - Système Téléphonique 3CX, VoIP & support SIP (menée par la communauté) d'utilisateurs à utilisateurs - Les réponses proviennent de la communauté. 3CX NE FOURNIT PAS de support technique au travers de ce forum.

Moderators: kevin, 3CX staff

Problème avec GrandStream GXW-4024 V0.2C [résolu]

Postby Spider » Tue Jan 12, 2010 11:32 am

Bonjour,

Tout dabord merci pour ce fabuleux logiciel complet et performant, c'est une vrai révolution.

A présent, voila le problème que je rencontre :

J'ai acheté la passerelle VoIP GrandStream GXW-4024 V0.2C qui comporte 24 ports. J'y ai connecté dessus 19 lignes RTC dont 2 étant des lignes entrantes/sortantes de France Telecom, les 17 lignes restantes sont internes.
J'ai suivi à la lettre le manuel de configuration disponible ici : http://www.3cx.com/voip-gateways/Grands ... W4024.html

My Software Version : Program-- 1.0.1.41 Bootloader-- 1.0.0.9 Core-- 1.0.0.37 Base-- 1.0.0.87

La version traitée par le manuel est sensiblement identique niveau interface par rapport à la mienne, seul l'écran Advenced Settings n'a rien à voir, je ne peux pas configurer de mode Bridge par exemple.
Malgré cela, j'ai réussi à configurer à priori correctement la passerelle puisque, après avoir créé, comme demandé, mes extensions dans le logiciel 3CX, puis configuré celles-ci dans la passerelle, elles arrivent à s'enregistrer et fonctionne parfaitement pour les appels en interne.

extensions.jpg
Liste des extensions créées
extensions.jpg (133.49 KiB) Viewed 933 times

grandstream.jpg
Page d'informations de la passerelle
grandstream.jpg (103.47 KiB) Viewed 932 times


A présent je souhaite pouvoir configurer mes extensions 63 et 64 qui correspondent à mes 2 lignes France Telecom. J'ai donc tenté de créer des règles entrantes mais on me demande d'ajouter une passerelle.
Je me rend donc dans la section Périphériques RTC et je fais "ajouter une passerelle".
J'entre le nom "GrandStream", je sélectionne la marque GrandStream et le modèle GXW-4024.

ajout_passerelle_etape1.jpg
Etape 1 de l'ajout d'une passerelle
ajout_passerelle_etape1.jpg (94.99 KiB) Viewed 933 times


Ensuite j'entre l'adresse MAC de l'appareil : 00:0B:82:22:70:8C

ajout_passerelle_etape2.jpg
Etape 2 de l'ajout d'une passerelle
ajout_passerelle_etape2.jpg (82.14 KiB) Viewed 933 times


Enfin je saisi l'ip de la passerelle : 192.168.0.100

ajout_passerelle_etape3.jpg
Etape 3 de l'ajout d'une passerelle
ajout_passerelle_etape3.jpg (90.93 KiB) Viewed 933 times


Puis j'obtient l'écran suivant :

ajout_passerelle_etape4.jpg
Etape 4 de l'ajout d'une passerelle
ajout_passerelle_etape4.jpg (141.86 KiB) Viewed 932 times


Tout est configuré automatiquement, je n'ai rien touché, je fais donc suivant et obtient :

ajout_passerelle_etape5.jpg
Etape 5 de l'ajout d'une passerelle
ajout_passerelle_etape5.jpg (100.63 KiB) Viewed 932 times


A priori tout s'est bien passé, malheureusement lorsque je réaffiche la liste des Périphériques RTC celle-ci est vide...

peripheriques_rtc.jpg
Liste des phériphériques RTC après ajout de la passerelle GrandStream
peripheriques_rtc.jpg (84.08 KiB) Viewed 931 times


Je ne peux donc pas créer de règle entrante pour configurer mes lignes France Telecom...

J'ai vérifié dans la section Mise à jour du système 3CX que le modèle de configuration soit bien à jour, j'ai tenté une réinstallation du logiciel 3CX, j'ai cherché sur forum et vos manuels des solutions, rien à faire, je ne parviens pas à ajouter cette passerelle GrandStream GXW-4024 que j'ai acheté spécialement car elle était soit disant compatible avec votre système... (600€ tout de même).

Voila, en espérant que vous allez pouvoir m'aider et trouver une solution rapidement, car si jamais ça ne marche pas je prèfère retourner la passerelle sous les 7 jours laissé par la loi française plutôt que de garder un appareil aussi cher qui ne me sert pas.

Merci d'avance.

P.S: comme il est demandé sur l'annonce du forum, je joinds ci-après les logs de 3CX :

Code: Select all
11:19:11.627  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
10:59:10.813  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
10:39:10.162  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
10:19:09.345  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
09:59:08.669  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
09:45:10.059  [CM504001]: Ext.64: new contact is registered. Contact(s): [sip:64@192.168.0.100:5106/64]
09:45:08.608  [CM504001]: Ext.63: new contact is registered. Contact(s): [sip:63@192.168.0.100:5104/63]
09:45:07.158  [CM504001]: Ext.62: new contact is registered. Contact(s): [sip:62@192.168.0.100:5102/62]
09:45:05.707  [CM504001]: Ext.61: new contact is registered. Contact(s): [sip:61@192.168.0.100:5100/61]
09:45:04.258  [CM504001]: Ext.60: new contact is registered. Contact(s): [sip:60@192.168.0.100:5098/60]
09:45:02.807  [CM504001]: Ext.59: new contact is registered. Contact(s): [sip:59@192.168.0.100:5096/59]
09:45:01.359  [CM504001]: Ext.58: new contact is registered. Contact(s): [sip:58@192.168.0.100:5094/58]
09:44:59.909  [CM504001]: Ext.57: new contact is registered. Contact(s): [sip:57@192.168.0.100:5092/57]
09:44:58.461  [CM504001]: Ext.56: new contact is registered. Contact(s): [sip:56@192.168.0.100:5090/56]
09:44:57.009  [CM504001]: Ext.55: new contact is registered. Contact(s): [sip:55@192.168.0.100:5088/55]
09:44:55.559  [CM504001]: Ext.54: new contact is registered. Contact(s): [sip:54@192.168.0.100:5086/54]
09:44:54.109  [CM504001]: Ext.53: new contact is registered. Contact(s): [sip:53@192.168.0.100:5084/53]
09:44:52.660  [CM504001]: Ext.52: new contact is registered. Contact(s): [sip:52@192.168.0.100:5082/52]
09:44:51.208  [CM504001]: Ext.51: new contact is registered. Contact(s): [sip:51@192.168.0.100:5080/51]
09:44:49.757  [CM504001]: Ext.50: new contact is registered. Contact(s): [sip:50@192.168.0.100:5078/50]
09:44:48.309  [CM504001]: Ext.49: new contact is registered. Contact(s): [sip:49@192.168.0.100:5076/49]
09:44:46.861  [CM504001]: Ext.48: new contact is registered. Contact(s): [sip:48@192.168.0.100:5074/48]
09:44:45.407  [CM504001]: Ext.47: new contact is registered. Contact(s): [sip:47@192.168.0.100:5072/47]
09:44:43.962  [CM504001]: Ext.46: new contact is registered. Contact(s): [sip:46@192.168.0.100:5070/46]
09:44:42.577  [CM504001]: Ext.45: new contact is registered. Contact(s): [sip:45@192.168.0.100:5068/45]
09:44:41.129  [CM504001]: Ext.44: new contact is registered. Contact(s): [sip:44@192.168.0.100:5066/44]
09:44:39.679  [CM504001]: Ext.43: new contact is registered. Contact(s): [sip:43@192.168.0.100:5064/43]
09:44:38.229  [CM504001]: Ext.42: new contact is registered. Contact(s): [sip:42@192.168.0.100:5062/42]
09:44:36.779  [CM504001]: Ext.41: new contact is registered. Contact(s): [sip:41@192.168.0.100:5060/41]
09:39:07.989  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
09:20:43.725  [CM503008]: Call(7): Call is terminated
09:20:43.707  [CM503020]: Normal call termination. Reason: Not available
09:20:43.707  [CM503016]: Call(7): Attempt to reach <sip:0820902500@192.168.0.5> failed. Reason: Not Registered
09:20:43.706  [CM503016]: Call(7): Attempt to reach <sip:0820902500@192.168.0.5> failed. Reason: Not Registered
09:20:43.706  [CM503017]: Call(7): Target is not registered: Out.0820902500{rule=Règle pour GrandStream}
09:20:43.696  [CM503010]: Making route(s) to <sip:0820902500@192.168.0.5>
09:20:43.692  [CM505001]: Ext.42: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXW-4024  V0.2C 1.0.1.41] PBX contact: [sip:42@192.168.0.5:5060]
09:20:43.680  [CM503001]: Call(7): Incoming call from Ext.42 to <sip:0820902500@192.168.0.5>
09:19:07.315  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
08:59:06.435  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
08:39:05.622  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
08:19:05.220  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
07:59:04.326  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
07:39:03.471  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
07:19:02.716  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
06:59:02.040  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
06:39:01.272  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
06:19:00.583  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
05:59:00.115  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
05:38:59.648  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
05:18:58.857  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
04:58:58.047  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
04:38:57.369  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
04:18:56.579  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
03:58:55.733  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
03:38:54.980  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
03:18:54.178  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
02:58:53.493  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
02:38:52.837  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
02:18:52.132  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
01:58:51.751  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
01:38:50.928  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
01:18:50.077  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
00:58:49.397  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
00:38:49.053  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
00:18:48.225  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
23:58:47.397  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
23:38:47.178  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
23:18:46.834  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
22:58:46.443  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
22:38:45.974  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
22:18:44.382  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
21:58:44.194  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
21:38:43.974  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
21:18:43.084  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
20:58:42.335  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
20:38:41.990  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
20:18:41.802  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.5:5060
20:17:11.043  [CM503008]: Call(6): Call is terminated
20:16:36.099  [CM503007]: Call(6): Device joined: sip:41@192.168.0.100:5060
20:16:36.084  [CM503007]: Call(6): Device joined: sip:42@192.168.0.100:5062
20:16:19.548  [CM505001]: Ext.41: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXW-4024  V0.2C 1.0.1.41] PBX contact: [sip:41@192.168.0.5:5060]
20:16:19.548  [CM503002]: Call(6): Alerting sip:41@192.168.0.100:5060
20:16:19.470  [CM503025]: Call(6): Calling Ext:Ext.41@[Dev:sip:41@192.168.0.100:5060]
20:16:19.423  [CM503004]: Call(6): Route 1: Ext:Ext.41@[Dev:sip:41@192.168.0.100:5060]
20:16:19.423  [CM503010]: Making route(s) to <sip:41@192.168.0.5>
20:16:19.407  [CM505001]: Ext.42: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXW-4024  V0.2C 1.0.1.41] PBX contact: [sip:42@192.168.0.5:5060]
20:16:19.407  [CM503001]: Call(6): Incoming call from Ext.42 to <sip:41@192.168.0.5>
20:08:22.790  [CM503008]: Call(5): Call is terminated
20:08:12.707  [CM505001]: Ext.57: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXW-4024  V0.2C 1.0.1.41] PBX contact: [sip:57@192.168.0.5:5060]
20:08:12.706  [CM503002]: Call(5): Alerting sip:57@192.168.0.100:5092
20:08:12.626  [CM503025]: Call(5): Calling Ext:Ext.57@[Dev:sip:57@192.168.0.100:5092]
20:08:12.585  [CM503004]: Call(5): Route 1: Ext:Ext.57@[Dev:sip:57@192.168.0.100:5092]
20:08:12.584  [CM503010]: Making route(s) to <sip:57@192.168.0.5>
20:08:12.577  [CM505001]: Ext.42: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXW-4024  V0.2C 1.0.1.41] PBX contact: [sip:42@192.168.0.5:5060]
20:08:12.571  [CM503001]: Call(5): Incoming call from Ext.42 to <sip:57@192.168.0.5>
20:07:59.613  [CM503008]: Call(4): Call is terminated
20:07:49.487  [CM505001]: Ext.46: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXW-4024  V0.2C 1.0.1.41] PBX contact: [sip:46@192.168.0.5:5060]
20:07:49.487  [CM503002]: Call(4): Alerting sip:46@192.168.0.100:5070
Last edited by Spider on Wed Jan 13, 2010 5:41 pm, edited 1 time in total.
Spider
New User
 
Posts: 3
Joined: Tue Jan 12, 2010 10:40 am

Re: Problème avec GrandStream GXW-4024 V0.2C

Postby gadson » Tue Jan 12, 2010 11:23 pm

Bonjour, je vous réponds suite à votre problème avec le GXW 4024.

Déjà juste vous dire qu'on ne branche pas de ligne RTC (France Telecom) sur cette passerelle, c'est plutôt le 4104 ou le 4108 pour ajouter des lignes RTC France télécom.
Il faut dejà ajouter la passerelle dans l'IPBX avec de le configurer.
N'hésiter pas à me contacter sur contact@gadsonconcept.com afin que je puisse vous apporter une assistance à Distance.
gadson
New User
 
Posts: 3
Joined: Sun Nov 29, 2009 2:18 pm

Re: Problème avec GrandStream GXW-4024 V0.2C [résolu]

Postby Spider » Wed Jan 13, 2010 5:40 pm

Merci pour votre réponse.

Après plusieurs recherches et à l'aide du support technique de Watsoft, il s'avère que ma passerelle n'a pas de port FXO nécessaire au branchement de mes lignes France Telecom.
Je dois donc me procurrer une passerelle possédant ce type de ports.
Spider
New User
 
Posts: 3
Joined: Tue Jan 12, 2010 10:40 am


Return to Français

Who is online

Users browsing this forum: No registered users and 0 guests