MGCP gateway still registered in SRST?

[lowfell]

Question I'm trying to test srst on an a replacement isdn 28XX with 4321.
I put a acl on  access switch to deny access to cucm and the phones. the phones go in to "service interupted"  but no SRST service,

However when i run #show ccm-manager it says the gateway is still registered to a call manager. Is this correct?

[Nithin Eluvathingal]

If the gateways shows registered with CUCM means gateway is still talking to CUCM. 
check ur ACL.

[lowfell]

Hello all and thank you. This is the ACL is this which should cover it?
The phones DO go in to "Service interrupted. This is very puzzling! 

Also. I've just had a brainwave, instead of using an acl Or a route to null, could you not just change the domin name on the gateway or the CUCM to temporarily make the phones/gateway unregister?

Interface voice vlan
ip access-group 109 in
ip access-group 110 out
!
access-list 109 remark *** Prohibit traffic from remote site to central site VOIP Vlans ***
access-list 109 deny ip any 10.210.1.0 0.0.0.255
access-list 109 deny ip any 10.226.1.0 0.0.0.255
access-list 109 permit ip any any
access-list 110 remark *** Prohibit traffic from central site VOIP Vlans to remote site***
access-list 110 deny ip 10.226.1.0 0.0.0.255 any
access-list 110 deny ip 10.210.1.0 0.0.0.255 any
access-list 110 permit ip any any


I can see this message in the logs when i tried a call which mentions about "out of order", but the isdn works when Cucm is connected?

ISDN Se0/1/0:15 Q931: RX <- SETUP pd = 8 callref = 0x0085
Sending Complete
Bearer Capability i = 0x9090A3
Standard = CCITT
Transfer Capability = 3.1kHz Audio
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA18381
Preferred, Channel 1
Progress Ind i = 0x8A81 - Call not end-to-end ISDN, may have in-band info
Calling Party Number i = 0x2180, '780097XXXX'
Plan:ISDN, Type:National
Called Party Number i = 0x81, '526900'
Plan:ISDN, Type:Unknown
Feb 19 11:25:54: ISDN Se0/1/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x8085
Cause i = 0x809B - Destination out of order

[Roger Kallberg]

Changing the domain would not have the specific effect that you seek. As I wrote in your duplicate post, use null host routes.

If you’re CM IP would be 10.221.224.75 for example the below route on the gateway from the site would block all traffic to reach that IP.

ip route 10.221.224.75 255.255.255.255 Null0

[lowfell]

Hello and thanks again for your help. Can you please explain why changing the domain name wouldn't stop the gateay from registering with the cucm as if it's not correct in the first place then registration won't work?

[Nithin Eluvathingal]

Go through the below Link.

https://www.ciscopress.com/articles/article.asp?p=1744068&seqNum=4

[lowfell]

Good morning and thanks again for your help. In the past when i've setup gateways, if the domain name isn't exactly the same in CUCM as it is on the gateway, then registration fails. Using that logic, if I change the domain name temporarily, then wouldn't the gateway drop it's registration? Here is a loink from Cisco which confirms this
https://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-manager-callmanager/68240-mgcp-gtwy-reg-failure.html

Isn't my issue more to do with the ISDN not falling back to the gateway if you look at the debug message?
ISDN Se0/1/0:15 Q931: RX <- SETUP pd = 8 callref = 0x0085
Sending Complete
Bearer Capability i = 0x9090A3
Standard = CCITT
Transfer Capability = 3.1kHz Audio
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA18381
Preferred, Channel 1
Progress Ind i = 0x8A81 - Call not end-to-end ISDN, may have in-band info
Calling Party Number i = 0x2180, '780097XXXX'
Plan:ISDN, Type:National
Called Party Number i = 0x81, '526900'
Plan:ISDN, Type:Unknown
Feb 19 11:25:54: ISDN Se0/1/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x8085
Cause i = 0x809B - Destination out of order

[Roger Kallberg]

It might get the gateway to fall over, but it doesn’t necessarily mean that the phones would do the same. It would depend on how your configuration in CM looks like. The safest and quickest option IMO is to use null routes. Obviously it’s your choice, use whatever option you feel comfortable with.

[lowfell]

thanks again for your patience. i'll I'll try  both ways tomorrow and see which works best. watch this space.

[Nithin Eluvathingal]

@Roger Kallberg  mentioned Changing the domain will not help you. use null route.

[Roger Kallberg]

Duplicate post https://community.cisco.com/t5/ip-telephony-and-phones/mgcp-gateway-still-registered-in-srst/m-p/4294488