|
Title: Obi110 setup for VOICEMAIL access to LINE - local PBX system Post by: searchformission on July 27, 2014, 11:08:07 am I am trying to find a way to access my local phone system's voicemail.
To access my local voicemail system, I need to dial: pressing FLASH button, then *130 (the setup connected directly, without the Obi110). With the current setup, the voicemail/local phone PBX is connected to my Obi110's LINE port. The reason I want to go with this setup is so that I only need one phone to call/receive connections from SP1/SP1/landline. When I tried to press "#" to switch to the LINE port and try the above pattern, I can't. There is some sort of conflict or confusion between the Obi and the PBX in handling this. Is there a way to configure the Obi to allow me to do this? Is this setup possible? I already tried removing SP1 and SP1 from being the primary line, and dialed the above pattern. Nothing works for now. Thanks for any suggestion you can provide. Edit: Removed confusing info. Title: Re: Obi110 setup for VOICEMAIL access to LINE - local PBX system Post by: giqcass on July 27, 2014, 01:23:21 pm Welcome to the forum.
Your question confuses me slightly. You said "pressing FLASH button, then *130" and later you say "our voicemail doesn't use */stars". When trouble shooting I often create a speed dial for testing purposes. In this case I would make an explicit speed dial that specified the line port. li(*130) Personally I use speed dial 1 for voicemail because it's the same on cellphones. Long press 1 on most cell phones to get voicemail. If I wanted to keep *130 and the speed dial worked I might put the following in my star code profile A. *130, Voicemail, call(li(*130)) An adjustment can be made to the DigitMap / OutboundCallRoute if your star code profile doesn't have the room. Title: Re: Obi110 setup for VOICEMAIL access to LINE - local PBX system Post by: searchformission on July 27, 2014, 03:35:20 pm I apologize for any confusion.
With my current system, I need to press the FLASH key/button on the phone before dialing "*130" to access the voicemail. The FLASH part is where it is tricky. Title: Re: Obi110 setup for VOICEMAIL access to LINE - local PBX system Post by: azrobert on July 27, 2014, 03:57:56 pm If I wanted to keep *130 and the speed dial worked I might put the following in my star code profile A. *130, Voicemail, call(li(*130)) giqcass, I believe you coded to Star Code correctly, but there is a bug in the firmware and it will fail. It appears the OBi ignores the last parenthesis, so it interprets the code as Call(li(*130). It then sends li(*130 to the Phone Port OutboundCallRoute where it fails. To prove this is what's happening place "{(@@.):sp2($2@192.168.1.199)}," at the beginning of the Phone Port OutboundCallRoute and check the Call History. I circumvented the bug by coding the Star Code like this: *130(<li(*130)>), Voicemail, call($Code) I have an OBi110 w/Build 2824 I don't know if the OBI20x has the same bug. Title: Re: Obi110 setup for VOICEMAIL access to LINE - local PBX system Post by: azrobert on July 27, 2014, 04:28:27 pm Try changing Physical Interfaces -> Phone Port
HookFlashHandling to: Send Hook Flash to PSTN Title: Re: Obi110 setup for VOICEMAIL access to LINE - local PBX system Post by: giqcass on July 27, 2014, 05:34:55 pm giqcass, I think that was discussed somewhere before however I forgot about it. I believe you coded to Star Code correctly, but there is a bug in the firmware and it will fail. Try changing Physical Interfaces -> Phone Port @searchformission HookFlashHandling to: Send Hook Flash to PSTN Let us know if that works for you. Title: Re: Obi110 setup for VOICEMAIL access to LINE - local PBX system Post by: searchformission on July 28, 2014, 05:26:42 am I didn't change anything besides this:
HookFlashHandling to: Send Hook Flash to PSTN Now, by pressing # to switch to the local PBX via LINE, and pressing FLASH (even tried with double FLASH), I was able to reach the auto-attendant. But still, not the voicemail yet. I will play around a little more and see what happens. At least, with this change, I got somewhere. For your information, my Obi110 is on the v2.8 hardware and v1.3.0 (Build: 2824) |