" /> Workspace Desktop Issue - Genesys CTI User Forum

Author Topic: Workspace Desktop Issue  (Read 5066 times)

Offline mic

  • Newbie
  • *
  • Posts: 44
  • Karma: -1
Workspace Desktop Issue
« on: February 12, 2017, 11:38:23 AM »
Advertisement
i am having a training as Genesys system engineer, and i just deployed Workspace and Genesys sip end point, and every time i try to call the workspace from X-lite (which is on the same host) the Workspace create infinite no of multiple tabs of "consultation call".


Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Workspace Desktop Issue
« Reply #1 on: February 12, 2017, 04:13:31 PM »
Check SIP logs and maybe xlite is causing some port conflict. Check IWS logs. Not a good idea to test 2 sip endpoints on a single PC.

Enviado de meu E6633 usando Tapatalk


Offline mic

  • Newbie
  • *
  • Posts: 44
  • Karma: -1
Re: Workspace Desktop Issue
« Reply #2 on: February 12, 2017, 08:11:18 PM »
thanks cavagnaro
i made sure that the x-lite port doesn't conflict with another.
every time i open the workspace this msg appears "Workspace SIP Endpoint is not available.The Registration is still in progress"


this is part of the sip srvr log
2:02:34.527: $-NET:SIP::0:0

22:02:36.527: $+NET:SIP::0:0
22:02:36.527: SIPTR: Received [0,UDP] 514 bytes from 192.168.75.132:5060 <<<<<
REGISTER sip:192.168.75.132:5060 SIP/2.0
From: "Genesys0" <sip:6001@192.168.75.132:5060>;tag=7CCCE9DF-76F6-4783-BAAC-655A738D463A-1
To: <sip:6001@192.168.75.132:5060>
Call-ID: F8398D44-8172-4D56-9F85-F2590A1B83DC-1@192.168.75.132
CSeq: 1 REGISTER
Content-Length: 0
Via: SIP/2.0/UDP 192.168.75.132:5060;branch=z9hG4bK8D2C3D55-F7EF-4899-9CA1-8C373D764DFE-1
User-Agent: Genesys-SIPendpointSDK/8.5.200.64 (OS version:6.0.6002.131072)
Max-Forwards: 70
Contact: <sip:6001@192.168.75.132:5060>
Expires: 1800


22:02:36.527: Sending  [0,UDP] 476 bytes to 192.168.75.132:5060 >>>>>
SIP/2.0 200 OK
From: "Genesys0" <sip:6001@192.168.75.132:5060>;tag=7CCCE9DF-76F6-4783-BAAC-655A738D463A-1
To: <sip:6001@192.168.75.132:5060>;tag=A7F8E459-78A7-4E25-A3C9-8EFD64A7EC7A-934
Call-ID: F8398D44-8172-4D56-9F85-F2590A1B83DC-1@192.168.75.132
CSeq: 1 REGISTER
Via: SIP/2.0/UDP 192.168.75.132:5060;branch=z9hG4bK8D2C3D55-F7EF-4899-9CA1-8C373D764DFE-1;received=192.168.75.132
Expires: 1800
Contact: <sip:6001@192.168.75.132:5060>;expires=1800
Content-Length: 0


22:02:36.527: $-NET:SIP::0:41

22:02:36.527: $+NET:SIP::0:0
22:02:36.527: SIPTR: Received [0,UDP] 476 bytes from 192.168.75.132:5060 <<<<<
SIP/2.0 200 OK
From: "Genesys0" <sip:6001@192.168.75.132:5060>;tag=7CCCE9DF-76F6-4783-BAAC-655A738D463A-1
To: <sip:6001@192.168.75.132:5060>;tag=A7F8E459-78A7-4E25-A3C9-8EFD64A7EC7A-934
Call-ID: F8398D44-8172-4D56-9F85-F2590A1B83DC-1@192.168.75.132
CSeq: 1 REGISTER
Via: SIP/2.0/UDP 192.168.75.132:5060;branch=z9hG4bK8D2C3D55-F7EF-4899-9CA1-8C373D764DFE-1;received=192.168.75.132
Expires: 1800
Contact: <sip:6001@192.168.75.132:5060>;expires=1800
Content-Length: 0


22:02:36.527: $-NET:SIP::0:7

22:02:37.536: $+NET:SIP::0:0
22:02:37.536: SIPTR: Received [0,UDP] 514 bytes from 192.168.75.132:5060 <<<<<
REGISTER sip:192.168.75.132:5060 SIP/2.0
From: "Genesys0" <sip:6001@192.168.75.132:5060>;tag=7CCCE9DF-76F6-4783-BAAC-655A738D463A-2
To: <sip:6001@192.168.75.132:5060>
Call-ID: F8398D44-8172-4D56-9F85-F2590A1B83DC-2@192.168.75.132
CSeq: 1 REGISTER
Content-Length: 0
Via: SIP/2.0/UDP 192.168.75.132:5060;branch=z9hG4bK8D2C3D55-F7EF-4899-9CA1-8C373D764DFE-2
User-Agent: Genesys-SIPendpointSDK/8.5.200.64 (OS version:6.0.6002.131072)
Max-Forwards: 70
Contact: <sip:6001@192.168.75.132:5060>
Expires: 1800


22:02:37.536: Assocaited transport for the device [11622] changed from [:0:0] to [192.168.75.132:5060:1]
22:02:37.536: TRNMNGR: internal domain 192.168.75.132
22:02:37.536: SIPTS: handle registration event 0
22:02:37.536: REGISTRAR:DN[6001]:OBSOLETE REGISTRATION FOUND: TERM >> DLG[926]
22:02:37.536: ProcessRegister: No GSIPCTI subscription found for [6001]
22:02:37.536: Sending  [0,UDP] 476 bytes to 192.168.75.132:5060 >>>>>
SIP/2.0 200 OK
From: "Genesys0" <sip:6001@192.168.75.132:5060>;tag=7CCCE9DF-76F6-4783-BAAC-655A738D463A-2
To: <sip:6001@192.168.75.132:5060>;tag=A7F8E459-78A7-4E25-A3C9-8EFD64A7EC7A-935
Call-ID: F8398D44-8172-4D56-9F85-F2590A1B83DC-2@192.168.75.132
CSeq: 1 REGISTER
Via: SIP/2.0/UDP 192.168.75.132:5060;branch=z9hG4bK8D2C3D55-F7EF-4899-9CA1-8C373D764DFE-2;received=192.168.75.132
Expires: 1800
Contact: <sip:6001@192.168.75.132:5060>;expires=1800
Content-Length: 0

 

Offline nonny

  • Full Member
  • ***
  • Posts: 218
  • Karma: 2
Re: Workspace Desktop Issue
« Reply #3 on: February 13, 2017, 07:59:32 AM »
Turn off role for using endpoint and don't install it if you're using something else.

Sent from my SM-N9005 using Tapatalk


Offline mic

  • Newbie
  • *
  • Posts: 44
  • Karma: -1
Re: Workspace Desktop Issue
« Reply #4 on: February 13, 2017, 01:00:20 PM »
cavagnaro: i made sure that there is no conflict between xlite port and any other port and the problem still exist ( the workspace issue multiple "consultation call from unidentified") and whenever i open it it shows me this message(Workspace SIP Endpoint is not available.The Registration is still in progress)
nonny: wher can i find this "role"

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: Workspace Desktop Issue
« Reply #5 on: February 13, 2017, 01:12:35 PM »
Your used deployment seems to be wrong - my opinion is wrong role definition and incorrect configuration on X-Lite level.

Offline mic

  • Newbie
  • *
  • Posts: 44
  • Karma: -1
Re: Workspace Desktop Issue
« Reply #6 on: February 13, 2017, 01:16:30 PM »
what would you recommend me to do Kubig..and in detail if you well?

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: Workspace Desktop Issue
« Reply #7 on: February 13, 2017, 01:18:43 PM »
Check what is your IWS/WDE configured (especially on SE level). Check the X-Lite configuration on what URI is registering. Check the SIP flow and T-Lib messages to find-out what is wrong.

Offline mic

  • Newbie
  • *
  • Posts: 44
  • Karma: -1
Re: Workspace Desktop Issue
« Reply #8 on: February 13, 2017, 01:32:31 PM »
i really appreciate your responds and patience
could you please tell me what is the SE level, and what does it mean to check the xlite uri? and how to check the Sip flow ?
and from where can i learn how to readthe T-Lib messages?
i am new to Genesys so that is why i am asking these basic questions...but i really appreciate your help?

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Workspace Desktop Issue
« Reply #9 on: February 13, 2017, 01:41:53 PM »
My suggestion, go clean.
Forget XLite for now, you are adding dust to your tests. Worst if you have no clear idea on what you are doing.
The fact that the WDE SIP Endpoint can't register means something is blocking it. Firewall maybe? What does SIP Server logs shows on REGISTER request? NO need to know Tlib here, just basic SIP messaging, which I assume you at least manage that.

Once you have your WDE and WDE SIP Endpoint working go with XLite and see what happens

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: Workspace Desktop Issue
« Reply #10 on: February 13, 2017, 01:43:54 PM »
Strongly recommend to visit any Genesys Training to understand what Genesys is, how it works and the basic and general flow/events-model.

SE is a SIP Endpoint, in your case you should have only one SE per WDE instance - so you have to decide if you will use the embedded Genesys SE or any external like X-lite. The configuration of WDE + SE should covered the available guides (there is no place for describing entire WDE product). If you are using the X-Lite as a "customer" side/phone, you should register it under any non-internal number.