G3si and ANI (caller ID)

[HBPS]

We have a new Definity G3si and we are trying to get both alpha/numeric caller ID. Our service provider says that they can't do it because they have NorTel equipment and we have Lucent (whatever). I have contacted even CLEC's that are using the Lucent ES5500 and they say that they can only send numeric. So here is my question, is their anybody getting both alpha and numeric ANI using NI 2 protocol on the G3si? Please help my CEO is on my back!!

 

[jforti]

Guy,

I am facing the same problem.
Do you know whether the Lucent PBX has a owner caller ID ?

Thanks,

Juliano Forti

 

[cclausen]

I assume you mean ANI? You would have to have ISDN PRI to get this information. I have several questions. If you have ISDN. Do the phones have displays. If they do, you will get ANI if it is sent. As of R8.4 the ISDN PRI meets the Bellcore specs and can now receive Name and Number. On the trunk form there is a send name field. If you set it yes and the LEC has the PRI setup correctly you can send and receive name and number. NOTE: If you set send name on the trunk form to yes, now dial an outbound call. If you get waved off (reorder tone), turn the send name bcak to no. This tells you that the LEC does no have the PRI setup properly. The above only applies to the PRI. If you have trunks using an ICLID trunk board the rules are different.

 

[jforti]

MR,

I have phone with display and I am using ISDN PRI. I am receiving the number , but the name doesn't. I have a voice compression system in the middle from two PBX (Definity) from Marconi Communications. The name is yes to send, but I have been analyzed the frames in the voice compression system (SE) when the frames come, and the calling party can not be recognized. I don't know if the Lucent use the codeset to ETSI out of standard. Do you what codeset from Lucent is ?
And, when the SE doesn't recognize the calling party, it sends a request to PBX to send the calling party again separately, number by number.

For example :

00 000000-- Sapi = 0
------0- C/R: Command
-------0 Extension Bit = with extension
01 0000000- TEI = 0
-------1 Extension Bit = no extension
00 0000000- N(S) = 0
-------0 I-Frame
00 0000000- N(R) = 0
-------0 P/F = 0
08 00001000 ProtocolDiscriminator DSS1
02 00000010 Length of CallReference = 2
30 0------- CallRef-Flag: Origination Side
-0110000 CallReference = 12393
69 01101001 (CallReference)
05 00000101 MSG-Type: SETUP
04 00000100 I-Element: Bearer
03 00000011 Length = 3
90 1------- Extension Bit = no extension
-00----- Coding Standard: CCITT
---10000 Information Transfer Capability: 3.1 kHz Audio
90 1------- Extension Bit = no extension
-00----- Transfer Mode: circuit mode
---10000 Information Transfer Rate: 64 kbit/s
A3 1------- Extension Bit = no extension
-01----- Layer 1 Identifier
---00011 User Info Layer 1 Protocol: G.711 A-Law
18 00011000 I-Element: Channel Identification
03 00000011 Length = 3
A1 1------- Extension Bit = no extension
-0------ Interface Identifier present: interface implicitly identified
--1----- Interface Type: other interface
---0---- Spare
----0--- Preferred/Exclusive: indicated channel is preferred
-----0-- D-channel indicator: is not the D-channel
------01 Information Channel Selection = as indicated in following octets
83 1------- Extension Bit = no extension
-00----- Coding Standard: CCITT
---0---- Number/Map: Channel by Number
----0011 Channel Type/Map Element Typ: B-Channel Units
81 1------- Extension Bit = no extension
-0000001 Channel number: 1
1E 00011110 I-Element: Progress Indicator
02 00000010 Length = 2
81 1------- Extension Bit = no extension
-00----- Coding Standard: CCITT
---0---- Spare
----0001 Location: private network serving local user
83 1------- Extension Bit = no extension
-0000011 Progress Description: origination address is non-ISDN
6C 01101100 I-Element: Calling Party Number
05 00000101 Length = 5
A1 1------- Extension Bit = no extension
-010---- Type of Number: national
----0001 Numbering Plan: ISDN/Telephony
31 0------- Spare
-0110001 Number digit: 1
35 0------- Spare
-0110101 Number digit: 5
35 0------- Spare
-0110101 Number digit: 5
37 0------- Spare
-0110111 Number digit: 7
70 01110000 I-Element: Called Party Number
01 00000001 Length = 1
80 1------- Extension Bit = no extension
-000---- Type of Number: unknown
----0000 Numbering Plan: unknown
97 10010111 I-Element: unknown
28 00101000 (not decoded)
0D 00001101 (not decoded)
54 01010100 (not decoded)
65 01100101 (not decoded)
6C 01101100 (not decoded)
65 01100101 (not decoded)
63 01100011 (not decoded)
6F 01101111 (not decoded)
6D 01101101 (not decoded)
20 00100000 (not decoded)
2D 00101101 (not decoded)
20 00100000 (not decoded)
54 01010100 (not decoded)
6F 01101111 (not decoded)
63 01100011 (not decoded)


Thanks

jforti

 

[Jolagues]

I have spoken with our bell provider and have confirmed PAC BEll in California does not have the capability to send name and number over pri lines so the default is number you can have it changed to name but you will lose the number.

 

[HBPS]

Thanks for your comments. Our carrier tested the Definity that thay have in their corp office. It worked, however on another Definity it did not. Well I guess we'll just have to wait and see. Thanks Again

 

[wilsontec]

when you want to connect definity and nortel you must purchase isdn-pri Qsig protocol and speical feature (name tranfer to norton equipment)

 

[jforti]

Wilsontec,

So, I can't connect the Nortel PBX with Lucent through of ETSI protocol for example, only with Q.Sig.
Because that the DCS from Lucent is proprietary on ETSI ?
Am I sure ?

Thanks,

jforti