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 John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Caller ID on forward and manual transfer to cell phones using TAC of 9

Status
Not open for further replies.

LRB45

Programmer
Oct 5, 2005
157
US
Working with a 406V2 R5.0(15). The customer has several methods of forwarding numbers to mobile workers cellphones and wanted the originating caller ID to pass thru to the end user cellphone. So far I have created a separate short code of 8N;Dial; Nss and this has accomplished the task of passing caller id thru from originating caller as requested when the (8) is used for trunk access in each of the methods below
Method 1-Short code set as Feature: Dial; Number: 1318372XXXss . This method works fine when you transfer to the programmed short code internally
Method 2-User Forwarding Tab set to Unconditional; Number: 81318372XXXX This method also works
Method 3-Using TAC of 8 to manually transfer to cell phone also works

Ultimately they do not want to have to use 2 different access codes to accomplish this and instead want the same using just a (9)TAC.

They are on a Windstream PRI which the provider claims they are not blocking any numbers and we are free to send anything our PBX is programmed to send even if it is not in the block of assigned numbers on the PRI.

The questions is: Is it possible to use TAC 9 to both send the DID number of the extension calling(407-328-XXXX) on a standard outbound call but then also 'pass thru' the originating caller id on a forwarded or offsite transferred call?
So far have tried Short code of 9; Feature of Dial with a number of N407328Ess, Nss, Nsi & Ns407328Ess but none of thee work and are either rejected altogether by LEC or do not Provide the desired result.
 
can't remember if R5 has this already but in the newer releases there is a checkmark to "send original calling Party information" for twinned calls in the system - Mobility (twinning) tab
that way you don't need any shortcodes at all.

So when in doubt you could upgrade with an upgrade license to R8.1 and all twinning is included and free but make sure that you don't get screwed with licensing on other places. User licenses need preferred edition license to work etc.

Joe W.

FHandw, ACSS (SME), ACIS (SME)



Interrupt the silence only if you improve it by saying something, otherwise be quiet and everybody will be grateful.
 
Although the "send original calling party information" is an option in R5 they aren't using twinning feature right now so they would need to purchase the licenses for it and they have a large number of remote workers so that may get a bit pricey for them.
And the 406V2 only supports up to 6.1 so that would require a hardware upgrade. They've asked in the past if there was any reason to upgrade and it's always been "no" but if they can't get the original request working perhaps now is a good time.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top