Transfer the original Caller ID info to a External Phone No. 4

[Trustel]

I have a customer that wants to be able to send incoming caller ID info via a manual Call Transfer to an external number. So in other words; 'Bob' calls the company for service. The service dispatcher answers the call and then transfers it to a field technician. The field tech sees Bob's CID Info on his phone. Is the IPO capable of this and if so how do I set it up?

Currently the field tech sees the caller ID of the service dispatcher that transferred the call.

The IPOv2 is running on 8.1 (81), Essential.

All calls in and out are via a PRI.

Thank you for your help.

 

[Telecomboy]

You could probably accomplish this with twinning. You would then set-up a H323 user for each field tech. Set-up twinning with their cell phone info for each user and set twinning to send original called party info out. Then, transfer the call to the new extension and it will twin to the cell phone with the caller id info.

 

[intrigrant]

I don't think this ISDN feature is supported in IP Office.
The reason for me to believe that is that on a SIEMENS system I can call a person on his DDI, he/she answers and transfer me to a collegue whih has another DDI number, on my cell phone the number changes accordingly.
Never seen that happen on a IP Office.

 

[Okkie26]

Yes, the IP Office can do this, But most likely, your service provider will block this.

 

[Greybeard191]

possible with some PRI providers.

you must:

1, use twinning
2. under system/twinning, make sure that the "send original calling party information for mobile twinning" is checked
3. and this is the kicker... PRI vendor must support/permit CPS generated CLID and not restrict in any way what number is sent. Often this is restricted to maintain the integrity of E911 calls. Different central office switches call the feature of blocking "weird" outgoing CLID by different names... call screening table is one name. Whatever that feature is, it must be turned off. If it's left on, the incoming CLID will be sent as outgoing CLID (parts 1 and 2), but the CO will strip those digits and replace with some other legit number on the PRI, probably the pilot number. SO PRI vendors require a E911 waiver of some kind to be signed before they will remove this feature. Allstream in Canada does, as an example.

GB

 

[TouchToneTommy]

If your service provider does not block you from sending out caller id of numbers that don't belong to your incoming block, you could create a new ARS table, where the telephone numbers entries have SSi after the N (such as Code: 1N; / Telephone Number: 1NSSi / Feature Dial3K1 / Line Group ID: 0). New shortcode of 8N / Dial / N / 51:Forward Route, and teach the service dispatcher to transfer "Bob" to the field tech by pressing Transfer, pressing 8, dialing the field tech's cell number, and Complete when the call begins ringing.

 

[Trustel]

Thank you all for the feedback. I have talked with the carrier and they say they will transfer any digits that I send them even if its not a valid number on the IPO, so I think I'm good there. I think Telecomboy's suggestion using twinning will be a good place to start. I'll let you all know how it turns out.

 

[intrigrant]

I think it may be done with another approach.
Lets say you have a common shortcode like 9N;/N/Dial/LineID
Now make a short code like 8N;/NSS/Dial/LineID and transfer a call not using the 9 but using the 8 as a line access code.
It works on my SIP trunk I installed today. Also when a user forwards the phone to her/his mobile number using the 8 as a access number will forward the callers number as the CLI.
If you use the 8 on normal outgoing calls then "+extension number" is shown as the CLI.

 

[Trustel]

So I tried both the solutions. Intrigrant's Short codes and dialing an 8 when transferring a call solution works well. The customer has used it for a day and it's working without any problems.

I also tried Telecomboy's solution to set up an H323 user with Twinning for the person you want to Transfer the caller to. I have not been able to make this work. After some initial programming I was able to dial the H323 three digit extension from an office phone and it would ring the cell phone the H323 ext. was Twinned to. However after I went in and changed the Twinned number to a different cell phone all I would get is a busy signal. So I put the original number back in and it still rang busy even after a reboot. At that point I had to stop testing. I may pursue this farther when I have time but since the short code option works and the customer is happy it is a low priority. If anyone gets this scenario to work please let me know.

Thanks again for everyone's input.