Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
CRC on Bc9 Q-sig
- Thread starter Nibbio
- Start date
whosrdaddy
Vendor
there's no command, the TLU76 will follow automatically what is set on the other side...
-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!
-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!
Hi
you can do a SACOS
SACOS:UNIT=SLP60,LIM=xx,ADDR=909,SECTOR=REL,DATA=yy;
yy as the following values
01 = "AUTOMATIC CRC-4" MODE !
11 = "NO CRC-4" MODE !
31 = "ALWAYS CRC-4" MODE !
In BC9, it is valid for all TLU76/1 or TLU64 using SLP60 signalling scheme.
So if you have QSIG and Public line in the same LIM, the CRC4 procedure will be applied for both
In BC12, you can separate, DSS1, Public and QSIG.
you can do a SACOS
SACOS:UNIT=SLP60,LIM=xx,ADDR=909,SECTOR=REL,DATA=yy;
yy as the following values
01 = "AUTOMATIC CRC-4" MODE !
11 = "NO CRC-4" MODE !
31 = "ALWAYS CRC-4" MODE !
In BC9, it is valid for all TLU76/1 or TLU64 using SLP60 signalling scheme.
So if you have QSIG and Public line in the same LIM, the CRC4 procedure will be applied for both
In BC12, you can separate, DSS1, Public and QSIG.
fouesnant!
What's the idea to change CRC, if MD does it automatically? In my experience, the problem is ALWAYS on the other side, PSTN or whatever.....
Consider carefully why you want to change the CRC manually before doing anything!
The sacos command is not relevant to use in a PBX which is connected to a PSTN, it does NOT help (except the PSTN is not an old pre-war version)!!!
What's the idea to change CRC, if MD does it automatically? In my experience, the problem is ALWAYS on the other side, PSTN or whatever.....
Consider carefully why you want to change the CRC manually before doing anything!
The sacos command is not relevant to use in a PBX which is connected to a PSTN, it does NOT help (except the PSTN is not an old pre-war version)!!!
Hi fcpli
The idea of changing CRC4 was that our PSTN does not support automatic CRC4 detection and that it must be set to no CRC4.
Secondary, we have operators as customer that request to set CRC4 to no automatic detection.
I don't know if it is old pre-war releases PSTN, or if it is the way they choose to implement the connexion, but it is like that.
In other hand, why is there the possibility to modify CRC4 in the MD110 SW?
Can anybody tell me the real use of CRC4 ?
The idea of changing CRC4 was that our PSTN does not support automatic CRC4 detection and that it must be set to no CRC4.
Secondary, we have operators as customer that request to set CRC4 to no automatic detection.
I don't know if it is old pre-war releases PSTN, or if it is the way they choose to implement the connexion, but it is like that.
In other hand, why is there the possibility to modify CRC4 in the MD110 SW?
Can anybody tell me the real use of CRC4 ?
Hi, all,
I think, fouesnant is right, in a way. MD110 is small AXE. In a real AXE we have dtidp / dtidc commands:
CRC=0 - no CRC4;
CRC=1 - sorry, I can't understand it
;
CRC=2 - yes CRC4;
CRC=3 - automatic adjustment for CRC4.
Use of CRC4 - deeper analysis of errors and other things.
I think, fouesnant is right, in a way. MD110 is small AXE. In a real AXE we have dtidp / dtidc commands:
CRC=0 - no CRC4;
CRC=1 - sorry, I can't understand it
;CRC=2 - yes CRC4;
CRC=3 - automatic adjustment for CRC4.
Use of CRC4 - deeper analysis of errors and other things.
- Thread starter
- #10
Hi
Then do
SACOP:UNIT=SLP60,LIM=xx,ADDR=909,SECTOR=REL;
and verify the value at the address compare to the table os possibles CRC4 values :
01 = "AUTOMATIC CRC-4" MODE !
11 = "NO CRC-4" MODE !
31 = "ALWAYS CRC-4" MODE !
Normally by default it should be set to automatic, unless your country parameter is configure to sometihng else.
Then do
SACOP:UNIT=SLP60,LIM=xx,ADDR=909,SECTOR=REL;
and verify the value at the address compare to the table os possibles CRC4 values :
01 = "AUTOMATIC CRC-4" MODE !
11 = "NO CRC-4" MODE !
31 = "ALWAYS CRC-4" MODE !
Normally by default it should be set to automatic, unless your country parameter is configure to sometihng else.
Hi
In BC10 try
sacop:unit=slp60,lim=1,filno=12,point=0&&3,reloff=791;
To view the change :
irpdprot=qsig,type=sl60,lim=1,entry=crc4mode;
irpdprot=etsi,type=sl60,lim=1,entry=crc4mode;
irpdprot=nat,type=sl60,lim=1,entry=crc4mode;
irpdprot=res,type=sl60,lim=1,entry=crc4mode;
The pointer were you change the value in Hex is printed in decimal with IRPDP.
Best regards
In BC10 try
sacop:unit=slp60,lim=1,filno=12,point=0&&3,reloff=791;
To view the change :
irpdp
rot=qsig,type=sl60,lim=1,entry=crc4mode;irpdp
rot=etsi,type=sl60,lim=1,entry=crc4mode;irpdp
rot=nat,type=sl60,lim=1,entry=crc4mode;irpdp
rot=res,type=sl60,lim=1,entry=crc4mode;The pointer were you change the value in Hex is printed in decimal with IRPDP.
Best regards
testcentre
Technical User
Fouesnant
In response to your question about the purpose of CRC4, the following may assist.
With the introduction of ISDN it is possible for users to transmit data over a 64 kbit/s clear channel. The problem with this is that it is possible for user equipment to transmit the bit pattern 10011011 which corresponds to the 2 Mbit/s Frame Alignment Signal. PCM links with CRC4 overcome this possibility by checking first that the Frame Alignment Signal is correct, then checking that the CRC4 Multiframe signal is correct before allowing 2 Mbit/s link synchronizing. CRC4 also increases the likelihood of detecting errors in the 2 Mbit/s stream. This is most important as the signalling transfer for the D-channel is at a 64 kbit/s rate which means each bit corresponds to just 244 ns on a 2 Mbit/s link! It is very easy for this to be corrupted by noise unlike with Channel Associated Signalling where bit patterns only change every 2 or 4 ms.
In response to your question about the purpose of CRC4, the following may assist.
With the introduction of ISDN it is possible for users to transmit data over a 64 kbit/s clear channel. The problem with this is that it is possible for user equipment to transmit the bit pattern 10011011 which corresponds to the 2 Mbit/s Frame Alignment Signal. PCM links with CRC4 overcome this possibility by checking first that the Frame Alignment Signal is correct, then checking that the CRC4 Multiframe signal is correct before allowing 2 Mbit/s link synchronizing. CRC4 also increases the likelihood of detecting errors in the 2 Mbit/s stream. This is most important as the signalling transfer for the D-channel is at a 64 kbit/s rate which means each bit corresponds to just 244 ns on a 2 Mbit/s link! It is very easy for this to be corrupted by noise unlike with Channel Associated Signalling where bit patterns only change every 2 or 4 ms.
- Status
Similar threads
