Home » Forums » Community Edition » Open Discussion

Place caller on hold - should be simple

ericvititoe
Posts: 11
 Member Since:
2008-01-21
Submitted by ericvititoe on Thu, 04/02/2009 - 8:14am.

I'll cut to the chase...

I'm using TB CE 2.6.1.10. I have only 2 extensions. Ext 101 is a cheap Grandstream BT 101. Ext 102 is a cordless phone connected to a DVG-1120S.

Both ext work fine making and receiving calls. But ext 102 cannot place calls on hold or transfer. It's easy with the Grandstream, but the cordless phone obviously doesn't have the function buttons on it.

I've tried several button combinations: hook flash, ##, *700, everything I could find on google. But, nothing works. Asterisk doesn't even recognize the hook flash. I've set the flash in the DVG from the minimum of 100ms to the max of 2200ms, but nothing works.

Any ideas?

‹ Caller ID App for Blackberry? Final Setup: Paging, Intercom, Conference ›

&nbsp

hgolbar
Posts: 16
 Member Since:
2009-03-05
I'm trying to figure out a
Thu, 04/16/2009 - 6:25pm

I'm trying to figure out a similar problem. I able to get the transfer to work when it's an incoming call by hitting ##. But this is not working on the outgoing end. The phone I'm trying on is an unlocked ATS 6100s.


&nbsp

hgolbar
Posts: 16
 Member Since:
2009-03-05
I found the solution that
Wed, 04/22/2009 - 3:36pm

I found the solution that worked for me on the "General Settings" page in FreePBX. It was "Asterisk Dial command options," I added a Ttr and ## now works fine. You might want to also check that in your "Feature Codes," "In-Call Asterisk Blind Transfer" is enabled and set to the default ##.


&nbsp

tmwanda
Posts: 4
 Member Since:
2009-03-03
Mediatrix 4102 won't place call on hold
Wed, 11/04/2009 - 10:13am

TomW

I'm currently experiencing a problem with the Mediatrix 4102 where when a 2nd call comes in, you hook flash, you successfully answer the 2nd call, but the 1st caller gets dropped. Happens over a wide range of settings related to the hook flash processing and DTMF transport modes. The 4102 behaves in a manner consistent with its Call Hold function not working or being disabled (but it is enabled). I also have ATA's from Grandstream and they do not exhibit this problem at all.

Any ideas on what could be wrong. It seems like 4102 F/W versions are not the culprit as this problem also appears on 4102's with much older F/W than the curent version.

So any ideas out there?

--

TomW


&nbsp

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.