Server Edition and H.323 Trunk incoming group id

[hibroth]

Creating a H.323 trunk on the SE an outgoing line id group is requested but the incoming line id group is missing, how can we route (manipulating digits) an incoming call by line id?
It seems treated like a SCN trunk even if it's not...

 

[smokinjoe2938]

incoming call route if I understand you correctly

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.

 

[wfranklin]

hibroth

Hi man,

So, do you need route calls over your SCN? If yes, this is automatic.

Example:

System A: Extn 1000
System B: Extn 2000

1000 call for 2000. All process of the call dont neeed of "incoming call route"

[]´s

 

[biv343]

If you need to manipulate digits when calls come in via H323, QSIG or a SM line, you'll have to use shortcodes as ICR doesn't work for those three trunk types. If you receive 1234, but you want that to ring 2322, build a shortcode of 1234, feature dial extn, number 2322.

 

[smokinjoe2938]

yup your right key work here h.323

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.

 

[tlpeter]

A H.323 trunk only had an outgoing line group id.
Incoming is not needed as the call is send to the system anyway.

BAZINGA!

I'm not insane, my mother had me tested!

 

[hibroth]

I understand that the H.323 is treated as a SCN one (no Incoming Call Route) as per tlpeter assumption but this does not allow to manipulate digits (like the MSN/DDI setting does).
With the ICR you can manage the incoming call to users, shorts or any destination for that line group id only, what in the SE ?

 

[tlpeter]

What is what you want to do exactly?
On SCN and H.323 trunks there is no more incoming line group id for a couple of releases already as it is not needed.
You can use the trunk shortcodes or system shortcodes to route the call.



BAZINGA!

I'm not insane, my mother had me tested!