a-number in transit

[TRIDENT100]

We have some nodes with VPN connection and central operator at one node. One of satellite node has Cisco Call Manager connected via ISDN QSIG. The satellite node acts like transit node. When calling from node (A) to Cisco via node (B) as transit SEND SETUP from transit node (B) to Cisco contain Calling Party Number (8 digits) and Calling Connected Number (5 digits). Cisco Call Manager can only use Calling Party Number as a-number. I know how to do NUTRI on received A-number and received connected number CNVTYP=2, but this do not affect when call is in transit. Since Cisco Call Manager to not have so good number conversion properties as MD110 I will change a-number in transit node so Calling Party Number field only contains 5 digits.
Is there a way to program the transit node (B) so its only sends 5 digits in Calling Party Number field?
SW: TSW SP2 in all nodes

 

[whosrdaddy]

yes this is possible:

use cnvtyp 1 and set ADC D24 to 1 (enhanced sent A number conversion) of your RODDI

/Daddy

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

 

[TRIDENT100]

thanks

Like this??
- calling party number from node a: 12345678
- called number to Cisco: 13499

Then at node b (transit)
nutri:entry=123,cnvtyp=1,numtyp=x,trc=3,tardst=13499;
roddi:dest=13499,adc=(d24=1)

??
Trident

 

[whosrdaddy]

yes indeed.

numtyp will normally be 0(unknown) or 2 (national)

/Daddy

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