The error message "Call failed due to network issue" can be caused from a number of different reason, the following post outlines some of the issue that I have so far found.
Monitoring Server The first thing to check is to check the monitoring server reports for an error message. Usually the error is some thing like "Call failed to establish due to a media connectivity failure when one endpoint is internal and the other is remote"
Candidate information Checking the candidate information from the SIP packets during the call. What we are looking for is that both the Edge AV Service IP address and the NAT IP address (of your home router etc) is being sent and received by the two clients. DNS If the candidate information is not being sent first thing to check is that the internal client can resolve the DNS host name of the Edge Server to the INTERNAL interface.
If the DNS results returned don't match the IP address of the internal check DNS to make sure that a error …
So I have been having this problem, when I click on a number in a missed call notification email from Lync my Google Chrome browser would launch to my homepage instead of the Lync client.
When I tried to change the default association of the TEL protocol, i was given the option of two (2) values..
Clicking the "Change Program" button gave me two (2) options
After much searching a registry entry was found to enabled the Lync application be to added to the list (Thanks Simon). Create a new REG_SZ "String Value" Under Computer\HKLM\Software\Microsoft\Office\15.0\Lync\Capabilities\URLAssociations\ called TEL with a value of "callto"
Once this key is added you are given a third chose for the TEL protocol association for Lync Selecting "Microsoft Lync" updates the associations to show Microsoft Lync as the default application for the TEL URL.
Now clicking the number in the missed call notification email and it launches the Lync client.
Was setting up an FXO analog port for an in-dial today, with an AudioCodes Mediant 800, has some issues with getting the FXO to make and receive calls. After a few email with support at VExpress finally got it sorted.
The basic configuration of the Mediant 800 is much the same as all their other gateways, the FXO port needed a little tweaking that I hadn't been able find in any other documents.
The only additional configuration that was required was under "VoIP --> GW and IP to IP --> Analog Gateway --> FXO Settings" and under "VoIP --> GW and IP to IP --> Analog Gateway --> Automatic Dialing"
FXO Settings Change the "Dialing Mode" to One Stage
Automatic Dialling Then we had to setup the Automatic Dialling you just need to set the phone number that corresponds to the FXO line that is being configured.
UPDATE: So with this configuration we were seeing some issues with call quality on the Lync end. The PSTN caller could hear with no issues a…