Outbound calls showing restricted insread of DID

[rfreil]

We have 2 locations and this only happens when a person logs in at the respective remote location. If they are logged into their default phone everything works fine "DID shows up on the phone dialed " instead of restricted.

I think it might be a simple setting that I am just missing.

Any and all help would be appreciated.

[thiel2]

I had to look up your posting history to try and figure out that perhaps your system is an IP Office? More background information on what you are using is always helpful

When the user is logged in at his home location, unless your ARS tables are specifically sending something else as outbound caller ID, the system will automatically use the number from the Incoming Call Route as the outgoing Caller ID.

When the user is logged in at the remote location, that Incoming Call Route doesn't exist on that system, thus it sends the main number, or no number at all.

Create User Rights specifically for each user that will travel from home site to remote site.
Name them exactly the same at both sites. At the remote site, make a User Short Code of 9N / Dial / Ns0001234567 / ARS where the 000134567 is their own DID number.

[rfreil]

Thanks for the instructions.... I'm having trouble getting it to work.
Could you send some screenshots with your instructions. It would be much appreciated

Both the remote site and the home site are showing ARS 50 Main. But when I look at Line Group ID I am showing from the IPO Home Config options for 17, ARS50, 0.
When I look at Line Group ID I am showing from the IPO Remote Config options for 18, ARS50, 0.

Potentially a side note but....I used to have the option to add them "remote and home site users" to a new incoming call route... the sites are separate but I could see a remote site user in the destination list while logged onto the home site IPO. That is no longer the case for some reason. I have to login to the remote site IPO.... Its like before the sites used to be linked at least from a incoming call route perspective.

Thanks again for you guidance.
Let me know if you need anything else from me

[rfreil]

thiel2

With your original instructions and some knowledge gathering on my end I was able to resolve the issue. I could not have done it without your help.

Thanks