SRST/call-manager-fallback problem

[patrick.johnson]

I'm trying to change the ip source-address for call-manager-fallback but the router tells me that it cannot change ip source-address while call-manager-fallback occurs. The problem is the router is not in fallback mode. The Callmanager shows this router as registered. If I try to do a no call-manager-fallback to start the config over it says "Cannot remove call-manager fallback mode due to active devices (1)" How can I find out what device this is? Any help would be appreciated.

[patrick.johnson]

Well don't you know it by the time you get frustrated enough to post you figure out the problem 10 minutes later. We had to disable MOH-live on call-manager-fallback which was configured to use the E&M port on the router. It was creating an EFXS port which was the one active device.

[Bryant Seppelt]

To find the registered ephone, run command 'show ephone registered'. The output will show the TCP Port used by the registered ephone. In this example it is TCP Port 23508.

T3880RTR001#show ephone registered

ephone-1[0] Mac:2C58.CCF5.C409 TCP socket:[2] activeLine:0 whisperLine:0 REGISTERED in SCCP ver 9/9 max_streams=1
mediaActive:0 whisper_mediaActive:0 startMedia:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0 caps:8
IP:10.37.212.5 * 23508 SCCP Gateway (AN)  keepalive 336321 max_line 2 available_line 1 dual-line
port 2/0/9
Preferred Codec: g711ulaw
Lpcor Type: none

Next run command 'show tcp brief', and match up the TCP Port in the Foreign Address column in order to determine the TCB value (an internal identifier for the endpoint). In this example it is TCB 1A238D5C.

T3880RTR001#show tcp brief
TCB       Local Address               Foreign Address             (state)
137C7D14  t3880rtr001.target.co.1720  tccucmdc102p.target.c.46043 ESTAB
1A238D5C  t3880rtr001.target.co.2000  t3880vgwa001.target.c.23508 ESTAB

Next run command 'clear tcp tcb 1A238D5C'. Then wait a few moments and run command 'show ephone registered' to verify that it is removed. You can now run command 'no call-manager-fallback' without the error "Cannot remove call-manager fallback mode due to active devices (1)"