VoiceGuide IVR Software Main Page
Jump to content

Could Not Get Caller Id

Recommended Posts

I have DMV480A-2T1 board. I could not get the caller ID from it.

I tried in the PSTNDiag, and it does not show up the caller ID either. So I think it must be the phone company does not pass down the caller ID. But I called Verizon, they said they did. :(..

So, I tried to log a call with ISDNTRACE and see if the caller number is in it. I don't see it.

 

I attached the log file here. Can you take a look for me? Thanks.

I don't know where or which section the caller number should be though. Here is the piece that has the CALL PROCEEDING.

 

Thu Apr 30 18:16:10 2009

RX Frame: Time = 389.996

Command=1 SAPI=0x00

TEI=0x00

0x74 0x8e Information

PD=0x08 Dest=0 CR=0x0015

SETUP(0x05)

1: BEARER CAPABILITY(0x04)

2: IE Length(0x03)

3: 1------- Extension Bit

-00----- Coding Standard

---00000 Info. Transfer Cap.

4: 1------- Extension Bit

-00----- Transfer Mode

---10000 Info. Transfer Rate

5: 1------- Extension Bit

-01----- Layer 1 Indent

---00010 User Info. Layer 1

1: CHANNEL ID(0x18)

2: IE Length(0x03)

3: 1------- Extension Bit

-0------ Interface ID Present

--1----- Interface Type

---0---- Spare

----0--- Preferred/Exclusive

-----0-- D-Channel Indicator

------01 Info. Channel Sel.

3.2: 1------- Extension Bit

-00----- Coding Standard

---0---- Number Map

----0011 Channel/Map Element

4: 1------- Extension Bit

-0000001 Channel Number/Slot Map

1: NETWORK SPEC. FAC.(0x20)

2: IE Length(0x02)

3: 0x00 Length Of Network ID

1------- Parameterized/Binary

-1------ Expansion Bit

--1----- Feature/Service

---00010 MEGACOM 800

1: CALLED PARTY NUM(0x70)

2: IE Length(0x0b)

3: 1------- Extension Bit

-010---- Type of Number

----0001 Numbering plan ID

8662837255 Number Digit(s) --> this is called number, not caller number.

Hex Dump:

02 01 74 8e 08 02 00 15 05 04

03 80 90 a2 18 03 a1 83 81 20

02 00 e2 70 0b a1 38 36 36 32

38 33 37 32 35 36

 

Thu Apr 30 18:16:10 2009

TX Frame: Time = 390.0

Command=1 SAPI=0x00

TEI=0x00

0x01 0x76 Receive Ready

Hex Dump:

02 01 01 76

 

Thu Apr 30 18:16:12 2009

TX Frame: Time = 391.900

Response=0 SAPI=0x00

TEI=0x00

0x8e 0x76 Information

PD=0x08 Orig=1 CR=0x8015

CALL PROCEEDING(0x02)

1: CHANNEL ID(0x18)

2: IE Length(0x04)

3: 1------- Extension Bit

-1------ Interface ID Present

--1----- Interface Type

---0---- Spare

----1--- Preferred/Exclusive

-----0-- D-Channel Indicator

------01 Info. Channel Sel.

3.1: 1------- Extension Bit

-0000000 Interface Identifier

3.2: 1------- Extension Bit

-00----- Coding Standard

---0---- Number Map

----0011 Channel/Map Element

4: 1------- Extension Bit

-0000001 Channel Number/Slot Map

Hex Dump:

00 01 8e 76 08 02 80 15 02 18

04 e9 80 83 81

 

Thu Apr 30 18:16:12 2009

RX Frame: Time = 391.912

Response=0 SAPI=0x00

TEI=0x00

0x01 0x90 Receive Ready

Hex Dump:

00 01 01 90

 

Thu Apr 30 18:16:12 2009

TX Frame: Time = 392.0

Response=0 SAPI=0x00

TEI=0x00

0x90 0x76 Information

PD=0x08 Orig=1 CR=0x8015

CALL CONNECT(0x07)

Hex Dump:

00 01 90 76 08 02 80 15 07

 

Thu Apr 30 18:16:12 2009

RX Frame: Time = 392.12

Response=0 SAPI=0x00

TEI=0x00

0x01 0x92 Receive Ready

Hex Dump:

00 01 01 92

 

Thu Apr 30 18:16:12 2009

RX Frame: Time = 392.16

Command=1 SAPI=0x00

TEI=0x00

0x76 0x92 Information

PD=0x08 Dest=0 CR=0x0015

CALL CONNECT ACKNOWLEDGE(0x0f)

Hex Dump:

02 01 76 92 08 02 00 15 0f

test_04302009_18h15m42s.log

Share this post


Link to post

Trace shows no CallerID sent.

 

Have you show the trace to your Telco?

 

Telco should be able to quickly make their own ISDN traces on the line as well to confirm this as well.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×