Search results for query: *

Could any one please advise what the difference is if any between the DIU T2 variant S30810-Q2226-X100 and S30810-Q2226-X200? This is to be fitted in a HiPath 4000 V6.

Is the DIUT2 a replacement for the obsolete CDG card. If so what are the enhancements of it over the CDG? Any info on it will be much appreciated regarding its connectivity.

I can only answer for a HiPath 4000 and the answer is YES.

You will not be able to display the caller's ID on analogue phones. If a name is added is AMO PERSI for an analogue phone then only when it originates a call to an Optipoint/Optiset will the name be displayed on the destination phone. It doesn't matter what type of SLMA card the extension is...

Further to my previous comment, that is why you can't see the station using Assistant because it's not configured. Add the station using Assistant if you are more familiar with that than using Comwin. Incidentally if you dial 2901 you will get a number unobtainable tone indicating that the...

Hi JNZY111 2901 has not yet been configured as an extension. The R in the WABE output means that the number has been RESERVED to be used as a station. You would first need to create the extension using AMO's SBCSU for a digital station or SCSU for analogue to assign it a port number. Once...

Could you verify what 2901 is configured as and show the output using the commands below. DIS-WABE:TYPE=GEN,CD=2901; DIS-WABE:TYPE=GEN,CD=2901,DPLN=0&&15;

Think the AMO is CTIME

AMO-CTIME, CP1, CTHLDREC Default is 300 secs

If this is a CAS circuit then it will be configured using AMO-TACSU; If you DIS-BUEND; this will display all the trunk groups configured in the system.

Use AMO TDCSU dis-tdcsu

Please read details below. This has caused V6 systems to reload. “Leap second handling” on SUSE/NOVELL Enterprise Linux (SLES11) based Large Converged products Message Body: SEN LC Products based on SUSE/NOVELL Enterprise Linux (SLES11) can be affected by “leap second handling”. There is...

It could be that the destination side is rejecting the call for some unknown reason. Don't know why given that you're able to route a call succesfully between the 2 systems. A wireshark trace would give you more visibility of what is going on and which side is rejecting the transfer. This would...

Could you try adding TSCS to COT 101 and L3AR to COP 1

The KNMAT entries are OK.

Have you checked AMO-KNMAT entries?

Do you have TTT in COS 57?

Pleased to hear that the problem is now hopefully resolved and as previously stated it would appear that the network provider was at fault. Thanks for the update.

If you're de-activating channels then this will be the case. If you de-activate channels 22 & 23 for example, then these have been disabled on the HiPath but they're not de-activated by Telco and will attempt to route calls over them.

Yes, example: DEA-DSSU:OFFTYPE=DI,TYPE=BCHAN,PEN1=1-1-1-1,BCHL=22; This would de-ctivate channel 22 on link 1-1-1-1. Do the same for channel 23.