From looking at the docs, it seems the 4K will request the calling party info either before or after receiving the called party. But I don't know enough about it to advise as have never dealt with this signalling. MFCTA AMO is where you can nip & tuck for MFC R2, maybe it's possible there to either stop the 4K requesting it or make 4K discard it if received.
but their definition of A5 and A3 signal does not agree with Edoku. Not surprising as there a few different implementations of this signalling. You can see roughly how the signalling is working though.
MFCTA AMO is where I would be looking but there's a lot of parameters in there. You need to read the section in Edoku on MFC-R2 signalling and also the AMO guide for MFCTA. I'm not sure how easy it is to undo any MFCTA changes you make because there is no ADD, no DEL, only CHAnge. I would make any changes in the evening so I could reload it, if it came to that.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.