Outgoing caller ID on PRI

[JazzWizzard]

Hi everyone,

I just wanted to confirm: say I have a PRI and my provider is handing me 4 digits, a DID like 514-445-5555 and an incoming call route with a destination of extn 5555. When the user of that extension will make an outgoing call, will their caller ID be displayed correctly at the other end, meaning 514-445-5555?

I trying to avoid programming an insane amount of ARS and short codes since I have about 20 branches, different NXX and a setup looking like this:

Thank you!

 

[Telecomboy]

Have them send 10-digits. Easiest way to do it.

 

[critchey]

As Telecomboy pointed out easiest solution is to have provider send 10 digits. If for reason they won't the next best solution is to not send the callerID via the ARS table but send it via the 9N shortcode instead. It saves you having to enter the callerID for all the ARS shortcodes you only have to enter it for each user's 9N shortcode... still a lot of work though if you have a ton of users.

The truth is just an excuse for lack of imagination.

 

[JazzWizzard]

Alright, so to recap, if we go with the 9N shortcode route; I imagine we would have to imput something like Ns5144455555 in the Telephone Number field for the specific user?

Now, since we have more than 1 NXX, could we do something like Ns514445E or Ns515776E, etc.. and have this configured in user rights? Would that automatically imput the extention and would the complete number pushed to the PRI?

Thanks again, guys!

 

[TouchToneTommy]

How about if you put all 10 digits in the Incoming Call Route, even though the provider is only sending 4 digits. Now sending 9N to 50:Main and not specifying the outgoing caller ID should automatically send their DID as outgoing CID

 

[critchey]

Oh ya duh TTT is right of course. Despite the provider only sending 4 digits the IPO will best match so if you put all 10 digits it will still work.

The truth is just an excuse for lack of imagination.

 

[JazzWizzard]

Thank you so much gentlemen!