Genesys Engage on-premises

 View Only

Discussion Thread View

  • 1.  wde registration duplicity

    Posted 11-13-2023 04:35
    Hello everyone, I'm experiencing strange behavior on one of our clients, after I made an architectural change to the wde "REGISTRATION", where some machines kept requesting registration for the new and old address, even closing and opening the wde.
     
    The activity carried out was basically clearing the option "sipendpoint.sbc-register-address=" and asking everyone to close and open wde again.
     
    Some observations:
    After I successfully carried out some isolated tests of this new architecture, we implemented the turnaround into production at night for the entire operation. However, during the night, due to a connection problem with some operators who were having difficulty registering the sipendpoint, the support team had to roll back.
    The next day, we identified that the Configuration Master was processing very high, due to many registration requests, so it was not possible to write anything in the Configuration, the solution was to restart.It was verified that in the "contact" value of the DN, the IP address keeps changing with this sipendpoint registration duplicity behavior.
     
    Well guys, has anyone experienced this, or have any idea what could have happened?
     
    IWSIPEndpoint_14047.20231110T105224.026.log:
     
    Command Line: "C:\Program Files (x86)\GCTI\Interaction Workspace\InteractionWorkspaceSIPEndpoint\InteractionWorkspaceSIPEndpoint.exe" /logdirectory:"C:\Users\GNDI89492\AppData\Roaming\Genesys Telecommunication\InteractionWorkspace\log" /loglevel:all /logsegment:10MB /logexpire:10 /user:14047 /domain:172.20.41.53:5060 /videoLocation:50;50;640;480
     
     
     
    10:53:50.447 Trc 09900 Application.ServiceSIPEndpoint.GLogger |inf|15672|SIPconn[2404,UDP] 509 bytes to 172.20.41.53:5060 >>>>>
     
    REGISTER sip:172.20.41.53:5060;transport=UDP SIP/2.0
     
    From: "Genesys0" <sip:14047@172.20.41.53:5060>;tag=27350AC4-0EDA-4EA3-B690-DADBAC343F00-72
     
    To: <sip:14047@172.20.41.53:5060>
     
    Call-ID: DAF6EA14-BAAB-4A6F-AEE1-7F57B7A83079-57@REFr
     
    CSeq: 701 REGISTER
     
    Content-Length: 0
     
    Via: SIP/2.0/UDP 10.148.215.3:5060;branch=z9hG4bK6F82BE8E-CE11-4D08-8932-D987AFBFC455-1003
     
    User-Agent: Genesys-SIPendpointSDK/9.0.030.03 (Windows 10.0.19045)
     
    Max-Forwards: 70
     
    Contact: <sip:14047@10.148.215.3:5060>
     
    Expires: 180
     
     
    IWSIPEndpoint_14047.20231110T090104.685.log:
     
    Command Line: "C:\Program Files (x86)\GCTI\Interaction Workspace\InteractionWorkspaceSIPEndpoint\InteractionWorkspaceSIPEndpoint.exe" /logdirectory:"C:\Users\GNDI89492\AppData\Roaming\Genesys Telecommunication\InteractionWorkspace\log" /loglevel:all /logsegment:10MB /logexpire:10 /user:14047 /domain:172.22.23.50:5060 /videoLocation:50;50;640;480
     
     
     
    10:54:05.268 Trc 09900 Application.ServiceSIPEndpoint.GLogger |inf|8340 |SIPconn[2408,UDP] 508 bytes to 172.22.23.50:5060 >>>>>
     
    REGISTER sip:172.22.23.50:5060;transport=UDP SIP/2.0
     
    From: "Genesys0" <sip:14047@172.22.23.50:5060>;tag=9E4C5BB3-9395-4661-AB3E-8CACBD7F2D07-803
     
    To: <sip:14047@172.22.23.50:5060>
     
    Call-ID: 7FDBAE5E-5015-4B7C-B2AD-92B7C65EFFB3-799@NC1d
     
    CSeq: 1 REGISTER
     
    Content-Length: 0
     
    Via: SIP/2.0/UDP 10.148.215.3:5061;branch=z9hG4bKF072F7BE-B987-4CB8-83DF-42DE82DCCE30-878
     
    User-Agent: Genesys-SIPendpointSDK/9.0.030.03 (Windows 10.0.19045)
     
    Max-Forwards: 70
     
    Contact: <sip:14047@10.148.215.3:5061>
     
    Expires: 180

    #SIP/VolP

    ------------------------------
    [Andre] [Algusto]
    [Atento]
    ------------------------------


  • 2.  RE: wde registration duplicity

    Posted 11-14-2023 07:38

    We had something similar crop up recently and there was an update provided. See if it's applicable https://docs.genesys.com/extensions/Repository/cache/public/Interaction%20Workspace/8.5/iw_sip-endpoint_85rn.html#8.5.115.46



    ------------------------------
    Karl Theurer
    Optum Technology, Inc
    ------------------------------

    Original Message


  • 3.  RE: wde registration duplicity

    Posted 11-14-2023 07:48

    Thank you for the information, after some more analysis, we identified that the machines that exhibited this behavior were because they were running two "InteractionWorkspaceSIPEndpoint.exe" processes. For some reason one of the processes was not closed, and as we had a change in the registration address, it generated this behavior of duplication of registration for different addresses.



    ------------------------------
    [Andre] [Algusto]
    [Atento]
    ------------------------------

    Original Message


  • 4.  RE: wde registration duplicity

    Posted 11-14-2023 07:50

    From what I understand in this hotfix, it fixes the problem with changing the local IP of the machine and in my case the change was the IP of the server that we changed in the wde application.



    ------------------------------
    [Andre] [Algusto]
    [Atento]
    ------------------------------

    Original Message


  • 5.  RE: wde registration duplicity

    Posted 11-14-2023 08:05

    The way your SIP signaling was in the example, looked really similar to what we were dealing with. But two SIP endpoint processes running would cause that too. 



    ------------------------------
    Karl Theurer
    Optum Technology, Inc
    ------------------------------

    Original Message


Need Help finding something?

Check out the Genesys Knowledge Network - your all-in-one access point for Genesys resources