" /> SIP disconnect Softphones - Genesys CTI User Forum

Author Topic: SIP disconnect Softphones  (Read 6122 times)

Offline cjrennie

  • Newbie
  • *
  • Posts: 6
  • Karma: 0
SIP disconnect Softphones
« on: September 30, 2008, 04:52:01 PM »
Advertisement
Have problems with softphones (X-Lite and NCH) disconnecting from the Genesys SIP Server. The call is completed and will stay connected for about 30 sec before disconnecting both parties. I have a speech path between them.

Searched Google any have tried the solutions, but still having problems.

Since it is two are different types could it be a setting in the Ext or the SIP in CME?

Offline René

  • Administrator
  • Hero Member
  • *****
  • Posts: 1832
  • Karma: 62
Re: SIP disconnect Softphones
« Reply #1 on: September 30, 2008, 09:41:05 PM »
Hi,

There could be several reasons for such behaviour - wrong SIP extension configuration, wrong configuration of media gateway etc. Could you post SIP Server log here?

R.

Stephane

  • Guest
Re: SIP disconnect Softphones
« Reply #2 on: March 27, 2009, 03:28:15 PM »
Not certain whether this parameter is related to your issue or not, but in my case, when dialing a Routing Point having voice treatments played by Stream Manager via a Routing Strategy... the call would terminate at exactly 30 seconds. At first I thought it was a SIP Server option, but after looking at all of those settings, I discovered that my X-Lite (or Eyebeam) was configured with a timeout of 30 seconds for Call Inactivity (i.e. the default setting on X-Lite and/or EyeBeam)... Specifically, right-click on the X-Lite (or EyeBeam) SIP softphone, choose "options", click on "advanced"... choose "network" and you will see a checkmark option that says "Call Inactivity": "In times of network disruption, automatically hang up calls after:" and you will see RTCP is set to 30 seconds... Remove this checkbox. This worked in my case/scenario... I am using SIP Server 7.6.X

Offline kowari

  • Jr. Member
  • **
  • Posts: 53
  • Karma: 0
Re: SIP disconnect Softphones
« Reply #3 on: March 30, 2009, 04:11:22 AM »
Always trace the call in the TServer and URS logs and see what is happening.
Chances are, it is something reasonably simple :)

If you are feeling excited (or confused in equal parts) throw the logs up here and we can see if we can see the probelm.