[cisco-voip] SRST extension assignment

[Hughes, Scott GRE-MG]

OK .. in that case, I'm going to say we don't have that problem, because no ephone or ephone-dn appears in "show run"

Scott

From: Mac GroupStudy [mailto:mac.groupstudy at gmail.com] 
Sent: Thursday, May 20, 2010 1:50 PM
To: Hughes, Scott GRE-MG
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] SRST extension assignment

from global config)# no ehone #
and then config)# no ehone-dn #

where "#" equals the numeric values of ephones and ephone-dns (1,2,3, etc.) until they are all removed...


On Thu, May 20, 2010 at 2:39 PM, Hughes, Scott GRE-MG <SHughes at grenergy.com> wrote:
No, it was built from a blank config. We did attempt 1 SRST failover before adding the "dialplan-pattern..." config that I mention below. Could that hae an effect? If so, how can I clear out any "memory" it has of ephone configs?

Scott

From: Mac GroupStudy [mailto:mac.groupstudy at gmail.com]
Sent: Thursday, May 20, 2010 1:16 PM
To: Hughes, Scott GRE-MG
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] SRST extension assignment

Does the router have previous SRST configurations in it?
On Thu, May 20, 2010 at 12:24 PM, Hughes, Scott GRE-MG <SHughes at grenergy.com> wrote:
CUCM Version: 6.1(3)
Phone Firmware: Cisco 7942G/7962G -- SCCP42.8-4-2S
Router IOS: C2800NM-IPVOICEK9-M  12.4(20)T5

Perhaps I'm missing something obvious, but SRST is behaving strangely. When the phone loses connectivity to Call Manager, it registers to the on-site router as expected. The problem is that it gets a new extension number (it doesn't keep it's original). We have 4 digit DNs usually, but the router assigns a 5 digit extension, completely different than the correct one. All the phones have multiple DN's assigned in CUCM, but we hope to just have the primary extension of each phone come back to life in SRST mode.

I tried previously on 12.4(25b) before upgrading to the 12.4(20)T5

Relevant config:

call-manager-fallback
 max-conferences 12 gain -6
 transfer-system full-consult
 ip source-address X.X.X.X port 2000
 max-ephones 42
 max-dn 50
 dialplan-pattern 1 7655555... extension-length 4

And here's a debug from a ephone registration/extension-assigner

May 19 13:44:26: ephone-(8)[12] StationRegisterMessage (0/0/43) from 10.96.82.9
May 19 13:44:26: ephone-(8)[12] Register StationIdentifier DeviceName SEP2893FEA2F3C4
May 19 13:44:26: ephone-(8)[12] StationIdentifier Instance 2    deviceType 434
May 19 13:44:26: ephone-8[7/12]:stationIpAddr 10.96.82.9
May 19 13:44:26: ephone-8[7/12][SEP2893FEA2F3C4]:maxStreams 5
May 19 13:44:26: ephone-8[7/12][SEP2893FEA2F3C4]:From Phone raw protocol Ver 0x85720011
May 19 13:44:26: ephone-8[7/12][SEP2893FEA2F3C4]:protocol Ver 0x85720011
May 19 13:44:26: ephone-8[7/12][SEP2893FEA2F3C4]:phone-size 57240 dn-size 784
May 19 13:44:26: ephone-(8) Allow any Skinny Server IP address 10.96.82.254
May 19 13:44:26: ephone-8[7/12][SEP2893FEA2F3C4]:Found entry 7 for 2893FEA2F3C4
May 19 13:44:26: ephone-8[7/12][SEP2893FEA2F3C4]:phone SEP2893FEA2F3C4 re-associate OK on socket [12]
May 19 13:44:26: %IPPHONE-6-REGISTER_NEW: ephone-8:SEP2893FEA2F3C4 IP:10.96.82.9 Socket:12 DeviceType:Phone has registered.
May 19 13:44:26: Phone 7 socket 12
May 19 13:44:26: Skinny Local IP address = 10.96.82.254 on port 2000

May 19 13:44:26: Skinny Phone IP address = 10.96.82.9 24607
May 19 13:44:26: ephone-8[7/12][SEP2893FEA2F3C4]:Signal protocol ver 9 to phone with ver 17
May 19 13:44:26: ephone-8[7/12][SEP2893FEA2F3C4]:Date Format M/D/Y
May 19 13:44:26: ephone-8[7/12]:RegisterAck sent to sockettype ephone socket 12: keepalive period 30 use sccp-version 9
May 19 13:44:26: ephone-8[7/12]:CapabilitiesReq sent
May 19 13:44:26: %IPPHONE-6-REG_ALARM: 10: Name=SEP2893FEA2F3C4 Load= SCCP42.8-4-2S Last=TCP-timeout
May 19 13:44:26:
Skinny StationAlarmMessage on socket [12] 10.96.82.9 SEP2893FEA2F3C4
May 19 13:44:26: severityInformational p1=0 [0x0] p2=0 [0x0]
May 19 13:44:26: 10: Name=SEP2893FEA2F3C4 Load= SCCP42.8-4-2S Last=TCP-timeout
May 19 13:44:26: ephone-8[7/12][SEP2893FEA2F3C4]:Skinny IP port 3500 set for socket [12]
May 19 13:44:26: ephone-8[7/12]:ButtonTemplateReqMessage
May 19 13:44:26: ephone-8[7/12]:ButtonTemplateReqMessage waiting for Caps
May 19 13:44:26: ephone-8[7/12]:StationSoftKeyTemplateReqMessage
May 19 13:44:26: ***No Tag defined for SK 31
May 19 13:44:26: ephone-8[7/12]:StationSoftKeyTemplateResMessage
May 19 13:44:26: ephone-8[7/12]:StationSoftKeySetReqMessage
May 19 13:44:26: ephone-8[7/12]:StationSoftKeySetResMessage
May 19 13:44:26: ephone-8[7/12]:StationConfigStatReqMessage
May 19 13:44:26: ephone-8[7/12][SEP2893FEA2F3C4]:StationConfigStatMessage sent for device SEP2893FEA2F3C4 (40/280)
May 19 13:44:26: ephone-8[7/12]:CapabilitiesRes received
May 19 13:44:26: ephone-8[7/12][SEP2893FEA2F3C4]:Caps list 12
WideBand_256K  40 ms, is_mtp 0
G722_64k  60 ms, is_mtp 0
G711Ulaw64k  40 ms, is_mtp 0
G711Alaw64k  40 ms, is_mtp 0
G722_56k  60 ms, is_mtp 0
G722_48k  60 ms, is_mtp 0
ILBC  60 ms, is_mtp 0
G729AnnexB  60 ms, is_mtp 0
G729AnnexAwAnnexB  60 ms, is_mtp 0
G729  60 ms, is_mtp 0
G729AnnexA  60 ms, is_mtp 0
Unrecognized Media Type 257  1 ms, is_mtp 0

