Search results for query: *

So now you people are creating a new system? Wow....

Long time since I was cheking the forum, no on vacation. So first of all, himdp and vkrt are 100% right. DO nOT start with random SACOS commands,or you destrroy everything there. Now, I need to see the PLEX (I think I still have it), but then, if you REALLY want to fix this, prepare for a bunch...

SENFILCAT is a patch issue

Assuming key=0 and pointers (susip) for 4544 is 23b and 352, and 6190 pointers 46b and 2f6, then /*SETKEYINF*/ sgsai:sigar=1,signo=68,stype=swsw,level=b,lim=11,unit=klp1d,lcside=exe,byte=0-02&1-3b&5-1&6-c2&7-1&8-0&9-1&10-4&11-6b&13-ff&14-fF; sgsac:sigar=1,byte=15-2&16-f6; /*SETNUMINF*/...

also change here in byte 14-d to 14-x sgsai:sigar=2,signo=85,stype=swsw,level=b,lim=11,unit=klp1d,lcside=exe,byte=0-4&1-6b&5-1&6-c2&7-1&8-2&9-f6&10-1&11-7d&12-2&13-70&14-d;

Then one more job for you: sacop:unit=klp1o,lim=11,filno=2,reloff=3&&6,point=0&&1f3; The beginning is full of FF, but try to find 6190 like here: 01F3 0003 00007FC1 06 . 01F3 0004 00007FC2 01 . 01F3 0005 00007FC3 09 . 01F3 0006...

/*SETKEYINF*/ sgsai:sigar=1,signo=68,stype=swsw,level=b,lim=11,unit=klp1d,lcside=exe,byte=0-02&1-70&5-1&6-c2&7-1&8-d&9-1&10-4&11-6b&13-ff&14-fF; sgsac:sigar=1,byte=15-2&16-f6; /*SETNUMINF*/...

You can try this, but no guarantee it is working. Dump before. I fit is stuck, ladai /*SETKEYINF*/ sgsai:sigar=1,signo=68,stype=swsw,level=b,lim=11,unit=klp1d,lcside=exe,byte=0-02&1-70&5-1&6-c2&7-1&8-d&9-1&10-4&11-6b&13-ff&14-fF; sgsac:sigar=1,byte=15-2&16-f6; /*SETNUMINF*/...

OK. This is going to be tricky, no connection direct.... But first of all, hirei;, the start trace on KHH and ksane 6190. After it stops or reloads or whatever, stop the trace.

Now the pointers are there, but where is the key for ADN? Dump this conf first. This just if you get data reload. Try to initiate a new ADN on 4544. What happens?

So ODN is ATS? How in the heaven did you get this? Wau, change it back to DTS - here is your issue starting...

Can you print susip of the ODN?

Oh, sorry, this was ADN. I'll be back in a moment

OK, let's try to cheat this. If it doesn't help, we need to do it another way. First sacop:unit=der,lim=11,filno=1,reloff=1&2,point=2f6; here the result should be 02F6 0001 000267A7 16 . 02F6 0002 000267A8 09 . If not, stop here...

OK, seems that KLP1O has a small problem. sacop:unit=klp1o,lim=11,filno=1,reloff=0&1,point=23b; In the data I think you see only FF FF? 23B is your extension DER pointer, but KLP pointer is missing. This sacop is just to ensure that we are on correct track...

You seem to have a DER or KLP corruption (I think so) in LIM11. There is no pointer given to DER (FFFF). For this, trace KHH, when trying to print KSDDP. Just to start....

himdp: Just look at the trace. He is sending 3 times 21 - is it OK? But in any case, A3 or A5 or whatever back from the SP is missing, so this is definitely the PSTN issue (or maybe the digits are just accepted by the PSTN before it understands that this kind of numbering scheme/length is not...

Which version do you have? Type 6 is included in BC11 and later...

try this: IPU/NIU: 25 PINS: 9 PINS: A02 3 2 B02 2 3 A04+B04 7 5 A06 9 9 B06 20 4 C06 6 6 A08 8 1 B08 4 7 C08 5 5

himdp, Do you think this is going to work with only one channel? 19, as he explains? I don't know..... If yes, how?