December 16, 2018, 06:57:27 pm *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: [1] 2
  Print  
Author Topic: OBI212 Bug Releasing Line Port ?  (Read 6207 times)
dboling
Jr. Member
**
Posts: 74



« on: September 17, 2018, 10:14:47 am »

OBI212
HardwareVersion: 1.4
SoftwareVersion: 3.2.2 (Build: 5898EX)

This has to do with OBI212 setting Physical Interfaces>LINE Port>InboundCallRoute:

When using the setting ph,pp(obi202_number) receiving calls on the Line Port seems to work exactly as it should.

However when using the following settings the OBI212 will not release the Line Port. In one instance I had to unplug the OBI212 after both sides of the call had been hung up for 30 minutes.

SP4 SIP is set for Callcentric.
OBI212 IP 192.168.3.60
OBI202 IP 192.168.3.61

This setting is pointed at my OBI202
sp4(0@192.168.3.61:5083)

This setting is pointed at my NY Callcentric number. call treatments send direct to voicemail.
sp4(free_callcentric_number)

Both these setting connect the call however the OBI212 seems to be loosing it's mind during the call.

I do have a test Voicemail saved from callcentric that you can hear what the OBI212 is doing.

Since this forums attachments are broken, I'll link to it from my server.
The actual voicemail was about 10 seconds.

http://209.160.64.39/vm_2018-09-17_13_40_28.mp3
  

« Last Edit: September 18, 2018, 02:28:35 am by dboling » Logged

-Diane
dboling
Jr. Member
**
Posts: 74



« Reply #1 on: September 17, 2018, 03:44:19 pm »

This is starting to drive me crazy.
I've gotten complaints of people calling the landline and getting dead air. Having to call 5 times before the OBI212 will ring the phone.

I answered one landline call that was transferred to my OBI202 by the OBI212 via pp(). I transferred the call back to the OBI212 which nobody answered. However when the person called back and the call logs for the OBI212 was showing it was the same call I had transferred from the OBI202.

I'm wondering if the OBI212 is defective. I thought it could be Verizon, but even Verizon isn't that bad.
Logged

-Diane
dboling
Jr. Member
**
Posts: 74



« Reply #2 on: September 19, 2018, 04:38:07 pm »

Nobody has any idea how to fix this problem ?

Amazon sent out a replacement OBI212 today, OBI also pushed out new firmware for the OBI212 and the new OBI212 has the exact same problem.

Current firmware and revision:

HardwareVersion 1.4
SoftwareVersion 3.2.2 (Build: 5921EX)

Logged

-Diane
dboling
Jr. Member
**
Posts: 74



« Reply #3 on: September 22, 2018, 09:19:22 am »

On Thurs 9/20 I submitted a ticket with OBI on this issue.
Logged

-Diane
dboling
Jr. Member
**
Posts: 74



« Reply #4 on: September 27, 2018, 04:05:34 am »

Has anybody ever had OBIHAI Premium support get back to them after filing a ticket request ?
Logged

-Diane
azrobert
Hero Member & Beta Tester
*****
Posts: 3659


« Reply #5 on: September 27, 2018, 10:35:32 am »

Try this:

OBi202
ITSP D SIP -> X_DiscoverPublicAddress: checked

SP4 Service -> X_RegisterEnable: unchecked

OBi212
ITSP D SIP -> X_DiscoverPublicAddress: checked

If this fixes your problem and you need to receive inbound from CC, there is a solution.
Logged
dboling
Jr. Member
**
Posts: 74



« Reply #6 on: September 27, 2018, 12:05:07 pm »

Try this:

OBi202
ITSP D SIP -> X_DiscoverPublicAddress: checked

SP4 Service -> X_RegisterEnable: unchecked

OBi212
ITSP D SIP -> X_DiscoverPublicAddress: checked

If this fixes your problem and you need to receive inbound from CC, there is a solution.


I tried changing the OBI212 ITSP D SIP -> X_DiscoverPublicAddress: checked and unchecked several times, But
this isn't going to fix the OBI212 ability to forward the landline (correctly) on no-answer to callcentric.
The OBI212 is the problem, not the OBI202.

This is what I sent using OBI support page.

I did leave you a voicemail about this issue, I'll try and explain it here.

OBI212
HardwareVersion 1.4
SoftwareVersion 3.2.2 (Build: 5921EX)
IP Addr: 192.168.3.60
SP1: GV
SP2: GV
SP3: none
SP4: Callcentric

## The issue is regarding calls coming in to the OBI212 on the Line Port via Verizon landline.

## These settings seem to work as it should.

