![]() As most of the end-points are located behind a NAT-ted More concrete, these providers require the use of public IPĪddresses in the Contact header by the end-points when they REGISTER or make STUN is an obsolete broken standard that claimed that it solved NAT The requirement of SIP service provider to wrongly use STUN for NAT traversal purposes, see STUN section below.īlink does not interoperate with SIP service providers that require STUN for.If Blink got it wrong we can fix it, just report the problem to Blink Support Forum If this is the case or not, the SIP trace can indicate whether Blink or the other server or device is wrong. Blink is newer software that emerged after standards have been matured and we put lot of effort into making it work correctly according to the standards, while we may have not achieved 100% correctness, we still do better than many older implementations that implemented the standards before they were in a final shape. We have seen many cases where both the client and server were old and buggy but worked well with each other. Two broken devices can work well together until one gets fixes or a newer is brought in. This is bold statement but we have seen it so many times.If they point to a problem in Blink implementation we will do our best to fix it. You must send the SIP trace obtained from Blink to the SIP service provider and ask them for support. The SIP Server does not like the offer proposed by Blink (like a certain header or codec) and instead of refusing the call using a proper code as mandated by the SIP standard, it simply does not answer.It is possible that other software works while Blink does not. Send the archive to forget to disable the logging once you are done with their collection. ![]() In case of complete software crash, the Blink crash report, you can find it using Console application Or by using the Console application, you can filter by 'Blink' and save the output to file. Grep Blink /var/log/system.log > activity.txt var/log/system.log If the file is too big, you can filter the log lines by using in Terminal application the command: Repeat the action that causes the problemĪll files in the folder ~/Library/Containers//Data/Library/Application\ Support/Blink\ Pro/logs/ Go to Preferences -> Advanced -> File LoggingĬheck boxes Log SIP Signaling, Log Notifications and Log Core Engine ![]() Enable SIP (check box Everything and select all applications), Notifications and Engine logs Make sure you run the last version available in the Mac App Store ![]() If the software crashes or fails to handle incoming or place outgoing calls you can send the logs for analysis as follows: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |