Phone Won't Ring from Specific Caller
threehappypenguins:
This problem was existent before I started receiving the SIP scanner calls, therefore before I entered the Inboundcallroute info to block numbers shorter than 4 digits.
Shale:
Quote from: threehappypenguins on August 18, 2013, 07:59:25 am
This problem was existent before I started receiving the SIP scanner calls, therefore before I entered the Inboundcallroute info to block numbers shorter than 4 digits.
I guess you are sure. What does the caller ID info look like on the the logs from your SIP providers? If it is 811 or other short or otherwise blocked string, you will have to change your SIP scanner prevention method anyway.
I don't know what AcroVoice autoprovisioning is, so I don't know why that prevents you from using OBiTalk. https://www.obitalk.com/forum/index.php?topic=4682.0 was your earlier thread on that, so maybe somebody will see a setting there which would account for your symptoms.
http://www.obitalk.com/forum/index.php?topic=707.0 could be of use to you in advanced troubleshooting, but I am not sure it would log incoming attempts that are blocked somehow. It has been a while since I tried it.
Wireshark can be used at the ethernet packet level, and it has some knowledge of SIP packets. Its use requires that the computer and the OBi be on the same real hub (such as Netgear DS104), and not on a switch that is called a hub (and those are more common). A real hub sells for a premium today. Ebay can be a good source for more reasonably priced ones. I bought mine used without a power supply, so I got a better price. http://wiki.wireshark.org/HubReference lists known hubs that work with Wireshark. The simplest question would be do packets arrive when you get the return call. If so, the content of packets is the next step. Wireshark is not so easy to use and interpret, and I hope you get this handled without having to muck around to that level.
Navigation
[0] Message Index
[*] Previous page