November 28, 2021, 04:47:09 pm *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: [1]
  Print  
Author Topic: [bug]inbound line calls and auto attendant problem  (Read 455 times)
Josenet
Newbie
*
Posts: 4


« on: November 24, 2021, 05:00:47 am »

Hi,

I have my phone line connected to a obi110 and set Line Port InboundCallRoute to block telemarketers and anonymous calls like this {(Mblocked):aa1},{(11[27]|[23789]xx xxx xxx):ph},aa1 to redirect them to Auto attendant with a custom prompt configured with:
- OutboundCallRoute:   ""
- AnswerDelay:              0
- CallbackAnswerDelay: 0
- NumberOnNoInput:      ""

- Welcome:      %User1%
- InvalidPin:      &pause()
- EnterPin:        &pause()
- MenuTitle:      &pause()
- Menu:             &pause()
- PleaseWai:     &pause()
- EnterNumber: &pause()
- Bye:                &pause()
___________________________
The problem now is, after some time, inbound calls routed to the phone will wait more than the Line port RingDelay to ring the phone, not enough to answer it. The fix is to reboot the obi, then the Line port RingDelay is respected.

What can be the problem? Is this a known bug?

regards
Logged
drgeoff
Hero Member & Beta Tester
*****
Posts: 5507


« Reply #1 on: November 24, 2021, 06:22:32 am »

It may not address your issue but according to the syntax stipulated on page 193 of https://www.obitalk.com/info/documents/admin_guide/OBiDeviceAdminGuide.pdf that final aa1 in the InboundCallRoute should also be within {}.

Also, I'd be inclined to use empty fields instead of your two instances of "".

According to the description of RingDelay on page 151

"Delay in milliseconds after initial ring detected on
the LINE port before the device acts on the call (to
route it according to InboundCallRoute)."

the RingDelay has timed out before the OBi uses the InboundCallRoute to decide what to do with the call.
The calls which ring the phone are from
112
117
2xx xxx xxx
3xx xxx xxx
7xx xxx xxx
8xx xxx xxx
9xx xxx xxx

Note that those are 3 or 9 digit numbers.  What country is your OBi in?
« Last Edit: November 24, 2021, 06:46:18 am by drgeoff » Logged
Josenet
Newbie
*
Posts: 4


« Reply #2 on: November 24, 2021, 10:19:16 am »

It may not address your issue but according to the syntax stipulated on page 193 of https://www.obitalk.com/info/documents/admin_guide/OBiDeviceAdminGuide.pdf that final aa1 in the InboundCallRoute should also be within {}.
oops you're right, it can only be omitted if there is only one rule.

Also, I'd be inclined to use empty fields instead of your two instances of "".
Grin it was my way to tell it is empty

According to the description of RingDelay on page 151

"Delay in milliseconds after initial ring detected on
the LINE port before the device acts on the call (to
route it according to InboundCallRoute)."

the RingDelay has timed out before the OBi uses the InboundCallRoute to decide what to do with the call.
The phone will still ring, so the InboundCallRoute is used. But will ring only 1 or 2 times.

The calls which ring the phone are from
112
117
2xx xxx xxx
3xx xxx xxx
7xx xxx xxx
8xx xxx xxx
9xx xxx xxx

Note that those are 3 or 9 digit numbers.  What country is your OBi in?
It's correct, emergency: 112, forest protection: 117
I'm from Portugal.

regards
Logged
Josenet
Newbie
*
Posts: 4


« Reply #3 on: November 24, 2021, 01:33:16 pm »

This is syslog after reboot obi110,
Made 2 anonymous calls that are routed to aa1

The time from receiving "caller id (pcm_id: 1) received!" --> "fxo: cp proceeding":
- First call: 21:08:31 --> 21:08:34  (3 seconds)
- Second call: 21:09:43 --> 21:10:06 (23 seconds)

Code:
[reboot obi110]
[anonymous call routed to aa1]
Nov 24 21:08:30 192.168.1.100 [DAA]: FXO ring on
Nov 24 21:08:30 192.168.1.100 [0]Ring On
Nov 24 21:08:30 192.168.1.100 FXO:NewTermState:ringing
Nov 24 21:08:31 192.168.1.100 ------ caller id (pcm_id: 1) received! ------------
Nov 24 21:08:31 192.168.1.100 [0]DAA CND ,,,,,
Nov 24 21:08:31 192.168.1.100 [0]DAA CND ,,,,,
Nov 24 21:08:34 192.168.1.100 fxo: cp proceeding
Nov 24 21:08:34 192.168.1.100 [DAA]: FXO OFFHOOK
Nov 24 21:08:34 192.168.1.100 FXO:NewTermState:offhook
Nov 24 21:08:34 192.168.1.100 FXO:Stop Tone
Nov 24 21:08:34 192.168.1.100 [DAA] FXO ring off
Nov 24 21:09:00 192.168.1.100 [DAA]: FXO ONHOOK MONITOR
Nov 24 21:09:00 192.168.1.100 FXO:NewTermState:onhook
[anonymous call routed to aa1]
Nov 24 21:09:43 192.168.1.100 ------ caller id (pcm_id: 1) received! ------------
Nov 24 21:09:43 192.168.1.100 [0]DAA CND ,,,,,
Nov 24 21:09:43 192.168.1.100 [0]DAA CND ,,,,,
Nov 24 21:10:02 192.168.1.100 [DAA]: FXO ring on
Nov 24 21:10:02 192.168.1.100 [0]Ring On
Nov 24 21:10:02 192.168.1.100 FXO:NewTermState:ringing
Nov 24 21:10:06 192.168.1.100 fxo: cp proceeding
Nov 24 21:10:06 192.168.1.100 [DAA]: FXO OFFHOOK
Nov 24 21:10:06 192.168.1.100 FXO:NewTermState:offhook
Nov 24 21:10:06 192.168.1.100 FXO:Stop Tone
Nov 24 21:10:06 192.168.1.100 [DAA] FXO ring off
Nov 24 21:10:32 192.168.1.100 [DAA]: FXO ONHOOK MONITOR
Nov 24 21:10:32 192.168.1.100 FXO:NewTermState:onhook
Logged
Josenet
Newbie
*
Posts: 4


« Reply #4 on: November 25, 2021, 06:48:32 am »

Sorry for the multi posts, but I solved the problem.
Taken from Linksys_ATA_AG_v2_080716NC-LB_rev20080815.pdf

I set Line port:
DisconnectTonePattern: 425-10,620-30;10;(.5+.5)
ACImpedance: 220+(820||120 nF) and 220+(820||115 nF)
CallerIDDetectMethod: FSK(V.23)
RingThreshold: 13.50-16.50

I like my obi110 and it does the job well, but the team that made it, should have included a menu to choose the country and set the default settings accordingly to that country. This are very technical settings for the end user, and I know much more settings are incorrect for my country, that I have to deal if I have more problems.
 
« Last Edit: November 25, 2021, 06:51:01 am by Josenet » Logged
Pages: [1]
  Print  
 
Jump to:  

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

Advertisement
Advertisement