Hi Buddy
Really I am not much into Cisco but then the device TG-4C you have there doesn't require any external voltage and just requires a dry contact closure. Your FXO should do that only if you can configure "supervisory disconnect" and "Loop signalling" correctly.
--
Nithin
Yes HIMDP, you are right. I might have overlooked it [bugeyed]
@Anlly => Buddy, check it on Hyperterm, configuration is running good... still not coming,, try to change the I/O Port.
--
Nithin
Hi Buddy
As per this "/SYSN/USR1/ACS/CIL/ CIL-1 READY/STARTED C" you have an output file CIL-1 now whereas earlier it was only SMDR.
Did you initiate it?
anyways.. the " READY/STARTED " indicates that the output generation has started. you should get data on the serial port.
--
Nithin
Hi Buddy
This seems to be a peculiar issue. I remember I faced the same issue for which we need to implement a patch which Ericsson provided.
You may need to contact Aastra maybe through a partner.
--
Nithin
Hi Buddy
you already have a file initiated "SMDR"
Do you require a new one here? If yes as HIMDP said you need to initiate the file with "CLDFI" otherwise the output file "SMDR" is well configured. check CLDFP;
Is it on serial connection or on IP?
--
Nithin
Hi Buddy
Did you already use this ethernet connection to NIU, or trying lately to access it??
Just one thing to check if you are trying it lately, Did you initiate the IO port for MML login??
If you are able to login through the serial ports, take a IODDP print.
--
Nithin
--
Nithin
Hi FCPLI
Finally, not knowing what to do further.. New LIM is re-installed. and everything seems to work fine.
Thanks for your support
Nithin
--
Nithin
Doktor
I may be wrong in understanding your query but still thought if may help you...
If you have used command like
IONCI:IODEV=CIL,User=CIL-0,IP=a.b.c.d,RPORT=xxxx;
then the system which is having the IP "a.b.c.d" should monitor the port xxxx.
Usually the call accounting S/W monitors the...
Usually the SMDR port doesnt connect immediately. In XP, where fortunately Hyperterm is available, the "Wait for a call" just works fine.
Frankly speaking, never tried this on WinFIOL and also WIN2008 server.
--
Nithin
Hi FCPLI
the dump and reload was only after copying the units. I have no clues about this and I just going by you.
still the call log is not as it is on older LIMs.
Thanks
Nithin
--
Nithin
Hi FCPLI
I took dump before reloading ( was actually a scheduled one ;) ).
the prints
PCLOP:UNIT=KLP1D2,LIM=1;
PCLOP:UNIT=KLP1D2,LIM=6;
and
PCLOP:UNIT=SLP60,LIM=1;
PCLOP:UNIT=SLP60,LIM=6;
are identical. dont know where I am missing.. :(
Thanks
Nithin
--
Nithin
Hi FCPLI
I meant that I am doing the reload manually. I did it, even then the problem persists :(
Any more program units I need to copy... or is it required that we need to get the patch anyway.. which I dont think is available anymore with anybody [ponder]
Thanks much.
--
Nithin
Hi FCPLI
Thanks for the info, but I was not able to find any entry such relevance in NUTRI/RONDP.
But then I have copied the Program units you have suggested.. which again requires a LIM reload.
I'll have to do it later in the after hours. I'll get back once done. Hope this PU copying helps...
thread806-767724
Hi Guys
Referencing to the old thread, I have similar query, I learned that the NLOG in BC9 is a market adaption. A patch would have been implemented.
We have a BC9 with 6 LIMS.. the 6th is recently added.. (Yeah I know,, we did not upgrade the system yet )
the issue is...
Hey Aleena,
as XS said, you need an analog modem and a number be defined in command number 5621.
The number defined acts as an extension number to get connected to inbuilt modem.
If BP has ISDN PRI, then there shouldn't any problem directly mapping the number defined in 5621 to any DID...
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.