different ELU32 in one route?

[rfpup]

Hello to all,

I have to connect to different MD each at a different location. There is ethernet connection 1 Gb fibber between the locations. There are three ELU 32 at each MD. Do I need to create three routes with using cho parameter or I can create only one.
Thanks in advance

 

[whosrdaddy]

please try to search the forum before asking questions..

pointers can be found here thread806-775902

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!

 

[rfpup]

Thank you whosrdaddy.
The thread you suggested really helped me.
Is it possible for having call back,call parking and features like these from the extensions of one PBX to the extensions of the other PBX connected through ELU32?

 

[whosrdaddy]

here's an excerpt from ALEX :

[tt]
2.9 Network services
It is possible to execute network services both in pure H.323 private networks and in mixed H.323/ISDN private networks (scenarios with H.323/ISDN gateway nodes).

The procedure to request services is based both on ASB 501 04 Specific Protocol in UUI message and Information field, and on GFP (ISO QSIG). The aim of this twofold way of requesting some services is to assure interworking with existing ISDN tie lines: UUI assures interworking with previous ASB 501 04 releases, whilst GFP assures interworking with PABXes in the mixed H.323/ISDN scenarios mentioned above.
In case of a pure H.323 scenario, network services are only possible between ASB 501 04 systems and between ASB 501 04 and BusinessPhone systems.

The service information is included in H.225.0 messages by embedding Q.931 messages.
The same signalling procedures as in ISDN trunks are kept in H.323 trunks. Q.931 messages are embedded inside H.225.0 messages of the same message type, when possible.

The way some of the services (e.g., call diversion) are executed (in a proprietary way based either on UUI or on ISO QSIG) can be set in the destination configuration or, in some cases, can be chosen by means of the Application System Parameter PARNUM=223.

The following services make use of embedded UUI signalling:

Account code
Authorization code
Call Back
Call Deflection
Call Diversion
Call Extending
Call Offer
Called Party Number
Calling/Connected Line Identity
Calling/Connected Line Identity Restriction
Calling/Connected Name Identity
Customer Identity
Day/Night Service Notification
DNIS for ACD
FRL/TCM
Intrusion
Message Waiting Notification
Night Service Diversion
Priority Routing
Repeated Deflection
Rerouting
Transfer
Type of Party
Voice Mail facility
And these services are executed based on ISO QSIG standards:

Advice of Charge
Call Completion
Call Forwarding
Call Offer
Call Transfer
Calling/Connected Line Identity Restriction (only public number)
Calling/Connected Name Identity (without presentation rules)
Path replacement
Type of Party (through ISO common information)
[/tt]

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!

 

[rfpup]

Thank you whosrdaddy,
I really appreciate your help.
Is it possible using the same parameters suggested at thread thread806-775902 regarding MD routes for communicating to a BP compact through ELU32 - IPU ?

 

[whosrdaddy]

yes you can...

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!