Call parking and intercom

Status
Not open for further replies.

tjb1231

Joined
May 15, 2012
Messages
10
Reaction score
0
I am having trouble setting up call parking and getting the intercom to work.
3cx V11 with Aastra 6731i firmware 2.6.0.2019

When a call comes in and you want to park it, we hit transfer then *01 to park it. It says call failed.
I am interested in setting up BLF parking buttons. What is the syntax for that in the phone interface?

Another issue we are having is

When I assign Intercom and paging to the programmable keys nothing happens.

We have a licensed version of 3cx.

Thanks

Here are some logs when I try to park a call
11-Jun-2013 14:37:59.988 L:12.1[Extn] failed to reach ParkOrb:*0, reason Forbidden
11-Jun-2013 14:37:59.988 Call to T:ParkOrb:*0@[Dev:sip:*[email protected]:40000;rinstance=693b91c3e307bd6d] from L:12.1[Extn] failed, cause: Cause: 403 Forbidden/INVITE from 127.0.0.1:40000
11-Jun-2013 14:37:59.988 [CM503003]: Call(C:12): Call to <sip:*[email protected]:5060> has failed; Cause: 403 Forbidden/INVITE from 127.0.0.1:40000
11-Jun-2013 14:37:59.837 [CM503025]: Call(C:12): Calling T:ParkOrb:*0@[Dev:sip:*[email protected]:40000;rinstance=693b91c3e307bd6d] for L:12.1[Extn]
11-Jun-2013 14:37:59.787 [CM503027]: Call(C:12): From: Extn:9005 ("9005" <sip:[email protected]:5060>) to T:ParkOrb:*0@[Dev:sip:*[email protected]:40000;rinstance=693b91c3e307bd6d]
11-Jun-2013 14:37:59.787 [CM503004]: Call(C:12): Route 1: from L:12.1[Extn] to T:ParkOrb:*0@[Dev:sip:*[email protected]:40000;rinstance=693b91c3e307bd6d]
 
Mileage varies, but I configured extensions 101-109 to forward to SP1-SP9 for a client.. then provisioned their 500S units with the shared parks so they (three receptionists) could see which parks were in play. It also helped them in the pre-11 days aka pre-ringback to see if a caller was in "Park Hell".

The BLFs are "labeled" 101-109. The forward makes it easy to "pickup" the call from a shop floor handset after a page, for example.

Beyond that.. couldn't say as far as that model.
My first guess would be the dial plan. If the call makes it to the PBX, that's probably not the problem.
BLF and Shared Parking works well.

Can't add about your PSK config, either. We tend to run Cisco.
 
I like your idea of calls being forwarded to the SP's. However I do not see that option in the forwarding rules of the extension.
 
Reverse the direction.. forward 101 to SP1 under the Busy/Unregistered section.

I stole that from a post two-ish years ago. ;)
 
I would also upgrade the firmware on your Aastra phones. If you look at the template notes, they are designed for the v3.2 firmware.
 
Ian,
I do not see, in v11 SP4, the ability to forward an extension to an SP. Unless I am not understanding your process.
 
craig -

I think that gs phones require the use of the "transfer" key to use the SP function; hence the reference to forward.

Also, I finally played some with the T46. Provisioning took all of a couple of minutes manually as the look, feel and all of the web interface is typical Yealink. I like it.
 
Larry,
They mention in the thread setting up an extension to transfer to SP under under Busy/Not Available... But I do not see that the SP's are available in the Drop Down list.
 
Sorry for the delay.
Indeed, if Phone is Busy, using an external number with SP6 as an example value.
 
Does not work. Error message. It does appear to be valid input using MyPhone however.
Note in v12 you can enter SP? in the External number field... but not in v11 SP4
 

Attachments

  • Screen Shot 2013-06-21 at 9.28.30 AM.png
    Screen Shot 2013-06-21 at 9.28.30 AM.png
    27.1 KB · Views: 995
Status
Not open for further replies.

Forum statistics

Threads
111,838
Messages
589,298
Members
164,668
Latest member
Infinity Network