[Asterisk-Dev] NTT FSK - Japanese Caller ID

Isamar Maia isamar at isamarmaia.org
Wed Nov 26 10:04:47 MST 2003


Hi Folks,

I'm trying to play with the CallerID stuff to figure out
how to solve the NTT FSK caller id problem in *.

The information I got so far was that this protocol also named JCLIP,
is the data that it transports(1):

http://resource.intel.com/telecom/support/releases/winnt/sr60cpci/onldoc/htmlfiles/vocprgdw/voxpg-h3.htm

,this(2):

"For CLIP or JCLIP, the Caller ID information is received from the
service provider before the first ring. Set the ring event in the
application to occur on or after the first ring. The ring event indicates
reception of the CLIP Caller ID information from the CO."

And this(3):
"Caller ID information is available for the call from the moment the ring
event is generated (if the ring event is set to occur on or after the
second ring (CLASS, ACLIP) or set to occur on or after the first ring
(CLIP, JCLIP)) until either of the following occurs:

- If the call is answered (the application channel goes off-hook), the
  Caller ID information is available to the application until the call is
  disconnected (the application channel goes on-hook).

- If the call is not answered (the application channel remains on-hook),
  the Caller ID information is available to the application until rings are no
  longer received from the Central Office (signaled by ring off event, if
  enabled)."


And finally this:
http://www.ntt-east.co.jp/gisanshi/analog/edit5e.pdf (english)
And this:
http://www.ntt-east.co.jp/gisanshi/analog/siryo97/pdf/1997_1_3.pdf(Japanese)

The last one shows how  the information is organized and passed.

What is the standard used in US? Anybody has its specification to send to
me? So, I could compare both...

I am printing the value of 'b' in the callerid.c but the values in binary/
hex, dec or whatever doesn't look like anything familiar described
in the specification.

ff -- 255
fc -- 252
fc -- 252
fc -- 252
ee -- 238
fc -- 252
fc -- 252
fc -- 252
fc -- 252
fe -- 254

I was wondering if it is not a problem in the low-level frequence
settings...

Anybody could gimme a hand?

Isamar








More information about the asterisk-dev mailing list