Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: brendanb on May 04, 2017, 10:28:29 AM
-
Hi
I need some advise.
I have installed the latest version of Workspace desktop edition as well as the latest version of the sipendpoint.
The sipendpoint will not work correctly. When you open the application its starts and the voice channel is available but when you make a call after 30 seconds the voice channel goes out of service.
You can see URS trying to target the agent but because the sip endpoint is not initialized correctly it can not route the call to the agent.
I have the correct .net Installed that is in the requirement as well as the Redistributables. There are no errors in the SIP endpoint log and no errors in the Workspace Desktop Edition logs.
Regards
-
This seems like network or firewall related issue, not the WDE itself.
-
Hi
I have now found the following
It seems the RTP is being blocked.
I see the following messages in the sip server log
13:50:27.959: CGSIPListenerImplementation: Exception on listen socket[708] UDP
13:50:29.959: Sending [0,UDP] 653 bytes to 10.51.0.84:5060 >>>>>
On both the server and the Windows 10 pc all firewalls has been disabled.
Regards
-
I had that problem when my SIP Server had 2 NICs, by forcing SIP Server to use the correct one worked.
Win10 works fine. Something else is your problem.
-
Run a tracert to the sip server from your desktop and then from sip to desktop. This could indicate any connectivity problems.
-
Hi
Thank you for the response
The problem is that this is a VM on my laptop. It is not a server some where in a server room
From the SIP endpoint log the sipendpoint starts up fine with no errors there are also no errors in the WDE log.
However when I try to launch the WDE on the server I get the below error in the SIP endpoint log. Not sure if this might be related. According to a similar case logged on Genesys it is a problem with .net update. I do not have the referenced .nets installed
17-05-10 11:21:13.752 [ 29] ERROR ndpointCommunication - The IW SIP Endpoint is not available at this time. Exception while communicating with Endpoint:
System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.pipe://localhost/SIPPipe2001_192.168.30.139:5060/2001 that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.IO.PipeException: The pipe endpoint 'net.pipe://localhost/SIPPipe2001_192.168.30.139:5060/2001' could not be found on your local machine.
--- End of inner exception stack trace ---
Server stack trace:
at System.ServiceModel.Channels.PipeConnectionInitiator.GetPipeName(Uri uri, IPipeTransportFactorySettings transportFactorySettings)
at System.ServiceModel.Channels.NamedPipeConnectionPoolRegistry.NamedPipeConnectionPool.GetPoolKey(EndpointAddress address, Uri via)
at System.ServiceModel.Channels.CommunicationPool`2.TakeConnection(EndpointAddress address, Uri via, TimeSpan timeout, TKey& key)
at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Call(ServiceChannel channel, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Genesyslab.Desktop.Modules.SIPEndpointCommunication.Channels.IServiceSIPEndpoint.set_Options(Dictionary`2 value)
at SIPEndpointSDKApplication.NamedPipeServiceSIPEndpoint.set_Options(Dictionary`2 value)
at Genesyslab.Desktop.Modules.SIPEndpointCommunication.SIPEndpoint.ConfigureAndStartEndpoint()
I have no problem connecting to the VM from my laptop
Regards
-
What say WDE SE logs?
-
33 seconds is usually for how long traffic is accepted while waiting for INVITE / ESTABLISH in SIP. Most likely one of SIP fields are off or you are receiving the call on inet that has a different IP address than SIP message. Have you tried comparing the two?
-
Hi
Apologies I have left this one for a long time.
The problem is still ongoing.
The following has been established.
I use a laptop. What has been found is the following. If disable the wireless network and unplug the network cable you can then open the WDE and it will work. You can now plug in the network cable and it will still work as long as you do not close the WDE.
Remember this is a VM on my laptop that I use for testing.
Regards
-
It seems you are using old version of WDE SEP where was a known bug which causes using an incorrect NIC on local PC.
-
Hi Kubig
At the time it was the latest WDE available. Thank you I will have a look on the Genesys site if there is a newer version available. Do you maybe know in witch release the bug was fixed.
Regards
-
Just install last version
Enviado de meu E6633 usando Tapatalk
-
Thank you
Installing the latest version resolved the problem
Regards
-
Hi All,
I am awaking this topic again, We are on the latest version of WDE. WDE does work fine when user work from office but it doesn't work when users work from home using the VPN. This is the exact similar situation initially posted here on this topic that they receive error "Voice Channel Out of Service" ... Could you please advise what else can be checked here.
-
Check the communication matrix whether required communication protocols and used ports are allowed
-
Be sure you configure WDE options to use the VPN Ethernet interface in case of your VPN install an interface
Enviado de meu SM-N9600 usando o Tapatalk
-
Hi All,
Thanks for your kind response. This issue is resolved, There was firewall rules created in the Windows Defender Firewall which were causing it. We created the new firewall rule to pass the UDP traffic which fixes it.
Thanks