snowsam
Customer
- Joined
- May 26, 2011
- Messages
- 86
- Reaction score
- 3
We have been using shared parking spots for several years using the Extension forwarded to a Parking spot method.
That way our users transfer a call to 5005 to put it in shared parking spot #5. Then someone else is able to pick that call up by dialing 5005. It has worked well, especially with phones that don't have buttons. Our inbound lines have been via a Patton box to a PRI.
We recently added some VOIP inbound lines for some vanity numbers via a vendor that supports 3CX. Only with calls that come in via these numbers, we have issues when unparking these calls via the extensions. Often, the call will continue to play the hold music to the inbound caller and the person who picked up the call gets silence. When the person who picked up the call hangs up, the call terminates.
If we do the same scenario and park and unpark right clicking using the 3CXPhone app, the problem does not occur.
If we are receiving a call via the patton, the problem does not occur.
Has anyone else experienced this? We have put a case in with the VOIP vendor, and will update if there is any "ah-ha" from that.
We mostly have yealink T26P and T22P phones.
Between Christmas and new years we upgraded to v14 sp2 from 12.5.
Hmm.
That way our users transfer a call to 5005 to put it in shared parking spot #5. Then someone else is able to pick that call up by dialing 5005. It has worked well, especially with phones that don't have buttons. Our inbound lines have been via a Patton box to a PRI.
We recently added some VOIP inbound lines for some vanity numbers via a vendor that supports 3CX. Only with calls that come in via these numbers, we have issues when unparking these calls via the extensions. Often, the call will continue to play the hold music to the inbound caller and the person who picked up the call gets silence. When the person who picked up the call hangs up, the call terminates.
If we do the same scenario and park and unpark right clicking using the 3CXPhone app, the problem does not occur.
If we are receiving a call via the patton, the problem does not occur.
Has anyone else experienced this? We have put a case in with the VOIP vendor, and will update if there is any "ah-ha" from that.
We mostly have yealink T26P and T22P phones.
Between Christmas and new years we upgraded to v14 sp2 from 12.5.
Hmm.