search

signalwire / freeswitch

FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a versatile software implementation that runs on any commodity hardware. From a Raspberry PI to a multi-core server, FreeSWITCH can unlock the telecommunications potential of any device.
https://freeswitch.com/#getting-started
Other
3.56k stars 1.41k forks source link

FreeSwitch 1.8.5 sends "early" state instead of "terminated" when call ends and BLF is configured #156

Open Mickey34 opened 4 years ago

Mickey34 commented 4 years ago

Hello, I've got an issue with Avaya J100 phones and FreeSwitch server. I have 3 phones: J179 - extension 2121, BLF key is set to monitor extension 2122 J139 - extension 2122 J129 - extension 2123 FreeSwitch has defaults config. Steps to reproduce: 1) Make a call from 2122 to 2121 2) Make a call from 2123 to 2122 3) End call from 2123 After step 3 phone with extension 2121 shows on BLF key that 2123 calls to 2122. The problem is in freeswitch notify. When 2123 calls to 2122, freeswitch sends notify with state "early" to 2121, so 2121 shows "incoming call". But when 2123 ends call, freeswitch sends exactly same notify to 2121 with "early" state again and 2121 shows "incoming call" again. It happens only when a call from monitored phone to monitoring phone exist. Freeswitch sends normal notify with "terminated" state without the second call. You can see it in packet 50 of attached trace. blf_notify1.zip

SeanDevoy commented 4 years ago

I have the same problem, in a simpler test. With extensions defined as above, when 2122 calls 2121 and then hangs up, 2121's BLF for 2122 stays lit. The phone vender examined the capture and says FreeSwitch is not sending the NOTIFY to 2121 that 2122 hung up.