? on caller ID for customer that has Legend R7 and PRI

[mode1]

Have new customer that i recently cut over from T1 to PRI. Reason for this per AT&T was they needed PRI for caller ID to work. They have a secong site that is connected via point to point and DS1 cards. Apparently customer had SBC before the change over to AT&T and everything worked fine running on T1 circuit non ISDN not for sure just going on what I was told. Customer said when SBC became AT&T they installed new circuit and thats when they lost caller ID. I went to site and programmed main site for PRI and caller ID worked but only from main site not second site. Any help would be appreciated. Thanks in advance!

 

[TouchToneTommy]

From the Legend Netword Reference:

Caller ID

For 6.1 and later systems, Caller ID and Automatic Number Identification (ANI) information is conveyed across the private network when PRI tandem trunks are used to route the call and under the following conditions:

- The call is transferred using a DSS with one-touch transfer with automatic completion.
- The call is received on a PSTN trunk assigned to ring directly into a calling group with a non-local member.
- The call is received on a Personal Line and the principal user has activated Forward to a non-local extension and the Forward Delay option is set to one ring.
- The call is transferred to a user that has activated Forward to a non-local extension and the Forward Delay option is set to one ring.

For Release 6.0 systems, Remote Call Forwarding can be used in combination with Caller ID on a loop-start PSTN line connected to a networked system’s 800 LS-ID line/trunk module (loop-start ID delay must be on). To pass Caller ID information across the network when a call is transferred, set the Remote Call Forwarding Delay to one ring. Transfer of the call must be completed before the call is forwarded.

For 6.0 and later systems, Caller ID and ANI information is not conveyed across the private network under the following conditions:

- The call is routed over T-1-emulated tie trunks or analog (E&M) tie trunks.
- A call is manually transferred by a user or is transferred by an automated attendant.

So, how are they transferring the calls from Site A to Site B? Looks like it shoud go if they use a DSS button with Automatic Completion turned on. If they are answering, pressing Transfer, the extension number, and hanging up (or Transfer again), looks like it's not supposed to go.

 

[mode1]

Sorry I did not make myself clear read my thread and was not clear. What is actually happening is the second site dials 9 to access pri at main site at this point caller ID is not displayed to the called party.

 

[Dexman]

Just to make sure we understand the situation.

You have a customer with 2 offices. The main office has an R7 Legend and PRI/ISDN service.

The customer has a remote office and their telephone system is linked to the Legend via a point-to-point T1 circuit.

If someone in the main office places a call, the called party (if they have Caller ID) sees your customer's telephone number and name pop up on the Caller ID display.

If someone in the remote office places a call, the called party (if they have Caller ID) does NOT see your customer's telephone number of name on their Caller ID display.

How close am I

If it ain't broke, I haven't fixed it yet.

 

[mode1]

Exactly! Talked with customer today and confired that incoming DID calls show caller ID info but when they make a call the called party does not see caller ID info just unavailable or such

 

[TouchToneTommy]

This is going to be an issue with the new carrier.

Grab the manual from

http://support.avaya.com,

and in the Feature Reference, look at the section on PRI, and specifically "Number to Send"

[small]
Copy Telephone Number to Send

This option specifies whether or not the telephone number to send to the network for outgoing
calls made on PRI lines assigned to a B-channel group is copied from the PRI telephone number
assigned to that PRI line. Select the Copy Telephone Number to Send option when the telephone
number sent to the network should match the number received from the network, indicating the
number dialed by the outside caller. Select the Do Not Copy Telephone Number option either when
a telephone number to send is assigned to each PRI line in the B-channel group or when no
telephone number is to be sent to the network. (This can be used to block outgoing Caller ID,
system-wide.)



Telephone Number to Send

This option assigns the telephone number to send to the network when outgoing calls are made on
PRI lines. If the person being called subscribes to a PRI caller identification service, the number
indicates who is calling.


Station Identification-Automatic Number Identification (SID-ANI) as Calling Party Number.

Facility-based information is used by the network for sending the Calling Party Number. If the
SID-ANI option is programmed (and the service subscribed to), the system sends a system-wide
base number of up to 12 digits, of which the final digits (up to 4 digits) are replaced with the
number of the extension from which the call was made. For example, a call made from extension
7104 with a system-wide base number of 908-555-7000 sends the number 908-572-7104. For
facility-to-facility calls where there is no call-originating extension (for example, Remote Call
Forwarded calls), the system-wide base number is substituted. Trunk-to-trunk transfer, however,
results in a CPN that consists of a base number in which the last digits are replaced by the number
of the transferring extension.

In some instances, the system-wide base number is not sufficient to cover all extension numbers
in the system. For example, the base number might be 908-555-7000 and there might be a group
of extensions, 7000 through 7099, that correspond to telephone numbers from 908-555-7000 to
908-555-7099; there might be another group of extensions numbered 300 through 399 whose
telephone numbers are 908-555-0300 through 908-555-0399. In a case like this, there is no base
number that can cover all of the extensions so that the number sent is the correct number for the
extension.

The MERLIN MAGIX Integrated System’s PRI support for calling party identification extends to
MCI and local exchange (DMS-100) subscription services.

To specify that no telephone number is sent to the network, choose the Do Not Copy Telephone
Number programming option and use the Telephone Number to Send procedure to ensure that
telephone numbers are not assigned to each channel in the B-channel group. A network option to
block presentation of CPN is also available.

Copy Telephone Number to Send
Programmable by System Manager
Mode Hybrid/PBX, Key
Idle Condition Not required
Planning Form 3b, Incoming Trunks: DS1 Connectivity (100D, 100R INA, and
100 DCD module)
Factory Setting Do Not Copy
Valid Entries Do Not Copy, Copy
Inspect No
Copy Option No
Procedure Specify whether telephone number to send to network for outgoing
calls should be copied from line telephone number:
LinesTrunks?PRI?B ChannlGrp?Copy Number?
Dial group no.?Enter?Specify copy or no copy?Enter?
Back?Back?Back
Telephone Number to Send
Programmable by System Manager
Mode All
Idle Condition Not required
Planning Form 3b, Incoming Trunks: DS1 Connectivity (100D, 100R INA, and
100 DCD module)
Factory Setting No digits are assigned
Valid Entries Up to 12 digits (any combination of 0 to 9)
Inspect No
Copy Option No
Procedure Specify telephone number to send to network for outgoing calls on
PRI lines:
LinesTrunks?PRI?NumbrToSend?Specify type of no.?
Enter?Drop?Dial base no.?Enter? Dial line no.?Enter?
Drop?Dial telephone no. (up to 12 digits; 0–9)?Enter?Back?
Back



[/small]

 

[mode1]

Any thoughts if outbound caller ID should show to receiving party. Like I said earlier incoming caller ID shows on incoming calls at second location. Any help would be greatly appreciated.

 

[TouchToneTommy]

Yes - that is what I just referenced above - on a PRI, the carrier can send your main number, or can depend on you to send info on a "base number" + extension number, which would send the DID number of the person making the call. This is the CID that the called sees.

 

[mode1]

The second site is tied to main building via point to point setup as pri tandem trunk. With calls routing via UDP. Checked all settings on second site and number to send was set as main number for main building. When dialing out from second site number showed on caller ID is 0. Main site number to send is main number and everything works fine. Thanks in advance!