Why the long delay before an incoming landline call rings the OBI110 phone port?

<< < (4/4)

hwittenb:
I tried it some more times this evening with the RingDelay set to 0 and the caller id seems to always display as long as you have no other activity in the Line Port incoming routing except routing to the phone (ph).  I guess with my first test where it didn't work there must have been something wrong with the test.

If I also have some other activity in the incoming routing like forking the call to another phone the caller id doesn't display on the phone.  Actually it did display when I was using CallCentric to send the call to my PSTN line, but it would not when I tried calling three other ways and it always displayed on an external display on the phone line so AT&T was sending it each time.

Novice:
I've set RingDelay to 0 and it has been working well for me.

ipse:
Quote from: Novice on January 01, 2013, 07:18:30 pm

I've set RingDelay to 0 and it has been working well for me.

Only with VoIP calls...for PSTN (at least in NA) the CallerID info is sent between the first and second ring:

http://what-when-how.com/voip/fsk-caller-id-on-pstn-voip/

You cannot set the delay to zero for PSTN is US or Canada. I tested this in Canada - even my phone connected directly to POTS does not get the CallerID info before the second ring.
VoIP is a different story.

Novice:
To clarify, with RingDelay set to 0, the phone started ringing immediately with no caller ID, but caller ID showed up after the second or third ring. Basically, my phone was behaving the same as if it wasn't connected to an Obihai at all, which is what I was trying to achieve.

However, it recently stopped working - the caller ID never shows up anymore for calls coming in on the PSTN line.
Any suggestions on how to fix this (for those who were actually able to get it to work).

The frustrating thing with my Obi is that even though I don't change any settings, things always seem to stop working properly.

ipse:
All I can tell you is that for true PSTN LINE, I have to set it to min 2800ms to register CallerID.
In my case, RingDelay=0 really means the system NEVER gets the CallerID info - verified with logs and with "Call Status" while it's ringing.
Based on what I wrote before about CallerID info being sent after the first ring, it makes sense.

Navigation

[0] Message Index

[*] Previous page