I would like to set a backup proxy server (SIP) on my SPA508G. I've looked at the documentation, and it does mentions the phone support backup proxy server with the DNS SRV method, but that's not what I want.
In fact, I've not completely understood the behavior of the phone if a backup proxy server is configured and the primary proxy server becomes unavailable. For exemple, if I make a call in this situation, will the phone automatically try to send its SIP INIVITE to the backup proxy server ?
In the Ext1 tab, in the 'Proxy' field, I've tried the value '192.168.1.1:A=192.168.1.2' but it didn't worked (well, the phone didn't tried to fallback on 192.168.1.2 after I've made 192.168.1.1 unreachable).
Any ideas ?
Please see below. This is how we support backup proxy.
Thanks, my first understanding on how this was implemented on the Cisco SMB was wrong, that explain why I had trouble setting it up.
There's a small problem though. So let's say I have a main and secondary proxy. If I cut the connection between the phone and the main proxy, and then call an extension with my phone, it sometimes takes too much time for the phone to try the secondary proxy and the turn this into a 'no response'. This doesn't seem to happen frequently, and only after the phone has rebooted. Are you aware of any similar issue ?
I've done the tests on a SPA504G with firmware version 7.4.4.
I have tried to setup the manual SRV on the SPA504 according to your document and it will not register if I use the SRV= format no matter what I try to do with it. It will only register if I use a single IP address or DNS name. I cannot access DNS to make the changes, so I need the manual SRV format. I am using 7.4.3a on the SPA504G. What am I missing?
Please upgrade to a later firmware, to ensure this is not a bug/defect on an early firmware version. After doing that, if problem persists, please send your phone html configuration (full page .mht) to check config is ok.
The very first thing I did, before posting, was to upgrade the firmware. The did not help.
I am posting the mht file as you requested. This is becoming urgent, as the system had to go live without any redundancy,
so I need to resolve this without using DNS SRV records.
Thanks for your help,
I may need to check with the expert as I have conflicting info, but before that I think it is easier that you perform the test. Please stay tuned.
Alberto asked me to assist with this. I will get to this early next week and will provide you with an update then.
One reference document to locate SPA phone resources
I ran through your config in my lab and it all works as expected. I wrote this document and included some trace information that may offer you some clues: https://supportforums.cisco.com/docs/DOC-15604
Run a Wireshark trace to see what the phone is sending out. Notice on page 3 of the link that I provided, packet 24 the phone registers to the primary proxy and sends INVITES to 703@MY_proxies in my example.
Once the primary proxy has failed, the phone does not attempt to register to the secondary proxy, it sends an INVITE to the secondary proxy, shown in packet 118, at which time the target phone starts ringing.
When the primary proxy fails the phone will automatically switch over to the secondary proxy and the call will be routed. The user making the call will experience a short delay, in the order of seconds during the time that the phone takes to realize that the primary proxy is not responding.
This document may help: https://supportforums.cisco.com/docs/DOC-15604