Conversion of the Received B-Number type (ISDN)

[RomeoAlfa]

We would like to conversion of the Recevied B-Number type from public to any private, but doesn't work.

It's very important, that external public ISDN call can come in successfully to an extension, when this extension has blocked direct indialling characteristics for traffic from public exchange.
(Extension has Service Category: SERV=xxxx0xxxxxxxx, D5=0.)


ROUTE CATEGORY DATA
ROU SEL TRM SERV NODG DIST DISL TRAF SIG BCAP
79 7110000000000010 5 3100030001 0 30 128 00151515 111110000031 111100
ROU TYPE VARC VARI VARO FILTER
79 SL60 H'00000212 H'00000000 H'26410000 NO

number_conversion_initiate -entry 8529 -conversiontype 0 -numbertype 0 -route 79 -newtype 5

We test it with TSE 5.0 SP5 HF1.

Does anyone has experience with conversion of the received B-Number type solution?

Any suggestion ?

BR: Romeo

 

[whosrdaddy]

This wont work as the PBX will check the trunk parameters and not the numbertype of the call.
Using a loop may work.

/Daddy

-----------------------------------------------------
Helping people is my job...

 

[RomeoAlfa]

Hi Daddy,

I tested it with Q-SIG loop, but didn't work.

BR: Romeo

 

[snor]

Hi Romeo,

why don`t you try it in the way like Alexander (Sandokan) on Mitel Support Forum told you ?

// You change the B-number, but the check is done on the caller's category. Can't work this way.
// Why those tricks. If this user shall not get calls from a certain route you may play with the TCD category.

P.S.
It is only possible to set direct in dialling to YES or NO.
If you want that only a few external numbers should reach your extension with direct indialling, and the rest of external numbers should go to your Operator, etc. you should think about a solution with an external application, which is able to handle a "black/white" list

regards,
Norbert

 

[RomeoAlfa]

Hi Norbert,

this answer from Sandokan is mine.
I want, that all external number reachs our extension with direct indialling.
I tried use a loop after incoming ISDN public (with protocol Q-SIG and H.323),
but didn't help.
What is your opinion an external application (SeC, Envox,etc)?
Can connect this external application the incoming public ISDN call to an extension,
if this extension are block direct indialling?

BR:
Romeo

 

[snor]

Hi Romeo,

If all external number should reach your Extension with direct indialling, then the simplest way is to allow direct indialling
and set SERV D5=1 for your extensions.

What is the reason (background), why "direct indialling" is blocked in your extensions SERV-Parameter ?

best regards,
Norbert

 

[RomeoAlfa]

Hi Norbert,

it's a big network with a lots of ISDN public, Q-SIG and DPNSS routes.

Only few extension has SERV D5=1 and allow direct indialling from public ISDN,
but all extension allow calling from DPNSS and Q-SIG.

This will be a new ISDN GSM route and should call all extension. The supplier
can't pass Q-SIG protocol, can give up only public ISDN.

BR:

Romeo

 

[parnum]

Hi

As advised above, open all the ext cat for ddi incoming and use TCD matrix to restrict and allow different routes/connections. Do not allow calls from the public route to connect to the ext cat in TCD where they should not have incoming public ddi, but allow for other routes. This is the function of TCD.

best parnum

 

[RomeoAlfa]

Hi Parnum,

Thanks for advice.

BR: Romeo