Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 1.0.7
-
Fix Version/s: None
-
Component/s: mod_sofia
-
Labels:None
-
Environment:Polycom 331 => FS => any dest
-
Platform:Linux x86_64/gcc
-
Uname:Linux sip2.babblevoice.com 2.6.18-194.32.1.el5 #1 SMP Wed Jan 5 17:52:25 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
-
CPU Info:
-
GCC Version:gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-48)
-
FreeSWITCH GIT Revision:head
-
Reproduced with GIT HEAD?:yes
-
lsb_release:
-
Target Version:
Description
Attached are to sip traces.
eyebeam to polycom test, in this call the eyebeam places the polycom on hold. The polycom can hear music on hold - works perfectly.
polycom to eyebeam test, in this call the polycom places the eyebeam on hold. The eyebeam hears nothing and the call will drop after a period time.
The main difference I have spotted between the two calls is the absence of a=sendonly in the SDP from the polycom.
The eyebeam is just for this example, this is replicated when the polycom has a call with other devices or destinations.
eyebeam to polycom test, in this call the eyebeam places the polycom on hold. The polycom can hear music on hold - works perfectly.
polycom to eyebeam test, in this call the polycom places the eyebeam on hold. The eyebeam hears nothing and the call will drop after a period time.
The main difference I have spotted between the two calls is the absence of a=sendonly in the SDP from the polycom.
The eyebeam is just for this example, this is replicated when the polycom has a call with other devices or destinations.