- Joined
- Jan 13, 2012
- Messages
- 182
- Reaction score
- 59
Environment: 3CX Cloud v14 SP2, Raspberry Pi SBC 1.0.0.44201, Yealink T48G tried both firmware 35.73.0.50 and 35.80.0.70
I'm seeing odd behavior with Shared Parking between phones behind a RPi SBC.
When a call is made phone to phone (both phones are on the same LAN behind the SBC), when either phone puts the call into Shared Parking (using an assigned BLF), Music On Hold is not played to the other phone and often times, after the call is picked up from Shared Parking, only one-way audio is heard.
Additionally, when the call is picked up from Shared Parking, the direct phone to phone RTP network traffic communication path is lost. Instead, both phones begin communicating with the server, which is unfortunate because that's bandwidth intensive and abandons the convenient efficiency intended by using the SBC.
This problem does not appear to occur on voip provider calls coming into the server then phone extension. IOW, a typical incoming call.
This problem is easily duplicated on other 3CX frowned upon phones, so it's not specific to Yealink, but rather a RPi SBC programming problem.
3CX will you duplicate my environment in your lab and packet sniff the communication to see where it's falling down, please?
Thanks!
I'm seeing odd behavior with Shared Parking between phones behind a RPi SBC.
When a call is made phone to phone (both phones are on the same LAN behind the SBC), when either phone puts the call into Shared Parking (using an assigned BLF), Music On Hold is not played to the other phone and often times, after the call is picked up from Shared Parking, only one-way audio is heard.
Additionally, when the call is picked up from Shared Parking, the direct phone to phone RTP network traffic communication path is lost. Instead, both phones begin communicating with the server, which is unfortunate because that's bandwidth intensive and abandons the convenient efficiency intended by using the SBC.
This problem does not appear to occur on voip provider calls coming into the server then phone extension. IOW, a typical incoming call.
This problem is easily duplicated on other 3CX frowned upon phones, so it's not specific to Yealink, but rather a RPi SBC programming problem.
3CX will you duplicate my environment in your lab and packet sniff the communication to see where it's falling down, please?
Thanks!