[postmixfrance]

Bonsoir a tous,
suite au demenagement de ma société, je viens de reinstaller tout a neuf, Telephone, 3CX , PC (outlook 2010) ...
J'ai un probleme avec 3CX assistant, lorsque je souhaite composer a partir de outlook, cela fonctionne, mais la route choisi est forcement ma passerelle analogique (secour en cas de perte de connexion adsl). pour remedier a cela j'ai supprimer de ma config la passerelle analogique, et la impossible de composer ... faut il creer une regle d'appel special alors que les appels directs a partir de mon poste fonctionne tres bien ... quelqu'un a une idee ???
ma config:
-Serveur 3CX SP4 v9.14901 sur windows serveur 2007 32 bits
-Tel Liksys SPA 962 + 932
-Outlook 2010 sur PC windows 7 pro 64 bits
-FAI = Orange pro
-VOIP provider = Keyyo Pro

Help me , Merci.

[bluetel2]

Bonjour

sans log c'est difficile d'identifier votre problème. Pouvez vous poster le log du serveur lorsque l'appel ne passe pas.

[postmixfrance]

Bonjour, merci de me repondre.
Voici le log, mais je crois que cela viens de l'incompatibilité entre 3cx - SPA962+932 - Keyyo ...
A vous de voir:

09:12:49.393 [CM503008]: Call(185): Call is terminated
09:12:45.945 [MS210005] C:185.1:Answer provided. Connection(proxy mode):127.0.0.1:7046(7047)
09:12:45.945 [MS210001] C:185.2:Answer received. RTP connection[unsecure]: 192.168.0.103:16392(16393)
09:12:45.945 Remote SDP is set for legC:185.2
09:12:45.821 [MS210004] C:185.2:Offer provided. Connection(proxy mode): 192.168.0.2:7048(7049)
09:12:45.821 [MS210000] C:185.1:Offer received. RTP connection: 127.0.0.1:40720(40721)
09:12:45.821 Remote SDP is set for legC:185.1
09:12:45.384 [CM503016]: Call(185): Attempt to reach <sip:0679331802@127.0.0.1:5060> failed. Reason: Server Failure
09:12:45.384 [CM503003]: Call(185): Call to sip:0679331802@prx2.sip.phonesystems.net:5060 has failed; Cause: 500 Internal Error - Callee Customer not identified; from IP:83.136.162.72:5060
09:12:44.947 [CM503025]: Call(185): Calling VoIPline:0679331802@(Ln.10004@0387850745)@[Dev:sip:33387850745@prx2.sip.phonesystems.net:5060]
09:12:44.947 [MS210002] C:185.5:Offer provided. Connection(transcoding mode): 80.11.209.174:9042(9043)
09:12:44.947 [CM503003]: Call(185): Call to sip:0679331802@prx2.sip.phonesystems.net:5060 has failed; Cause: 500 Internal Error - Callee Customer not identified; from IP:83.136.162.72:5060
09:12:44.697 [CM503025]: Call(185): Calling VoIPline:0679331802@(Ln.10002@0387855526)@[Dev:sip:33387855526@prx2.sip.phonesystems.net:5060]
09:12:44.682 [MS210002] C:185.4:Offer provided. Connection(transcoding mode): 80.11.209.174:9040(9041)
09:12:44.682 [CM503003]: Call(185): Call to sip:0679331802@prx2.sip.phonesystems.net:5060 has failed; Cause: 500 Internal Error - Callee Customer not identified; from IP:83.136.162.72:5060
09:12:43.730 [CM503025]: Call(185): Calling VoIPline:0679331802@(Ln.10000@0980406980)@[Dev:sip:33980406980@prx2.sip.phonesystems.net:5060]
09:12:43.730 [MS210002] C:185.3:Offer provided. Connection(transcoding mode): 80.11.209.174:9038(9039)
09:12:43.668 [CM503004]: Call(185): Route 3: VoIPline:0679331802@(Ln.10004@0387850745)@[Dev:sip:33387850745@prx2.sip.phonesystems.net:5060]
09:12:43.668 [CM503004]: Call(185): Route 2: VoIPline:0679331802@(Ln.10002@0387855526)@[Dev:sip:33387855526@prx2.sip.phonesystems.net:5060]
09:12:43.668 [CM503004]: Call(185): Route 1: VoIPline:0679331802@(Ln.10000@0980406980)@[Dev:sip:33980406980@prx2.sip.phonesystems.net:5060]
09:12:43.668 [CM503010]: Making route(s) to <sip:0679331802@127.0.0.1:5060>
09:12:43.668 Refer: from="MakeCall"<sip:MakeCall@127.0.0.1:5060>;tag=a3421f54; to=<sip:*9103@127.0.0.1:5060;nofwd=1>;tag=2f452b73; RefTo=<sip:0679331802@127.0.0.1:5060>
09:12:43.496 [MS210003] C:185.1:Answer provided. Connection(transcoding mode[unsecure]):127.0.0.1:7046(7047)
09:12:43.496 [MS210001] C:185.2:Answer received. RTP connection[unsecure]: 192.168.0.103:16392(16393)
09:12:43.496 Remote SDP is set for legC:185.2
09:12:43.465 [MS210002] C:185.2:Offer provided. Connection(transcoding mode): 192.168.0.2:7048(7049)
09:12:43.465 [MS210000] C:185.1:Offer received. RTP connection: 127.0.0.1:40720(40721)
09:12:43.465 Remote SDP is set for legC:185.1
09:12:43.247 Session 2096422 of leg C:185.1 is confirmed
09:12:43.122 [CM503007]: Call(185): Device joined: sip:103@192.168.0.103:5060
09:12:43.106 [CM503007]: Call(185): Device joined: sip:MakeCall@127.0.0.1:40600;rinstance=5e2f635f8c548199
09:12:43.106 [MS210005] C:185.1:Answer provided. Connection(proxy mode):127.0.0.1:7046(7047)
09:12:43.106 [MS210001] C:185.2:Answer received. RTP connection[unsecure]: 192.168.0.103:16392(16393)
09:12:43.106 Remote SDP is set for legC:185.2
09:12:43.106 [CM505001]: Ext.103: Device info: Device Identified: [Man: Linksys;Mod: SPA series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA962-6.1.5(a)] PBX contact: [sip:103@192.168.0.2:5060]
09:12:43.106 [CM503002]: Call(185): Alerting sip:103@192.168.0.103:5060
09:12:42.857 [CM503025]: Call(185): Calling Ext:Int.103@[Dev:sip:103@192.168.0.103:5060]
09:12:42.857 [MS210004] C:185.2:Offer provided. Connection(proxy mode): 192.168.0.2:7048(7049)
09:12:42.825 [CM503004]: Call(185): Route 1: Ext:Int.103@[Dev:sip:103@192.168.0.103:5060]
09:12:42.825 [CM503010]: Making route(s) to <sip:*9103@127.0.0.1:5060;nofwd=1>
09:12:42.825 [MS210000] C:185.1:Offer received. RTP connection: 127.0.0.1:40720(40721)
09:12:42.825 Remote SDP is set for legC:185.1
09:12:42.825 [CM505001]: Ext.MakeCall: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX MakeCall Helper;Rev: 1] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX MakeCall helper] PBX contact: [sip:MakeCall@127.0.0.1:5060]
09:12:42.825 [CM503001]: Call(185): Incoming call from Ext.MakeCall to <sip:*9103@127.0.0.1:5060;nofwd=1>
09:12:42.825 [CM500002]: Info on incoming INVITE:
INVITE sip:*9103@127.0.0.1:5060;nofwd=1 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:40600;branch=z9hG4bK-d8754z-1e0dc944510c9f69-1---d8754z-;rport=40600
Max-Forwards: 70
Contact: <sip:MakeCall@127.0.0.1:40600;rinstance=5e2f635f8c548199>
To: <sip:*9103@127.0.0.1:5060;nofwd=1>
From: "MakeCall"<sip:MakeCall@127.0.0.1:5060>;tag=a3421f54
Call-ID: NWEyY2YzMjE3MTE5ZTQ1NmRhNzRlOTg0YmZjMWY3MzI.
CSeq: 2 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE
Proxy-Authorization: Digest username="MakeCall",realm="3CXPhoneSystem",nonce="414d535c0316667a63:e70b1a74ba8843d62e061f6f32e1f9f9",uri="sip:*9103@127.0.0.1:5060;nofwd=1",response="c814a00ece9b8e39513a6548019db166",algorithm=MD5
Supported: replaces
User-Agent: 3CX MakeCall helper
Content-Length: 0

09:12:42.545 [EC100007]: External application is connected: application:Serveur_3CX:0/3CXAssistantServer local:127.0.0.1:5482 remote:127.0.0.1:62066
09:12:37.802 Currently active calls [none]


D'apres un autre post cela viendrai de keyyo ???
Merci pour votre aide ...
J'ajoute quand meme que tout fonctionne lorsque je branche ma passerelle analogique(RTC) de secour, du coup je l'ai supprimer de ma config 3CX pour les tests ..., mais je ne souhaite pas passer tous les appels en analogique ...

ma config:
-Serveur 3CX SP4 v9.14901 sur windows serveur 2007 32 bits
-Tel Liksys SPA 962 + 932
-Outlook 2010 sur PC windows 7 pro 64 bits
-FAI = Orange pro
-VOIP provider = Keyyo Pro x 3

Cordialement,

Xavier PMF

[cdumaine]

Bonjour

A la lecture du log, oui problème avec KEYYO.
Idem post clic to call.
C'est vrai que ça devient pénible .... !

Nous avons put contourner le problème avec des postes Snom qui gère les appels via une url et ce n'est donc plus le "makecall" qui initie l'appel.

cdt

[mensa]

Bonjour,

Pour information, je pense avoir trouvé le problème.
Quelqu'un saurait-il s'il est possible de virer le Referred-By dans le PBX 3CX ou changer le From du MakeCall?

Voir ce post pour l'explication : pb-compatibilite-click-to-call-ou-3cx-assistant-avec-keyyo-12315.html

Merci pour votre aide,
--
Mensa