cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1076
Views
0
Helpful
3
Replies

8941/8961 SRST

carlnewton
Level 3
Level 3

Guys,

Im trying to get SRST to work with 8941 / 8961 in SIP mode.  The compatibility matrix says this should work provided my phones are above FW 9.2.2.  My phones are 9.3.2.

http://www.cisco.com/en/US/docs/voice_ip_comm/cusrst/requirements/guide/srs90spc.html

I have a config on my gateway, but to be honest I don't think this is the problem at the moment.  The phones dont even seem to have an SRST reference.  There is NOTHING in the menus for any of the 8941/8961 phones that lists an SRST reference.  When I browse to the phone IP Address, I still do not see it.  However, if I TFTP the config of the phone, it is def getting an SRST reference:

<srstInfo  uuid="{09836056-6fcc-e54a-94c8-9e025ea25c22}">

<name>SRST-Ref</name>

<srstOption>User Specific</srstOption>

<userModifiable>true</userModifiable>

<ipAddr1>10.201.2.250</ipAddr1>

<port1>2000</port1>

<ipAddr2></ipAddr2>

<port2>2000</port2>

<ipAddr3></ipAddr3>

<port3>2000</port3>

<sipIpAddr1>10.201.2.250</sipIpAddr1>

<sipPort1>5060</sipPort1>

<sipIpAddr2></sipIpAddr2>

<sipPort2>5060</sipPort2>

<sipIpAddr3></sipIpAddr3>

<sipPort3>5060</sipPort3>

<isSecure>false</isSecure>

</srstInfo>

If I convert the phones to SCCP mode they work in SRST fine.  In SIP mode they just sit there saying "phone unregistered" when we have a WAN failure.  I know there is a difference between SIP and SCCP SRST configurations on the gateway, but I have configured for both:

voice service voip

ip address trusted list

  ipv4 10.98.91.0 255.255.255.0

  ipv4 10.98.92.0 255.255.255.0

  ipv4 10.201.2.0 255.255.255.0

  ipv4 10.201.0.0 255.255.255.0

  ipv4 10.99.200.31

allow-connections h323 to h323

allow-connections h323 to sip

allow-connections sip to h323

allow-connections sip to sip

fax protocol pass-through g711alaw

h323

sip

  bind control source-interface GigabitEthernet0/1.2

  bind media source-interface GigabitEthernet0/1.2

  registrar server expires max 600 min 60

voice register global

max-dn 50

max-pool 10

!

voice register pool  10

id network 10.201.2.0 mask 255.255.255.0

number 1 41... preference 1

preference 1

alias 1 41000 to 41198

dtmf-relay rtp-nte cisco-rtp sip-notify

codec g711ulaw

no vad

call-manager-fallback

max-conferences 10 gain -6

transfer-system full-consult

ip source-address 10.201.2.250 port 2000

max-ephones 20

max-dn 50

system message primary CM DOWN FEATURES DISABLED

time-zone 23

time-format 24

date-format dd-mm-yy

The problem seems to be that the SIP phones just do not try and register with anything once they lose CM, and have nothing showing in any menus referencing SRST at all.  I def have an SRST reference on the device pool, and the phones are getting the SRST reference in the config file as you can see above.  Why do they not show it, or try and register with it?

Thanks for your help in advance

3 Replies 3

Jonathan Schulenberg
Hall of Fame
Hall of Fame

You need to specify an IP address for SIP Phones on your SRST Reference in CUCM. It is a separate field from the SCCP phones. Once you set it, perform an apply config and full reset of the phone so it picks up an updated XML config file.

Please remember to rate helpful responses and identify helpful or correct answers.

Thanks Jonathan, I have specified this though, and as you can see from my post above it is receiving it.

Extract from the phones config I manually TFTP'd from the CUCM:

10.201.2.250

10.201.2.250

5060

Thanks

I am having the exact same problem with SCCP, SRST , if you downgrade to 9.2..2 from 9.3.2 you will  see the SRSt reference

On the phone and SRST works. This problem only appeared after I upgraded the firmware to get phone walloper which was not available on 9.2.2. I opened a TAC case thus afternoon.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: