Author Topic: Question about "Broadsoft" support for SIP End Point.  (Read 496 times)

Offline victor

  • Administrator
  • Hero Member
  • *****
  • Posts: 1400
  • Karma: 18
Question about "Broadsoft" support for SIP End Point.
« on: August 06, 2019, 08:40:37 AM »

what is SIP extensions event package aka Broadsoft SIP extensions. I know of a company called Broadsoft. Do we need to buy some third-party package to control a SIP end-point and Genesys does not offer it itself? (floored) I am sure I am missing something here.

Genesys manual states:

If an endpoint (SIP phone) supports remote CTI control by providing the SIP extensions event package known as "BroadSoft" SIP extensions, SIP Server allows SIP Server clients to answer the call by means of the TAnswerCall request. When responding to the TAnswerCall request, SIP Server will send an event with the header "Event" and a header value of "talk" to the SIP phone, in a ringing state of NOTIFY. This event instructs the SIP phone to answer the call without human interference. Note that SIP phones that support such an event package should send a 180 Ringing message header of "Allow-Events:", which should contain "talk" inside its value.

Offline hsujdik

  • Sr. Member
  • ****
  • Posts: 394
  • Karma: 15
Re: Question about "Broadsoft" support for SIP End Point.
« Reply #1 on: August 06, 2019, 10:17:42 AM »
"talk" and "hold" events were developed by broadsoft but never made it into an RFC although many vendors implement it on the NOTIFY requests