[VoIP] Fun with Pat and Jane

Mark Rudholm mark at rudholm.com
Wed Feb 20 09:34:45 CST 2008


Steph Kerman wrote:
> It seems to me that in the past, certain OCCs I used via a 10xxxxx code 
> did not transmit CID.  I discovered this when I was unable to reach 
> people with Anonymous Call Rejection even though my line defaults to 
> pass CID and I had not prefixed the call with *67.   This might or might 
> not be true of the same carriers at this time.

Not sure.  I guess I could try a few, with billing to a credit
card.

> Have you tried your cellphone?  In the past I found that some 
> cellphones, although local, came through as "out of area".  But I have 
> not paid attention to this recently.

My cellphone service delivers proper CID.  It even correctly
supports *67.

> If calls you place from your coin line through ACTS arrive "unknown" why 
> doesn't that provide the test capability you're asking for?

It appears that calls requiring only the initial deposit
(local / zone 1&2 calls) are handled by my C.O. internally
and are not passed off to ACTS.  These calls arrive with
full CID (side note: the CNAM field is "PAYPHONE")

> In the past I also found that if I dialed 0+my own #, as though for a 
> credit card call, the call would go out to AT&T and come back in, 
> activating my Call Waiting, rather than returning a busy would happen if 
> I simply dialed my own #.  I think this occurred on the present 5E 
> rather than the 1AE that it replaced.   It's clear from this that once 
> 0+ was dialed, the local CO washed its hands of the matter and made no 
> attempt to correlate the called and calling #s.  This does not surprise 
> me.  Because of the delays required to release this call out to AT&T and 
> back to my local office, if I hung up after dialing this, I would get a 
> partial ring.

Yeah, I might try dialing 10xxxxx and 0+ to see if I can
find an arrangement that doesn't support CID.


More information about the VoIP mailing list