Hi Alice, The missing step in your setup (as pointed out by Roger) seems to be this: when the phone sends a message to the Host, it calls on a DNS resolver, which should resolve the hostname to the IP address of your deployment. You may be using AWS Route 53 or your own DNS resolver, and it is currently missing this entry to map hostname to IP.
The server/host name, as you are using an All-in-One node, should be <aio-identity>, which is “cw-aio.com” for our aio image. When you are not using All-in-One node, the server name would be <domain_name>, which is “example.com” as you put here. As for the IP address of the aio-identity, I believe you are using “localhost” to find it out. And you have correctly put that IP as the outbound proxy and used port 8060. In summary, the missing entry should map “cw-aio.com” to 192.168.104.8. Thanks, Ying From: Clearwater [mailto:[email protected]] On Behalf Of ??? Sent: 23 November 2017 08:42 To: [email protected] Subject: Re: [Project Clearwater] Making calls: cannot get two-way media Hi Ying, Roger, Thanks for your replying. I've double checked all the settings, and I attached two snapshots of my account settings. For Host part I put "example.com<http://example.com>" and Outbound Proxy part I put "192.168.104.8:8060<http://192.168.104.8:8060>" where 192.168.104.8 is the ip address of my computer(Windows). Roger, I'm not quite understand your meaning of "able to resolve cw-aio via DNS". Both of the phones can get and receive SIP message like INVITE, TRYING, RINGING......e.t.c. I thought this means they can already resolve cw-aio, doesn't it? As for my network architecture, my cw-aio in VirtualBox is using NAT. I'm still failing on making calls through two clients. Do you have any idea what should I do? Many thanks for your time and replying. Best regard, Alice 2017-11-11 2:49 GMT+08:00 Roger Case <[email protected]<mailto:[email protected]>>: Hi Alice, Ying, This exact issue I had in the beginning of experimenting with the all-in-one was caused by the client (in my case Cisco 7960 phones, and PacketCable eMTAs) needing to be able to resolve cw-aio via DNS. Without this they could not respond with the required ACK. Also, Alice, your RTP connections may be interesting. I’m not sure we are clear on your network architecture. Your client RTP ports seem to be in 10.X.X.X address space. Best of luck! Roger From: Clearwater [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Ying Huang Sent: Friday, November 10, 2017 9:17 AM To: [email protected]<mailto:[email protected]> Subject: Re: [Project Clearwater] Making calls: cannot get two-way media [External Email] Hi Alice, Looking through your wireshark trace, INVITE and 200OK are going through fine, but it’s missing an ACK from callee. Looking into debug log, there isn’t any ERROR, but no ACK is being routed through. So I believe the clearwater deployment is working fine, but the client isn’t configured in the right way and fails to send the ACK. Here is some instruction on setting up the client, it will be good if you double check all the fields. https://clearwater.readthedocs.io/en/stable/Making_your_first_call.html If any question feel free to come back to this thread. Thanks, Ying From: Clearwater [mailto:[email protected]] On Behalf Of ??? Sent: 06 November 2017 08:05 To: [email protected]<mailto:[email protected]> Subject: Re: [Project Clearwater] Making calls: cannot get two-way media Hi Adam, Thanks for your replying. I'm running the wireshark trace on Windows 7. I've attached the bono and sprout debug logs. Also the wireshark trace for this time and the txt file is some record for this experiment, like IP address for my host and clients. Best regards, Alice 2017-11-03 18:51 GMT+08:00 Adam Lindley <[email protected]<mailto:[email protected]>>: Hey Alice, I’m not sure what’s causing the issue from just the wireshark trace, though I think the record-route header `<sip:2FLuF4m0qB@cw-aio:5060;transport=TCP;lr>` looks unusual. Can you enable debug logging, and then get the bono and sprout debug logs from the node when you try to run the call? Also, can you let us know where you are running the wireshark trace? If you need some guidance on enabling debug logs, check out https://clearwater.readthedocs.io/en/stable/Troubleshooting_and_Recovery.html Cheers, Adam From: Clearwater [mailto:[email protected]<mailto:[email protected]>] On Behalf Of ??? Sent: 31 October 2017 04:05 To: [email protected]<mailto:[email protected]> Subject: [Project Clearwater] Making calls: cannot get two-way media Hi, I'm using AIO on VirtualBox. For clients, I'm using Zoiper on Android phones. Both clients can successfully sending out REGISTER, INVITE, 100 TRYING, 180 RINGING...... When Caller makes a call to Callee, Callee can successfully send out a 200 OK to Caller. But Caller didn't send back a 200 OK to Callee, and that makes Callee keep showing the interface of incoming call. The Wireshark trace and the snapshot for sip packets is attached. ********************************************************** Caller IP: 192.168.208.202 Callee IP: 192.168.208.48 PC IP: 192.168.104.121 ********************************************************** There is a similar problem in archive April 2016, but the answer there says that it is the problem in client part. If it is Zoiper's problem, may I ask what kind of softphone apps do you use? Cause I look through all the Clearwater archives, but it seems every one can use Zoiper successfully. As for X-Lite, Bria, Blink and Jitsi, some of them can not set up your own SIP account, and some even don't exist now. Best regards, Alice _______________________________________________ Clearwater mailing list [email protected]<mailto:[email protected]> http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org _______________________________________________ Clearwater mailing list [email protected]<mailto:[email protected]> http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
