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

adding route to Qsig on HiPath 4000

Status
Not open for further replies.

ccmjgb

Vendor
Feb 1, 2011
317
US
Hi all,

Need some assistance on adding a route that will translate HiPath 4000 internal calls to station 4000 over to 4100 and route over q.sig to cisco - cisco needs to receive 4100. Please provide as much detail as possible (very much appreciated). If this can be accomplished in an easier fashion using Assistant - please provide those steps. Thank you in advance for your input!

ccmjgb
- Job 38:36
 
You are brave to be trying this using the Assistant !

HERE is a PDF document which might assist you.

I assume that you have the trunk up and running OK???

If that is so then all you need to do is as follows for local extension 4000 to be changed to 4100 on the Cisco.


ADD-WABE:4100,,,STN,N;
CHA-WABE:4100,'destination node number of cisco';

4100 now exists in the cisco land.

You can forward internal calls that ring 4000 to 4100 and that will work.

There are other ways
Setup a RICHT, LODR, LDAT & LDPLN
In the LODR you can specify to dial 4100 and in the LDPLN set it to 4000 so that when someone calls 4000 it will actually dial 4100 out on the cisco route but the forwarding is easier.



 
thank you sbcsu!

yes the q.sig trunks are in and have been working for some time... there are some existing virtual stations that currently route over the q.sig now.

I took a look at the .pdf (thank you for that!) but the only problem is that the cisco q.sig gateways are mgcp rather than h.323

question: when you mention: CHA-WABE:4100,'destination node number of cisco'; would the 'destination node number of cisco' equal the trunk group number assigned to the q.sig (in this case 10) or this something different

there are some hotlines set-up to route over through the q.sig (is this what you are referring to when you mentioned the 2nd option?)

--- need to ask another question ----

If i need to route all stations beginning with 4xxx over to 4100 via q.sig - what would be the way to go

 
Hi
Because you have the trunks already up and running you can ignore the mgcp/h323 as it is working for you.

If you DIS-WABE:STN;

you will see the DESTNO of each number on the HiPath.
If you already have numbers 'sent over' to the Cisco you will then see the Destination Node Number for the Cisco.

Just to clarify your question:
You want to send all 4XXX numbers to 4100 on the Cisco, so if someone dials for example 4444 on the HiPath that it goes to 4100 only on the Cisco or does it need to go to 4144 on the Cisco?

 
If you know of a number that is sent from HiPath to Cisco then look up that number on the HiPath as follows:

Example you know 6377 is being 'sent' to the Cisco from the HiPath
DIS-WABE:GEN,6377;

You should get back something like this:

------------------------------------------------------------------------------
| DIGIT INTERPRETATION VALID FOR ALL DIAL PLANS |
------------------------------------------------------------------------------
| | CALL PROGRESS STATE |NODE/DIGIT| RESERVED/CONVERT |
| CODE | 1 11111 11112 22| ANALYSIS | DNI/ADD-INFO |
| |0 12345 67890 12345 67890 12| RESULT | *=OWN NODE |
------------------------------------------------------------------------------
| 6377 |. .**** ***** **... ..... .*| STN | |
| | | |DESTNO 120 |
| | | |DNNO 1- 1-220 |
| | | |PDNNO 1- 1-220 |
------------------------------------------------------------------------------


Now that you know that the Cisco Node is DESTNO 120 (in this example) you can send a number to the Cisco as follows:

Add it in WABE first (if it is not already) added as follows:
ADD-WABE:6377,,,STN,N;

Send it to Cisco as follows:
CHA-WABE:6377,120;




If 6377 does not go anywhere you will see something like this:
------------------------------------------------------------------------------
| DIGIT INTERPRETATION VALID FOR ALL DIAL PLANS |
------------------------------------------------------------------------------
| | CALL PROGRESS STATE |NODE/DIGIT| RESERVED/CONVERT |
| CODE | 1 11111 11112 22| ANALYSIS | DNI/ADD-INFO |
| |0 12345 67890 12345 67890 12| RESULT | *=OWN NODE |
------------------------------------------------------------------------------
| 6377 |. .**** ***** **... ..... .*| STN | R |
| | | |DESTNO 0 |
| | | |DNNO 1- 1-800*|
------------------------------------------------------------------------------
The 'R' tells you that the number is added to WABE but is 'Reserved' and not going anywhere.
The * next to the DNNO is OWN NODE


 
Hi sbcsu, got it, thank you again!


now as far as sending all the 4XXX to Cisco, sorry let me clarify... all stations in 4XXX range would be sent over q.sig to Cisco and Cisco would receive and route all the extensions in this range: beginning with 4000 - 4999... so people dialing 4000 on HiPath would reach 4000 on Cisco etc

I'm sure that this can be done by following your note above but it might take a little while to get each one in... is there a way to get all in at a time?


by the way, do you know what (OP) means - next to my hash?
 
ADD-WABE:4000&&4999,,,STN,N;
CHA-WABE:4000&&4999,node number of cisco;

That will do them all in one go.

As far as I can tell it means 'original poster' - that is the person who asked the original question?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top