[cisco-voip] PRI Wont Register!!

Countryman, Edward Edward.Countryman at provena.org
Mon Aug 20 09:49:48 EDT 2012


Just to close out this thread with a resolution.

 

It was necessary to bounce both the CCM and RIS COLLECTOR services on
all servers (pub and all subs) to resolve this.

 

Not sure what caused the problem in the first place, but things are back
to normal now.

 

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Countryman,
Edward
Sent: Thursday, August 16, 2012 10:26 AM
To: Ryan Ratliff
Cc: cisco-voip voyp list
Subject: Re: [cisco-voip] PRI Wont Register!!

 

No other connectivity issues.   But we were seeing a lot of phones and
other gateways showing up as unknown as well.  (These are all on the
same 2 SUB's, we have a 3rd SUB but all of its phones/gateways are
reflecting properly)

 

Heard back from TAC, who recommended bouncing the RIS COLLECTOR service
on all nodes.  This did seem to correct most of the problem however I
have still have a gateway that shows UNKNOWN but is in fact properly
registered.  The TAC engineer concluded this GW wasn't related to the
RIS problem and instructed us to open a different LOG for that.   (Not
sure why he couldn't just send us to the next group but we are waiting
for call back on second case)

 

I have never run across a problem like this before... 

 

From: Ryan Ratliff [mailto:rratliff at cisco.com] 
Sent: Wednesday, August 15, 2012 1:25 PM
To: Countryman, Edward
Cc: Lelio Fulgenzi; cisco-voip voyp list
Subject: Re: [cisco-voip] PRI Wont Register!!

 

No need for reboot when it's passing calls correctly.  I'd agree it's a
RIS issue.   You can try bouncing RIS on the pub in addition to the sub
where the phone is registered.   Since RIS relies on ccm to populate the
shared memory segment that RIS reads from worst case it may take a ccm
service bounce too. 

 

Any other connectivity issues between that sub and the pub?    If you
register devices to the pub or another sub do they show up correctly?

 

-Ryan

 

On Aug 15, 2012, at 2:15 PM, Lelio Fulgenzi wrote:

 

Have you tried reloading the router? 

---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it. 
                              - LFJ (with apologies to Mr. Popeil)

________________________________

From: "Edward Countryman" <Edward.Countryman at provena.org>
To: "Edward Countryman" <Edward.Countryman at provena.org>,
cisco-voip at puck.nether.net
Sent: Wednesday, August 15, 2012 2:13:40 PM
Subject: Re: [cisco-voip] PRI Wont Register!!

Thank you to all who responded.  Weird problem, which may be of interest
to some of you.

 

Gateway  (SHOW CCM-MANAGER) reflects proper registration.  Viewing the
GW  thru CCM admin indicates STATUS UNKNOWN and IP ADDRESS UNKNOWN. 

 

This lead me to believe it wasn't registered correctly, even though the
router says it was.

 

We configured a few numbers to route through the gateway just for the
fun of it and sure enough it is in fact up,  and properly passes calls.
I believe it has something to do with the RIS DATA COLLECTOR service on
CCM, but haven't figured out what yet.  Still waiting on TAC

 

I tried to reset the RIS DATA COLLECTOR service on one of my
subscribers, and now any phone or gateway shows UNKNOWN even through
everything is working correctly. 

 

Not sure what is going on..... 

 

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf OfCountryman,
Edward
Sent: Wednesday, August 15, 2012 11:09 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] PRI Wont Register!!

 

Im on a jobsite installing new 2951 with two port VWIC2-2mft-t1  being
used to connect via PRI to an existing Nortel CS1000

 

The gateway shows as registered to CCM and both PRI's have "multiple
frames established" but the PRI's show as UNKNOWN in the CCM admin
pages. 

 

No errors on the PRI connections, CCM is configured as network and the
switch type is DMS100. 

 

I am stumped, any ideas from anyone????

 

(Going to open TAC case but that may be hours)


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120820/efee80f8/attachment.html>


More information about the cisco-voip mailing list