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

B Number conversion on internal dialing 2

Status
Not open for further replies.

summerdike

Instructor
Oct 24, 2003
217
EU
I manage MD110/TSW (BC13).
I want to facilitate users on different (80) locations (in one MD110) to dial the same number (for ex. 44444.

Dialing 4444 must result in the ringing of different extensions (B numbers;groups/extensions) depending on where 4444 is dialed or who is dialing 4444.


Possible? How?

______________________________
Fictitious Destination Table containing Fictitious Route Choices....

 
just a suggestion:
make 44444 as a coacc and then use cust and empty corg with rernum to the difference b numbers.
 
Mundus,
Can you state sequence of commands.

I don't see where the cust parameter comes into the story.

As mentioned before, alle traffic stays , preferably, internal.

______________________________
Fictitious Destination Table containing Fictitious Route Choices....

 
sorry for my late respons !
a short/brief description:
1. assign a common oacc with nansi:numtyp oc/od and opcoi NB! you can only have one coacc in the exchange, in your case 44444.
2. assign some "dummy" oacc (just for routing purchase) with nansi:numtyp oc/od and opcts:corg=x,oacc="first dummy",calt=3(and maybe also with calt 1, 2 and 7+rou),CUST=Y.
3. opadc:corg=x,rernum="answer position" for CUST Y users when they call 44444.
4. assign CUST Y to the users of this Call origin group answer position with kscuc, excuc or gedic.
 
Mundus,

In my case COACC is already assigned to a common operator number.
And even when the COACC was not occupied, I want several services (not only 44444 but at least one more) to be reachable by a single number on all locations.


______________________________
Fictitious Destination Table containing Fictitious Route Choices....

 
What you can try is to create a dummy route with dest 4444, then create different customer numbers for different callers. The pre should be the desired number (extension etc.
It looks something like this: (adc is left out in the ex.)

DEST DRN ROU CHO CUST TRC SRT NUMACK PRE

4444 2 4 5 0 44448787
2 1 4 5 0 44442018
2 2 4 5 0 44442033

The calling number should have a customer number accordingly.8787 is adummy number. Maybe this helps?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top