Physical Interfaces>LINE Port>InboundCallRoute: ph
Physical Interfaces>LINE Port>InboundCallRoute: ph,pp(my_obi202_num)
Physical Interfaces>LINE Port>InboundCallRoute: pp(my_obi202_num)


## These setting do not work correctly.

Physical Interfaces>LINE Port>InboundCallRoute: ph,sp4(0@192.168.3.61:5083)
Physical Interfaces>LINE Port>InboundCallRoute: sp4(0@192.168.3.61:5083)
Physical Interfaces>LINE Port>InboundCallRoute: sp4(callcentric_ph_num_Vmail)
Physical Interfaces>LINE Port>InboundCallRoute: sp2(calcentric_ph_num_Vmail)
Physical Interfaces>LINE Port>CallForwardOnNoAnswerNumber: sp4(callcentric_ph_num_Vmail)
Physical Interfaces>LINE Port>CallForwardOnNoAnswerNumber: sp2(callcentric_ph_num_Vmail)

The calls do get routed correctly and I'm able to answer when routed to my OBI202(192.168.3.61). When routed to my callcentric voicemail it also answers the call.

The problem is about 10-20 seconds into the call the OBI212 starts sending weird phone tones to the receiving party. It doesn't matter if the caller or callee  hangs up, the OBI212 continues to send phone tones and holds the Line port off hook. One time the OBI212 held the Line Port off hook for 40 minutes and I had to unplug the OBI212 in order to release the line.

Here is a saved callcentric voicemail were you can hear what the OBI212 is doing http://209.160.64.39/vm_2018-09-17_13_40_28.mp3 . The voicemail represents exactly what is't doing with all these settings.

Amazon replaced the OBI212 as we thought it was defective unit, however both OBI212s exhibited the same symptoms.

First OBI212
HardwareVersion: 1.4
SoftwareVersion: 3.2.2 (Build: 5898EX)
« Last Edit: September 27, 2018, 01:31:56 pm by dboling » Logged

-Diane
dboling
Jr. Member
**
Posts: 74



« Reply #7 on: September 28, 2018, 06:37:52 am »

Try this:

OBi202
ITSP D SIP -> X_DiscoverPublicAddress: checked

SP4 Service -> X_RegisterEnable: unchecked

OBi212
ITSP D SIP -> X_DiscoverPublicAddress: checked

If this fixes your problem and you need to receive inbound from CC, there is a solution.


I didn't have sp3 on the OBI212 configured so I setup sp3 as callcentric and used your suggested settings.

OBI212
ITSP C SIP -> X_DiscoverPublicAddress: checked
SP3 Service -> X_RegisterEnable: unchecked  

Physical Interfaces>LINE Port>InboundCallRoute: pp(my_obi202_num)
Physical Interfaces>LINE Port>CallForwardOnNoAnswerEnable: Checked
Physical Interfaces>LINE Port>CallForwardOnNoAnswerNumber: sp3(callcentric_ph_num_Vmail)
Physical Interfaces>LINE Port>CallForwardOnNoAnswerRingCount: 2

The voice mail on callcentric was 71 secs, about 10 seconds after recording voicemail and hanging up the tones started. I guess it starts with a reorder tone.
The line port on the OBI212 continues off hook and connection to Callcentric remains long after caller hangs up and continues until I delete the call within call status or unplug the OBI212.

This is the syslog error I got for the OBI212.
Sep 28 07:45:21 obi212  Send() error 104
Sep 28 07:45:21 obi212  HTTPD: SendHeader Failed
« Last Edit: September 30, 2018, 10:04:32 am by dboling » Logged

-Diane
dboling
Jr. Member
**
Posts: 74



« Reply #8 on: October 04, 2018, 12:44:11 pm »

We'll 2 weeks since I filed a ticket with OBIHAI and no contact from OBIHAI's Premium support.

They did push another update out to the OBI212 today (SoftwareVersion 3.2.2 (Build: 5932EX)). I have no idea what the new version fixes or if it even deals with the issues of forwarding landline calls.
 
Logged

-Diane
dboling
Jr. Member
**
Posts: 74



« Reply #9 on: October 05, 2018, 09:50:43 am »

Checked to see if firmware SoftwareVersion 3.2.2 (Build: 5932EX) addressed the OBI212 PSTN line forwarding issue, IT DID NOT!!!

It would be nice to see OBIHAI/POLYCOM take more interest in their customer support as they have advertised "One Year Premium Customer Support with the purchase of their device". They even sell additional Premium Customer Support on the side.




Logged

-Diane
dboling
Jr. Member
**
Posts: 74



« Reply #10 on: October 08, 2018, 06:46:48 am »

