Can't Get Call Waiting to Work on Vonage Line Connected to LINE Port

<< < (2/3) > >>

jimates:
You have to "hook/flash" twice to access the second call on the line port.

Hook/flash only once is handled locally by the Obi. One time will connect you to the default SP.

You can change it so that hook/flash always goes to the PSTN, but then you won't have call waiting on your SP line, unless after the change a double hook/flash may work for the SP. I am not sure but RonR knows.

Physical Interfaces -> Phone -> HookFlashHandling

Glenk:
Jimates,

Hookflashing once, twice, 10 times, etc produces the same result in my case.

I got hold of a phone line splitter and connected it at the Vonage box with one leg going to the OBI LINE port and the other going to a telephone handset.  With the phone port configured for “Send Hook Flash to PSTN”.  A call was received via the Vonage box and answered on the handset connected to the OBI PHONE port.  A second incoming call produced a call waiting tone on the phone , a single hook flash put the first call on hold (per the Vonage box’s display).  There was a hum in the hand set and no voice communication with the second caller. 

At that point, I picked up the receiver of the phone that was connected to the Vonage box via the splitter.  On that phone, I had voice communication with the line that is supposed to be active (not on hold per the Vonage box’s display).

It appears that the Vonage box is doing what it’s supposed to.  The problem seems to be with the OBI110 since the Vonage box is presenting voice to the OBI LINE port but it's not getting through to the attached phone.  Once the first call is placed on hold, communication between the Vonage box and the OBI ceases.  I've tried more than one phone on the OBI.

RonR:
Glenk,

The problem may not be limited to the LINE Port/Vonage:


http://www.obitalk.com/forum/index.php?topic=2896.0

http://www.obitalk.com/forum/index.php?topic=243.msg18943#msg18943

Glenk:
I've been trying to run syslog.  Here is what happens:

-          Opened the OBi's web page (http://192.168.10.3)

-          Navigated to System Management/Device Admin/Syslog and filled in             the 'Server' parameter with 192.168.10.3 and left the 'Port' parameter at 514 .

-          In the Voice Services settings, changed the 'X_SipDebugOption' parameter to 'Log All Messages.'

-          Downloaded syslogd.zip to folder C:\syslog.

-          Unzipped syslogd.zip to the C:\syslog folder which created a file called syslogd.exe.

-          Opened a command prompt window and ran syslogd.exe from C:\syslog (C:\syslog>syslogd.exe).  A file called log.txt was created in the C:\syslog folder.  The file had the following entry “Syslogd is listening to port# 514:”

-          Doing anything with the phone connected to the OBI’s PHONE port, does not register anything in the command prompt window.

What am I missing?

RonR:
Quote from: Glenk on March 30, 2012, 12:58:45 pm

-          Navigated to System Management/Device Admin/Syslog and filled in             the 'Server' parameter with 192.168.10.3 and left the 'Port' parameter at 514 .


Set:

System Management -> Device Admin ->Syslog -> Server : (IP address of the PC running syslogd.exe)

Navigation

[0] Message Index

[#] Next page

[*] Previous page