jocelynaziere Posted May 9, 2014 Report Share Posted May 9, 2014 Please se the 2 attached files .txt -> CSTA decode seqience .pcapng -> wirewhark trace from application to pbx The AnwsercallResponse is empty and the device did not take the call. Regards. SnomOne153_answercall .txt SnomOne153_answercall.zip Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted May 9, 2014 Report Share Posted May 9, 2014 This works only if the attached phone supports the "talk" event in a NOTIFY sent to the phone. What phone are you using? Quote Link to comment Share on other sites More sharing options...
jocelynaziere Posted May 12, 2014 Author Report Share Posted May 12, 2014 We use 870, 760 and 720. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted May 15, 2014 Report Share Posted May 15, 2014 Hmm, there this should work. The logs also suggest that the PBX received the request to answer the call successfully. Does the phone get the Event: talk? Maybe a stinky firewall in between the PBX and the phone? A SIP trace from the phone will show this. Quote Link to comment Share on other sites More sharing options...
jocelynaziere Posted May 23, 2014 Author Report Share Posted May 23, 2014 Hello,Please find the SIP trace of the device(snom 720 version 8.7.3.25)(snom 760 version 8.7.5.8)The pbx log file : PBX_Trace.txtThe wireshark trace : PBX_WireShark_Trace.ZipThe CSTA trace from our application: CSTATrace.txtTalk event is supported but this event seems to be not received.All device are on the same lan as the PBX.In the wireshark trace you can see the AnswerCall CSTA request, but in the PBX trace file , nothing is found.How can we process on this point ?We can do a remote session if it is more easy for you to see what happens on the PBX ?RegardsJocelyn. Sip_Trace_Answer_Call_720.txt Sip_Trace_Answer_Call_760.txt CSTAPduTraces.txt PBX_Trace.txt PBX_WireShark_Trace.zip Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted May 29, 2014 Report Share Posted May 29, 2014 At least one problem is that the deviceId is sometimes in the "user@domain" form, and in other cases just in the form "user". What CSTA tool are you using again? In theory it would be possible that the PBX looks up the domain by itself because it has the CSTA session context anyway. But before we start looking into what this would mean it would be good to know if we can instead fix it on the CSTA client side. Quote Link to comment Share on other sites More sharing options...
jocelynaziere Posted June 12, 2014 Author Report Share Posted June 12, 2014 Hello, Algoria ( http://www.algoria.fr ) is an editor in UCC software , and we provide solution for many IPBX constructor or device constructor as Snom One pr Snom Device , but also Mite / Aastra PBX /Alcatel / Siemens ... And check the CSTA traces and i not sure that your answer is the solution because: To start monitoring you must use device numer + domain context , il not the monitor return an error , Right ? When the device received an incomming call the connection ID done by the PBX is a dialingNumer with no context ) and in the alerting device the dialing number as a context , so this not our application who set this information When we send an answer call to the PBX we used the exact connexion séquence received in the delivered event , so in my point of view this right and it should work. You will find in the attached file the CSTA trace with : StartMonitor / delivered event (incomming call) and / answer call Let me know the point of view Jocelyn. SnomOne.txt Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.