It took a very long time, but I think I found the issue. This web page explains the issue very well http://www.sandman.com/cpcbull.html .

I just had Verizon out testing the line, the tech said the line passed his test. However he didn't know what open loop disconnect was, he called the Guy that runs the CO and he knew exactly what CPC disconnect was. He confirmed that I was not getting the disconnect signal and that the card at CO needed to be change out from POTS line to a Loop Disconnect. He said I need to call billing to get it provisioned so he could make the change.

It would be nice if OBI added another disconnect option for the line port that could detect the reorder,howling type signals you get when CPC signal isn't present.



« Last Edit: October 08, 2018, 06:51:54 am by dboling » Logged

-Diane
drgeoff
Hero Member & Beta Tester
*****
Posts: 3859


« Reply #11 on: October 08, 2018, 09:24:50 am »

The OBi110 Line Port settings has the options DetectDisconnectTone and DisconnectTonePattern.  Are those not provided on an OBi212?
Logged
dboling
Jr. Member
**
Posts: 74



« Reply #12 on: October 08, 2018, 09:33:30 am »

The OBi110 Line Port settings has the options DetectDisconnectTone and DisconnectTonePattern.  Are those not provided on an OBi212?

DetectDisconnectTone   checked
DisconnectTonePattern   480-30,620-30;10;(.25+.25)

I tried changing the pattern, but no luck.

Been on hold with Verizon the last 3 1/2 hours to try and get the pots card changed over.

They said that the card should be changed by 3 pm tomorrow.

Whats weird is when Verizon runs a line test I get these readings in my syslog:

Oct  8 12:49:09 obi212  OB:<==CRLF 1
Oct  8 12:49:11 obi212  [DAA]: CPC DETECTED ( 3820 ms, 4 v ) #012
Oct  8 12:49:11 obi212  [DAA]: FXO ONHOOK MONITOR
Oct  8 12:49:13 obi212  [DAA]: FXO ONHOOK MONITOR
Oct  8 12:49:14 obi212  [DAA]: POLARITY REVERSAL (-4 V)#012
Oct  8 12:49:15 obi212  [DAA]: CPC DETECTED ( 3460 ms, 5 v ) #012
Oct  8 12:49:15 obi212  [DAA]: FXO ONHOOK MONITOR
Oct  8 12:49:18 obi212  [DAA]: CPC DETECTED ( 2460 ms, 20 v ) #012
Oct  8 12:49:18 obi212  [DAA]: FXO ONHOOK MONITOR
Oct  8 12:49:19 obi212  [DAA]: CPC DETECTED ( 540 ms, 6 v ) #012
Oct  8 12:49:19 obi212  [DAA]: FXO ONHOOK MONITOR
Oct  8 12:49:22 obi212  [DAA]: CPC DETECTED ( 2460 ms, 41 v ) #012
Oct  8 12:49:22 obi212  [DAA]: FXO ONHOOK MONITOR
Oct  8 12:49:23 obi212  [DAA]: CPC DETECTED ( 860 ms, 5 v ) #012
Oct  8 12:49:23 obi212  [DAA]: FXO ONHOOK MONITOR
Oct  8 12:49:27 obi212  [DAA]: CPC DETECTED ( 2521 ms, 78 v ) #012
Oct  8 12:49:27 obi212  [DAA]: FXO ONHOOK MONITOR
Oct  8 12:49:27 obi212  [DAA]: POLARITY REVERSAL (61 V)#012
Oct  8 12:49:28 obi212  [DAA]: CPC DETECTED ( 620 ms, 4 v ) #012
Oct  8 12:49:28 obi212  [DAA]: FXO ONHOOK MONITOR
Oct  8 12:49:28 obi212  [DAA]: POLARITY REVERSAL (-7 V)#012
Oct  8 12:49:31 obi212  [DAA]: CPC DETECTED ( 2451 ms, 71 v ) #012
Oct  8 12:49:31 obi212  [DAA]: FXO ONHOOK MONITOR
Oct  8 12:49:35 obi212  [DAA]: CPC DETECTED ( 3010 ms, 74 v ) #012
Oct  8 12:49:35 obi212  [DAA]: FXO ONHOOK MONITOR
Oct  8 12:49:35 obi212  [DAA]: POLARITY REVERSAL (74 V)#012
Oct  8 12:49:36 obi212  [DAA]: POLARITY REVERSAL (-4 V)#012
Oct  8 12:49:36 obi212  [DAA]: CPC DETECTED ( 580 ms, 5 v ) #012
Oct  8 12:49:36 obi212  [DAA]: FXO ONHOOK MONITOR
Oct  8 12:49:37 obi212  [DAA]: CPC DETECTED ( 720 ms, 18 v ) #012
Oct  8 12:49:37 obi212  [DAA]: FXO ONHOOK MONITOR
Oct  8 12:49:38 obi212  [DAA]: CPC DETECTED ( 687 ms, 4 v ) #012
Oct  8 12:49:38 obi212  [DAA]: FXO ONHOOK MONITOR
Oct  8 12:49:40 obi212  [DAA]: POLARITY REVERSAL (31 V)#012
Oct  8 12:49:40 obi212  [DAA]: CPC DETECTED ( 711 ms, 27 v ) #012
Oct  8 12:49:40 obi212  [DAA]: FXO ONHOOK MONITOR
Oct  8 12:49:41 obi212  [DAA]: POLARITY REVERSAL (-4 V)#012
Oct  8 12:49:41 obi212  [DAA]: CPC DETECTED ( 651 ms, 4 v ) #012
Oct  8 12:49:41 obi212  [DAA]: FXO ONHOOK MONITOR
Oct  8 12:49:48 obi212  [DAA]: FXO ONHOOK MONITOR
Oct  8 12:49:49 obi212  [DAA]: CPC DETECTED ( 4120 ms, 54 v ) #012
Oct  8 12:49:49 obi212  [DAA]: FXO ONHOOK MONITOR
Oct  8 12:49:50 obi212  [DAA]: POLARITY REVERSAL (55 V)#012
Oct  8 12:50:37 obi202  OB==>CRLFCRLF
« Last Edit: October 08, 2018, 10:16:42 am by dboling » Logged