May 19 13:44:26: ephone-8[7/12]:Process pending button template
May 19 13:44:26: ephone-8[7/12]:ButtonTemplateReqMessage
May 19 13:44:26: ephone-8[7/12][SEP2893FEA2F3C4]:StationButtonTemplateReqMessage set max presentation to 6
May 19 13:44:26: ephone-8[7/12]:ButtonTemplateReq requesting fallback info
May 19 13:44:26: %VOICE_CODEC-6-FALLBACK: ephone-8: Configured codec is not supported by phone , fallback to codec g711ulaw
May 19 13:44:26: ephone-8[7/12]:MediaPathEventMessage
May 19 13:44:26: ephone-8[7/12]:MediaPathEventMessage
May 19 13:44:26: ephone-8[7/12]:MediaPathCapabilitiesMessage
May 19 13:44:26: ephone-8[7/12][SEP2893FEA2F3C4]:Button Template 2 buttons received, total 2 buttons
May 19 13:44:26: ephone-8[7/12]:ButtonTemplateReqMessage
May 19 13:44:26: ephone-8[7/12][SEP2893FEA2F3C4]:StationButtonTemplateReqMessage set max presentation to 6
May 19 13:44:26: ephone-8[7/12][SEP2893FEA2F3C4]:Setting 2 lines 0 speed-dials on phone (max_line 2)
May 19 13:44:26: ephone-8[7/12][SEP2893FEA2F3C4]:First Speed Dial Button location is 0 (0)
May 19 13:44:26: ephone-8[7/12]:ButtonTemplate lines=2 speed=0 buttons=2 offset=0
May 19 13:44:26: ephone-8[7/12]:Send the previous reserved one from the ephone back to it
May 19 13:44:26: ephone-8[7/12][SEP2893FEA2F3C4]:StationLineStatReqMessage from ephone line 1
May 19 13:44:26: ephone-8[7/12]:StationLineStatReqMessage ephone line 1 DN 1 = 79041 desc = 79041 label =
May 19 13:44:26: ephone-8[7/12][SEP2893FEA2F3C4]:StationLineStatResMessage sent to ephone (1 of 2)
May 19 13:44:26: ephone-8[7/12][SEP2893FEA2F3C4]:StationForwardStatReqMessage line 1 from ephone
May 19 13:44:26: Skinny StationForwardStatMessage line 1 sent on ephone socket [12] for ephone-8
May 19 13:44:26: activeForward 0 AllActive 0 BusyActive 0 NoAnswerActive 0
May 19 13:44:26: ephone-8[7/12][SEP2893FEA2F3C4]:StationLineStatReqMessage from ephone line 2
May 19 13:44:26: ephone-8[7/12][SEP2893FEA2F3C4]:StationLineStatReqMessage from ephone line 2 Invalid DN -1
May 19 13:44:26: ephone-8[7/12][SEP2893FEA2F3C4]:StationLineStatResMessage sent to ephone (2 of 2)
May 19 13:44:26: ephone-8[7/12]:SkinnyCompleteRegistration
May 19 13:44:26: ephone-8[7/12][SEP2893FEA2F3C4]:StationForwardStatReqMessage line 2 from ephone
May 19 13:44:26: Skinny StationForwardStatMessage line 2 sent on ephone socket [12] for ephone-8
May 19 13:44:26: activeForward 0 AllActive 0 BusyActive 0 NoAnswerActive 0
May 19 13:44:26: ephone-8[7/12][SEP2893FEA2F3C4]:Skinny Available Lines 2 set for socket [12]
May 19 13:44:26: ephone-8[7/12]:Already done SkinnyCompleteRegistration


Am I missing something?

Scott





NOTICE TO RECIPIENT: The information contained in this message from
Great River Energy and any attachments are confidential and intended
only for the named recipient(s). If you have received this message in
error, you are prohibited from copying, distributing or using the
information. Please contact the sender immediately by return email and
delete the original message.






NOTICE TO RECIPIENT: The information contained in this message from
Great River Energy and any attachments are confidential and intended
only for the named recipient(s). If you have received this message in 
error, you are prohibited from copying, distributing or using the
information. Please contact the sender immediately by return email and
delete the original message.