CP 150 will not show OLI using Message Notification

[pecossunset]

I can't seem to get the CP-150 to show the OLI that I have entered into the DN for the CP. It is DN 299 and I have the 10 digit DID number so when it is calling they know it is the CP relaying a message to them.

I also notice that the CID is not passing through when the caller presses 7 to be transferred to the cell phone via the MB. Usually it will Pass Through the CID info.

 

[curlycord]

The CP does not act like a phone so OLI will not work.

For the cell phone what does show up?
Maybe a carrier issue.

=----(((((((((()----=
curlycord

http://www.curlycord.com

Toronto Canada

http://www.telcopc.ca

 

[jsaad]

do you have a PRI?

http://www.tgscorp.com

 

[Multimedium]

I can't seem to get the CP-150 to show the OLI that I have entered into the DN for the CP. It is DN 299 and I have the 10 digit DID number so when it is calling they know it is the CP relaying a message to them.

The CallPilot 150 has 8 channels. When it makes an Off-Premise Message Notification, it does so using any of its 8 channels.

The CallPilot Primary DN (in your case, 299) is mapped to the first channel. There are 7 other DNs (3 B1 DNs and 4 B2 DNs) that are mapped to the other channels. You need to program the OLI number for these 7 other DNs, too.

I also notice that the CID is not passing through when the caller presses 7 to be transferred to the cell phone via the MB.

I don't think there is much you can do.

Depending on the features offered by your telco and your setup, Outbound Transfer may be performed using the Link Transfer feature from the CO or the Conference feature from the system.

When the CallPilot uses the Link Transfer feature from the CO, it actually performs the following steps:
[ol 1]
[li]It sends a Link signal to the CO.[/li]
[li]It dials the destination number.[/li]
[li]It releases the call.[/li]
[/ol]

When the CallPilot uses the Conference feature from the system, it actually performs the following steps:
[ol 1]
[li]It puts the incoming call on hold.[/li]
[li]It grabs an outgoing line.[/li]
[li]It dials the destination number.[/li]
[li]It joins the incoming and the outgoing calls together using the Conference feature.[/li]
[/ol]

In both cases, the CallPilot is dialing the destination number. For the telco, the call originates from your line. Therefore, Caller ID will always be the one of your line.

 

[pecossunset]

Multimedium yes I did find the other DN's on the other channels and changed their OLI but it still says UNKNOWN when the call is coming in no CID is being sent. I COPIED the profile from 299 to all the other DN's to make sure. Still no CID being sent.

 

[allworxguy]

There are also B2 DN channels which you can't program.

If you remove OLI you should get the default CLID from the Telco.

Marv ccna

http://www.telemarv.ca

Sales, Installation & Service for Norstar, BCM & Allworx Serving Ottawa and Eastern Ontario since 1990

 

[Multimedium]

yes I did find the other DN's on the other channels and changed their OLI but it still says UNKNOWN when the call is coming in no CID is being sent.

I don't think there is much more you can do on your side.

Still, you can try to program the Off-Premise Message Notification feature or the Outbound Transfer feature so it calls one of your target lines.

If you see the Caller ID when the call comes in on one of your target lines, it means that there is it a carrier issue, as curlycord already mentioned. Basically, the cell phone company doesn't request the Caller ID from your local phone company.

If you don't see the Caller ID when the call comes in on one of your target lines, you will need to sort this out with your service provider. At this point, there are a lot of possibilities, but here are a few things that could be happening:
[ul]
[li]The CO may be configured to send the Caller ID based on the OLI number. However, the CO may not have a record for the OLI number you are providing.[/li]
[li]The CO may be configured to override the OLI number, the calling name, or both with its own data. However, the CO may not have a replacement name or number on file.[/li]
[/ul]

Anyway, your service provider should be able to track what is going on (and, hopefully, fix it).

There are also B2 DN channels which you can't program.

You're right: B2 DNs cannot be programmed independently. But, they share the same settings than their related B1 DN. Sorry for the confusion.