cuneyt2919
Technical User
Hi all,
We have a problem on making calls from MD110 to As5350. It says 2 route busy on DTS,
The same config is working fine on AS 5300.
The route parameters are as follows.
<RODAP:ROU=67;
ROUTE DATA
ROU TYPE VARC VARI VARO FILTER
67 SL60 H'00000350 H'15580000 H'46200010 NO
END
<ROCAP:ROU=67;
ROUTE CATEGORY DATA
ROU SEL TRM SERV NODG DIST DISL TRAF SIG BCAP
67 011000000000 7 0110000001 0 30 128 00151515 111100000031 001100
END
The destination parameter is
<RODRP:ROU=67;
EXTERNAL DESTINATION DATA
ROU DEST
67 8409
<roddpEST=8409;
EXTERNAL DESTINATION ROUTE DATA
DEST DRN ROU CHO CUST ADC TRC SRT NUMACK PRE
8409 67 2606100000000250 0 5 0
END
And the cisco engineer, debugged the problem and gave an advise..
****************************
cisco's Answer:
1) Modify PBX config: For the PBX attached to the AS5350, we need that the ISDN setup
arrives with no PI (progress indicator IE) to the AS5350. If TGW is 12.2, PI will
be understood when we pass it thru H225 IE. Otherwise (12.1(14) will not. So if setup
arrives with no PI IE and we configure in the AS5350 VoIP dial peer pointing to
aSnmpTest1 "tone ringback alert-no-pi", AS5350 should generate the ringback
tone locally. I think this is something that can be tested fast if PBX people
know how to change the config.
********************************************
HOw can we do this. Can someone help me
Regards.
We have a problem on making calls from MD110 to As5350. It says 2 route busy on DTS,
The same config is working fine on AS 5300.
The route parameters are as follows.
<RODAP:ROU=67;
ROUTE DATA
ROU TYPE VARC VARI VARO FILTER
67 SL60 H'00000350 H'15580000 H'46200010 NO
END
<ROCAP:ROU=67;
ROUTE CATEGORY DATA
ROU SEL TRM SERV NODG DIST DISL TRAF SIG BCAP
67 011000000000 7 0110000001 0 30 128 00151515 111100000031 001100
END
The destination parameter is
<RODRP:ROU=67;
EXTERNAL DESTINATION DATA
ROU DEST
67 8409
<roddpEST=8409;
EXTERNAL DESTINATION ROUTE DATA
DEST DRN ROU CHO CUST ADC TRC SRT NUMACK PRE
8409 67 2606100000000250 0 5 0
END
And the cisco engineer, debugged the problem and gave an advise..
****************************
cisco's Answer:
1) Modify PBX config: For the PBX attached to the AS5350, we need that the ISDN setup
arrives with no PI (progress indicator IE) to the AS5350. If TGW is 12.2, PI will
be understood when we pass it thru H225 IE. Otherwise (12.1(14) will not. So if setup
arrives with no PI IE and we configure in the AS5350 VoIP dial peer pointing to
aSnmpTest1 "tone ringback alert-no-pi", AS5350 should generate the ringback
tone locally. I think this is something that can be tested fast if PBX people
know how to change the config.
********************************************
HOw can we do this. Can someone help me
Regards.