-Diane
dboling
Jr. Member
**
Posts: 74



« Reply #13 on: October 10, 2018, 10:22:01 am »

Getting Verizon to swap the POTS card to an Open Loop Disconnect card at the CO is proving to be a headache.

They say that residential customers don't need an open loop disconnect.   
Logged

-Diane
drgeoff
Hero Member & Beta Tester
*****
Posts: 3859


« Reply #14 on: October 10, 2018, 10:55:44 am »

You should be getting a Disconnect Tone from the telco.  Is the telco not providing that or is the OBi212 not detecting it or is the OBi212 not acting on the detetced tone?
Logged
dboling
Jr. Member
**
Posts: 74



« Reply #15 on: October 10, 2018, 11:23:00 am »

You should be getting a Disconnect Tone from the telco.  Is the telco not providing that or is the OBi212 not detecting it or is the OBi212 not acting on the detetced tone?

At this point I'm not sure what I'm getting.
I see a disconnect just before LI gets forwarded to callcentric voicemail, in the voicemail I get tones, but I think that's hardware generated from the OBI212. I have my syslog set to level 7 and here is the log for a single call. I don't see any tones being registered in the log. I know no other way to look for tones.

Oct 10 14:16:03 obi212  [DAA]: FXO ring on
Oct 10 14:16:07 obi212  CCTL:NewCallOn Term 12[0] ->,500100000
Oct 10 14:16:08 obi212  PNNCACHE:pnn found NS in cache:364371a3:12520
Oct 10 14:16:08 obi202  PP:WebrtcIncomingCall=0
Oct 10 14:16:08 obi212  SIP_TS:Retx, next in 100
Oct 10 14:16:08 obi202  ++++ bcllr=0; caller=52012000
Oct 10 14:16:08 obi202  CCTL:NewCallOn Term 1[0] ->,
Oct 10 14:16:08 obi202  fxst_ccapi_new_call: 52012000->52012000 name Sandy
Oct 10 14:16:08 obi202  [SLIC] CID to deliver: 'Sandy' 52012000
Oct 10 14:16:29 obi212  [DAA]: FXO ONHOOK MONITOR
Oct 10 14:16:29 obi212  CCTL:CFWD-->10[3]:1631488000
Oct 10 14:16:29 obi202  RTP:Del Channel
Oct 10 14:16:29 obi212  RTP:Del Channel
Oct 10 14:16:29 obi212  RTP:DtmfTxMtd:1(1),0
Oct 10 14:16:29 obi212  [DAA]: FXO OFFHOOK
Oct 10 14:16:29 obi212  [DAA]: detecting disconnect tone, reinit: 1
Oct 10 14:16:29 obi212  RTP:Start->cc0bc027:58248(80 160);0;0;0:0:0;0(45)
Oct 10 14:16:29 obi212  [DAA] FXO ring off
Oct 10 14:16:43 obi212  OB==>CRLFCRLF
Oct 10 14:16:43 obi212  OB:<==CRLF
Oct 10 14:16:43 obi212  OB:<==CRLF 1
Oct 10 14:16:43 obi212  OB==>CRLFCRLF
Oct 10 14:16:43 obi212  OB:<==CRLF
Oct 10 14:16:43 obi212  OB:<==CRLF 1
Oct 10 14:16:46 obi212  RTP:Del Channel
Oct 10 14:16:46 obi212  [DAA]: FXO ONHOOK MONITOR
Logged

