Re: [hylafax-users] [hylafax-devel] Re: Distinctive ring & cid

["Network" <network@network.shacknet.nu>]

> At 04:56 PM 6/21/01 -0400, Network wrote:
> >> cid
> >> >data whereas HylaFAX will not display this data via distinctive ring
> >> dial-in's.
> >>
> >> RingsBeforeAnswer is set to what?
> >>
> >
> >RingsBeforeAnswer:      4
>
> Watch it work when you set RingsBeforeAnswer: 2

We have tried this 2 ring setting in the past while attempting to solve the
other distinctive ring issue... (picking up both on the primary and secondary
numbers).  The reason for not bringing this current issue up at that time, was
an effort to not confuse myself or others following this thread -and- because
the primary number displayed cid-data and the distinctive ring number didn't, I
was almost sure it was telco.
-
Lastly on this 2-ring setting suggestion; during an incoming call via the
primary number Hylafax does not answer (goody) and the cid-data is logged
faithfully.  Why would/should it be different for the secondary number?  In any
case, setting RingsBeforeAnswer:    2 doesn't help this current situation.

>
> See: http://bugs.hylafax.org/bugzilla/show_bug.cgi?id=139

QUOTE; "1) it uses Campbell McKilligan's rings-cid-passing.patch to allow
faxgetty to
remember the CNID data throughout subsequent rings that do not present CNID data
2) it documents in the cid manpage the sometimes-tricky fact that CNID data
isn't always presented before the first ring"

FACT; local telco (verizon) provides cid-data after the first ring  -or-  during
the second ring.  :)
-
That patch allows faxgeety to *remember*.  Whereas in this situation, there is
nothing to remember because the cid-data is not seen at all *only when* the
incoming call is via the distinctive ring number.
-
Whats even more baffling is the same issue is present with cu -l cuaa1 (no
cid-data seen upon incoming calls via distinctive ring)  which leads me to
believe its still the phone co but, the working cid-box thorws that Idea out the
window.
-
Only other thing i can think of is some kind of protocol difference that this
box can see but yet hylafax nor cu -l is able to see.
I really hope I'm not misreading something again.  :\

Thoughts?




____________________ HylaFAX(tm) Users Mailing List _______________________
 To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null