Ok so it turns out I did not put the provisioning files in there, i went ahead and did this. I restarted the phone and it did pull a 3CX background this time, which i'll have to work on changing later because it blacks out everything, I tried several different kinds of restarts and the results were the same as was the pcap.
....BUT, after a burger/vape induced epiphany, it occurred to me the behavior being exhibited can sometimes be indicative of a conflict of some kind on the network. I shutdown the 3CX server and cleared the arp cache on my computer, pinged, got a timeout, did arp -a, and, there was the answer staring at me. My machine had arp'd and pulled a different MAC address than the one belonging to the 3CX server, when an arp was being sent out on the network it was returning the MAC of the firewall for the 3CX's server's IP, this is why no HTTP packets hit the server, why it would provision only in the morning when i come in or after an extended period of time (ARP entry expired), and why when i rebooted the server it would provision but never again after that. I logged into our ASA and found out there is a rule I must have put in there when I first started trying to get the RTP traffic to flow. Since our ASA is pre 8.3 I can't setup a NAT entry for a range of ports for RTP, I found a way around this by creating a one-to-one NAT entry and putting the port range as a rule in the ACL on the outside interface, but the very first NAT entry I did was backwards and was causing the firewall to reply to ARP requests for the 3CX's IP. Good lord have mercy what a mess for a simple oversight on my part. Thank you all that replied, I am glad I posted here because if not I probably never would have uploaded those provisioning files to the server. NOW....I just have to figure out how to modify that background, I don't mind the 3CX logo for the moment, its the black background it has, it makes it impossible to see any of the text on the screen next to the BLF buttons.
If someone could provide some quick insight on that I would be greatly appreciative, but as usual I will be googling to see if I can figure it out.
....BUT, after a burger/vape induced epiphany, it occurred to me the behavior being exhibited can sometimes be indicative of a conflict of some kind on the network. I shutdown the 3CX server and cleared the arp cache on my computer, pinged, got a timeout, did arp -a, and, there was the answer staring at me. My machine had arp'd and pulled a different MAC address than the one belonging to the 3CX server, when an arp was being sent out on the network it was returning the MAC of the firewall for the 3CX's server's IP, this is why no HTTP packets hit the server, why it would provision only in the morning when i come in or after an extended period of time (ARP entry expired), and why when i rebooted the server it would provision but never again after that. I logged into our ASA and found out there is a rule I must have put in there when I first started trying to get the RTP traffic to flow. Since our ASA is pre 8.3 I can't setup a NAT entry for a range of ports for RTP, I found a way around this by creating a one-to-one NAT entry and putting the port range as a rule in the ACL on the outside interface, but the very first NAT entry I did was backwards and was causing the firewall to reply to ARP requests for the 3CX's IP. Good lord have mercy what a mess for a simple oversight on my part. Thank you all that replied, I am glad I posted here because if not I probably never would have uploaded those provisioning files to the server. NOW....I just have to figure out how to modify that background, I don't mind the 3CX logo for the moment, its the black background it has, it makes it impossible to see any of the text on the screen next to the BLF buttons.
If someone could provide some quick insight on that I would be greatly appreciative, but as usual I will be googling to see if I can figure it out.