-Diane
drgeoff
Hero Member & Beta Tester
*****
Posts: 3859


« Reply #16 on: October 10, 2018, 12:34:54 pm »

Unplug the phone from your OBi212 and connect it to the telco line. Make a call. Ask the called party (possibly yourself on your cellphone) to hangup. Do you hear the disconnect tone?

If yes, record the tone as a digital recording. Recording device microphone against phone earpiece will be good enough. Import recording into eg Audacity and try to analyse its spectral components.
« Last Edit: October 10, 2018, 12:40:19 pm by drgeoff » Logged
azrobert
Hero Member & Beta Tester
*****
Posts: 3659


« Reply #17 on: October 10, 2018, 07:28:59 pm »

I always thought the disconnect tone was only used when the phone is kept off hook. I tested this with my OBi110 and OBi200. My OBi110 is connected to PSTN and I route inbound calls only to the OBi200, I don't ring the OBi110 phone port.

My 1st test was without any changes. I called PSTN and answered with the OBi200 and then hung up the calling phone. About 15 seconds later I heard the disconnect tone on the OBi200 and a couple seconds after that I was disconnected from PSTN and then heard dial tone. This is how it should work.

My second test I disabled all the Disconnect Detection options on the OBi110 Line definition. After I hung up the calling phone I didn't hear the disconnect tone, but got a busy signal. The phone would not disconnect from PSTN. I have DECT phones connected directly to PSTN and the display showed "Line Busy". After I hung up the OBi200 phone I immediately got disconnected, the "Line Busy" disappeared. I took the OBi200 phone off hook again and had dial tone.

I think you should disconnect after hanging up even if there is a problem with the disconnect tone or detection. I assume it works correctly when your phone is connected directly to PSTN. Does it work when the phone is connected to the OBi212 and you don't route calls to the OBi202?

Edit:

I recommend turning off Silence Detection. I once was on a call to Dell tech support and they put me on hold. I got disconnected because of this setting.
« Last Edit: October 10, 2018, 07:42:16 pm by azrobert » Logged
dboling
Jr. Member
**
Posts: 74



« Reply #18 on: October 11, 2018, 06:14:37 am »

Verizon Phone Configuration:

DSL and Dialtone only (Bare Minimum).
Verizon line is only meant to fullfill DSL miniums.
GV1 and GV2 is forwarded to Verizon line as well as being forward to SP1 and SP2.
Allowed Outbound calling: 911, Verizon, and toll free numbers.
 

Device configuration:

OBI202
SP1: GV1
SP2: GV2
SP3: GV3
SP4: callcentric
IP: 192.168.3.61

OBI212
SP1: GV1
SP2: GV2
SP3: N/A
SP4: callcentric
LI: Verizon
IP: 192.168.3.60

Since I don't use Verizon for outbound call, this issue only concerns Verizon inbound calls.

OBI212(LI): InboundCallRoute pp(500100000)
Hang up OBI202: PASSED
Hang up OBI212(LI) PASSED


OBI212(LI): InboundCallRoute sp4(0@192.168.3.61)
Hang up OBI202: OBI212(LI) stays off hook until I kill the connection.

Hang up OBI212(LI): OBI212(LI) stays off hook and OBI212 syslog generates a single tone followed by more tones that syslog does not log. I presume these tones are from Verizon. I did record the call using the OBI202 record function. To disconnect I still have to kill the connection.

SYSLOG: obi212  [LI0]  ---- S/W TONE ON (level: default) : , @ 1882521 ----

Recorded Audio File: http://209.160.64.39/record.au
« Last Edit: October 11, 2018, 07:54:55 am by dboling » Logged

-Diane
dboling
Jr. Member
**
Posts: 74



« Reply #19 on: October 11, 2018, 12:17:12 pm »

After 5 tickets with Verizon, no luck getting the pots card swapped for an open loop disconnect card.
I'm giving it one last try with Verizon Executive Relations.

So even if I don't get the card swapped over, the pots card should be sending a Disconnect Tone Pattern and Verizon should be able to give me the correct pattern ? 
Logged

-Diane
Pages: [1] 2
  Print  
 
Jump to:  

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