Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Ring Group CID Problem

Status
Not open for further replies.

snd1234

IS-IT--Management
Mar 10, 2006
123
US
BCM450 r6 w/ Aug12 SU patch
DTM w/ PRI
Autoattendant DN=472
Skillset #1 DN=580

We have two different ring groups in our organization we manually trigger with a schedule services button on a handset.

Ring Group #1 controls line 361 & 362 w/ DN600 as the control set for the lines. NIGHT SERVICE=Rings to DN472 (AA); OFF=Rings to DN600
Ring Group #2 controls line 368 w/ DN511 as the control set. NIGHT SERVICE=Rings to DN580 (Skillset #1); OFF=Rings to DN472

When either ring group is ON/enabled (in night mode) the number portion of the caller ID of the incoming call disappears and is replaced by a question mark in BCM monitor. The name portion of the caller ID is fine. Only affects calls on the lines being controlled by the ring group.

When either ring group is OFF/disabled both the name & number portion of CID pass fine.

What I actually see in the monitor is this.

1. 5551234567 - ? - DNIS:5553217654 (to start)
2. ? - JOHN DOE - DNIS:5553217654 (1 second later)

This only happens on lines I put into ring groups and only when the ring group service is enabled manually on the phone.
 
If you have POT's lines then you will never get caller id when using service modes since it answers right away when caller ID signal is sent between first and second ring.
Since you have PRI I am assuming service mode still answers too quickly and that id is sent during the first ring.
Doing F811 would be the only way to see the ID.

Other can confirm or correct me if this is true even with PRI.






=----(((((((((()----=
curlycord
 
PRI should be sending the caller ID info instantly as part of the initial call.
The provider might be setting up the call prior to doing the CNAM name lookup and then later sending the name in a subsequent packet. The BCM might be misinterpreting that update packet as completely new call display info.

It could be the type of switch setting for your PRI.
Call your provider and ask what kind of network switch they use.
You can trace the PRI messages using BCM monitor UIP screen. You have to figure out what bus your DTM interface is using and then click on PRI enable the monitoring on that bus to watch the PRI messages. It runs for 15 minutes at a time.
If you do this during the day it can get a bit confusing with all the other calls going through, Would suggest you do it during a quiet time so you can just watch the results of a single call at a time.
If the name is coming after the initial setup packet then it might be overwriting the phone number.
When I look at mine the initial setup message coming in has both the number and the name of the caller so all that info is presented right away.

You can check what kind of switch protocol your PRI is configured for in Configuration->Resources->Telephony Resources Click on your DTM PRI module. In the Trunk Module Parameters tab you will see the protocol.
For example mine is set to DMS100 (We use Telus who used the Nortel DMS100 switching equipment in their office)
I'm guessing if the protocol you have selected there does not match your carrier, the if it didn't outright fail, it could result in issues like that.



 
Thanks guys, here's some more info.

1. Caller ID works. But when a line is controlled by a ring group (service enabled) the CID comes in showing only the phone number and "?" for the caller's name but w/i 1 second (as viewed in BCM Monitor) it changes to "?" for the number and the correct name. So CID is reaching the system. It's just not complete.

First Ring: 5551234567 - ? - DNIS:5553217654
Afterwards: ? - JOHN DOE - DNIS:5553217654

2. I upgraded from BCM400 r4 and it didn't do this. Same PRI circuit, same DTM card. So I thinking it's not the circuit.

3. When those three target lines are on "night" service they have the problem. But the other target lines pass CID fine at the same time.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top