yes it is traced on voiceguide server 2012 10.1.1.5
it is 10.1.1.5 is sending RTP to 184.108.40.206 it means this public ip needs to allow ports on firewall right (220.127.116.11) right ?
yes it did wire shark on 18.104.22.168 machine it is not showing any thing as i already mentioned in my previous post (empty).
so firewall is prevent RTP from 22.214.171.124 reaching 10.1.1.5
coming to point of initial testing 10.1.1.5 is located @ datacenter which is completely on different location uk and mine 126.96.36.199 is from india so i cannot test them on same network.
10.1.1.5 is dedicated box it is not VM
coming to my internal network 188.8.131.52 before i install this on server i was running two machines on my personal lan one is windows 10 machine and other one is virtual VM this two are working perfectly without any issue voice commuction and sip call flow is working fine becuz they are behind the firewall which is location on my internal lan.
give me some time i will come back need to allow ports on firewall 49100 and above (to say 50000) which is pending @ my end.
you also mentioned to test the MicroSIP softphone right i did this on my pcs where IVR was running perfectly but no voice can be listen this is behind the firewall
which is like 192.168.2.4 (PC) from to voiceguide server 192.168.2.63 (VM).