December 16, 2017, 04:25:21 pm *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: [1]
  Print  
Author Topic: Using Blind Transfer  (Read 11400 times)
RonR
Forum Member

Posts: 4528


« on: April 16, 2012, 03:59:17 pm »

A virtually undocumented feature in the OBi is Blind Transfer.

Existing calls on the OBi's PHONE Port can be blind transferred to any number the OBi is capable of reaching.

The procedure is:

- Press the FLASH button on the phone

- Wait for a new dialtone

- Dial *98

- Wait for a new dialtone

- Dial the number that the call is to be transferred to

- Wait for a confirmation tone

- Hang up the phone
Logged
ProfTech
Sr. Member
****
Posts: 377


« Reply #1 on: April 19, 2012, 03:53:06 pm »

Interesting information. Doesn't transfer tie up two sessions if Voip to Voip or your PSTN line and one Voip session? I don't really have a need for the transfer function but have always wondered about it since the manual clearly states the Obi bridges the call. Some of the information in the manual leads one to believe that the bridging can be avoided if both calls are Voip and your ITSP supports the transfer function but I'm not sure what providers might support it.   [Huh]
Logged
RonR
Forum Member

Posts: 4528


« Reply #2 on: April 19, 2012, 06:05:59 pm »

Doesn't transfer tie up two sessions if Voip to Voip or your PSTN line and one Voip session?

Yes, by default it bridges regardless of the service provider.

Some of the information in the manual leads one to believe that the bridging can be avoided if both calls are Voip and your ITSP supports the transfer function but I'm not sure what providers might support it.

That's the SIP Refer mechanism, but recent posts seem to indicate there may be problems with the OBi's implementation of it.
Logged
MichiganTelephone
OBi110 Beta Testers
***
Posts: 484


« Reply #3 on: April 20, 2012, 01:27:03 pm »

There is a problem with the X_UseRefer option not working as it should in some, but not all situations.  Apparently it's an issue that shows up primarily with certain versions of Asterisk, and my gut feeling is that it involves a timing issue of some kind.  Obihai customer support did push some beta firmware to my OBi202 which fixed the issue, but as far as I know this fix has not yet been rolled into any version of the release firmware yet (however there's been no new firmware releases since they made that fix).  If someone has a real need for this feature to work and it's not working now (check first, because apparently it does work with some installations), and you have an OBi202, you could request that customer support push firmware version 3.0.0 (Build: 3089MD ) to your OBi202 (I have no idea whether they have a version of the OBi1x0 firmware that contains this fix).

If it's not working, what will happen is that when you attempt to transfer a call, it will act as if the called endpoint is busy and handle the call accordingly (by returning a busy signal, going to voicemail, going to the next number in a follow-me, etc.).

Hopefully Obihai will include this fix in the next full firmware release, because it definitely solved the problem for me.
Logged

Inactive, no longer posting or responding to messages.  Goodbye and good luck.  Some of my old Obihai-related blog posts have been moved to http://tech.iprock.com - note this in NOT my blog; I have simply given the owner permission to repost some of my old stuff.
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC