OBI212 Bug Releasing Line Port ?

<< < (2/5) > >>

azrobert:
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.

dboling:
Quote from: azrobert 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.



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)

dboling:
Quote from: azrobert 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.



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

dboling:
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.
 

dboling:
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.




Navigation

[0] Message Index

[#] Next page

[*] Previous page