Monday, February 20, 2006
PRI In INDIA
Thus if you were to terminate them on to your cisco router , you shall need to know one very important parameter.
The FRAMING
So here they are
TATA : crc4
RIC: crc4
BSNL/BBNL/MTNL: no-crc4
So your config for the E1 controller would look like for a BSNL/BBNL/MTNL PRI circuit
isdn switch-type primary-net5
controller E1 2/0
pri-group timeslots 1-31
framing no-crc4
no shut
description : ISDN PRI (XXXXXX)
Friday, February 17, 2006
c2821 ISDN site dialing into c3845 , call lasts only 28 sec
We have a 1 PRI at the central site on c3845
The remote site is supposed to dial in to the central site when the primary link fails
We have a Dialer-watch configuration done on the remote site & PPP callback request. The IP address is negotiated during PPP NCP/IPCP.
At the central site we have a PPP callback accept configured & the IP address is assigned from a static ISDN pool
Now the problem:-
The Remote site connects successfully into the Central Site. However the call lasts only 28 sec.
So what we did to resolve it.
We had four BRI S/T ports on the c2821. However only one was connected to a BRI line. But at all times all four ports were part of the rotary group.
This was causing the dialer interface to cycle between the 4 BRI S/T ports.
So we removed the other 3 non connected ports from the rotary group & voila the cal lasted till the idle timeout.
Monday, February 13, 2006
Saturday, February 11, 2006
c3845 & SFP 1000BaseLX modules
Sounds simple,
well its simple
1) insert the SFP, the router immediately recognizers it.
2) configure the interface with followings details
- media-type sfp
- duplex
- speed
- no shut
- IP address
Well we did all the above and yet the link was not coming up.
We could also not see the SFP LED indicator come UP. This clearly indicated that there was a link issue .What could we've done wrong ?
Seems to be a pretty simple task, aint it ?
Well it turned out to be a horror for us.
We spent hours on the testing the Fiber , the config, and the SFP itself.
To our horror, out some searching on cisco.com & goggle we found out that we should try the defaults first.
i.e default speed
&
default duplex
So we did that , not hoping much luck.
But surprisingly the link came Up instantly
the LED on the SFP module was glowing & we could ping the remote destination address as well.
So I am not sure, why did the Link not come up when we had enforced the Duplex = Full & Speed = 100 , also tried Speed = 1000 ?
Anybody can help why it didn't work ?
the present interface config is as follows:-
interface GigabitEthernet0/0
IP address 10.12.13.9 255.255.255.252
IP access-group 112 in
duplex auto
speed auto
media-type sfp negotiation auto
end
SIM Card Rejected
Well it has worked in roaming just fine all these times.
But yesterday I was .
in PUNE for some office work, & the Phone gave this message..
" SIM Card Rejected"
Thus I tried frantically the following:-
1) reboot the phone
2) remove the sim , battery & reinsert it
3) clean the SIM & the socket connections on the phone
4) Try inserting the SIM into another phone.....
But all these attempts were in vain
every time I would boot the phone I would get the same message, " SIM card Rejected"
So I called HUTCH callcenter.
The guy very very politely told me that my card was still active & the roaming profile was enabled.
so from their end the service aspect is not a problem.
Thus I was left with only one choice.
As per the call center guy, I have to visit the local HUTCH shop & they will replace the faulty SIM with a new one.
Also he told me that the new sim would be active in one hour & that the replacement would be FREE.
So lets see, I am due to return for MUMBAI tomorrow . Will try to visit the HUTCH shop then.