Plantronics + Polycom. Now together as Poly Logo

Polycom phones looses registration within cluster scenario.

Highlighted
Occasional Advisor

Polycom phones looses registration within cluster scenario.

Hello. We faced to an issue with polycom, namely - polycom phones looses registration within SRV/DNS based cluster scenario.. 
So we have round-robin cluster of SIP-proxy instances behind the same SRV/A records(each instance has the same weight). The initial registration works fine, but after the polycom sends a SUBSCRIBE request to another one sipProxy instance(because of round-robin scenario) - polycom stops sending re-register by expires which we are providing in 200Ok message... 

So the idea is to keep polycom located on the instance where initial register request came to.

But polycom is sending SUBSCRIBE in shuffle(not to the server where registration is located)

Message 1 of 11
10 REPLIES 10
Highlighted
Polycom Employee & Community Manager

Re: Polycom phones looses registration within cluster scenario.

Hello @zbazarov ,

 

Welcome to the Poly Community.

Both the communities Must Read First and the FAQ reference the basic minimum information a new or follow up post should contain.

This ensures the questions having to be asked are limited and any new or follow up post contains the right amount of details to ensure any voluntary participant within the community does not spend additional time chasing basic information.

As a reminder the basic information asked for:

UC Software 4.0.0 or later via the Web Interface Utilities > Phone Backup & Restore > Phone Backup > Phone Backup. Please rename into .TXT or Zip the file to attach.
Since UC Software 5.9.0 simply provide this via the Web Interface Diagnostics > Download Support Information Package

  • If possible provide a Log and either attach them or use the Code Tag.Consult the Troubleshooting Section found within the FAQ if applicable
  • If possible provide the MAC Address or Serial of the device
  • Provide details for example if the issue is a day 1 issue or only happened after an upgrade or any other relevant details
  • For questions around Support please check here

Whilst providing some of these details may not directly impact any possible answer the community can provide, it does enable Poly to have an overview of the current software used. In addition, providing all details at the same time allow us to check logs or look up potential support partners if an issue needs to come into support. It also enables us to verify the entitlement for using features.


Please ensure you always check the FAQ's and/or utilize the community search before posting any new topics or follow up posts.


Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

----------------

Notice: This community forum is not an official Poly support resource, thus responses from Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge. If you need immediate and/or official assistance please open a service ticket through your proper support channels.
Please also ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's
Message 2 of 11
Highlighted
Occasional Advisor

Re: Polycom phones looses registration within cluster scenario.

Phone ModelVVX 411
Part Number3111-48450-001 Rev:A
MAC Address64:16:7F:0E:5B:2C
IP ModeIPv4
IP Address10.3.2.78
UC Software Version5.9.2.3446
Updater Version5.9.7.19340


Call platform rfc3261 based. 

Message 3 of 11
Highlighted
Polycom Employee

Re: Polycom phones looses registration within cluster scenario.

Hello  zbazarov,

 

As per the scenario mentioned in above comment we need to verify below :

 

- If  re-registration fail over parameter (RROFO) is enabled or disabled on phone  if enabled the registration and subscribe will stick to same server.

 

- Since each instance has same weight need to check how phone is preparing the proxy list based on the DNS response for the SRV record before phone sending  register or subscribe requests to the server.

 

To get more understand about the behavior of the phone in this scenario please provide below information:

- Import the attached debug file(logs.cfg) to the phone.

- Replicate the scenario.

-  Share us the app logs and wireshark capture from the phone.

- Phone backup file.

 

 Thanks,

Surya

Message 4 of 11
Highlighted
Occasional Advisor

Re: Polycom phones looses registration within cluster scenario.

Hello! Thanks for you reply! 
When I can get this parameter? 
- If  re-registration fail over parameter (RROFO) is enabled or disabled on phone  if enabled the registration and subscribe will stick to same server.

Message 5 of 11
Highlighted
Occasional Advisor

Re: Polycom phones looses registration within cluster scenario.

btw, could you please provide some configuration template which is needed for cluster scenario. It would be greatly appreciated. 

Message 6 of 11
Highlighted
Polycom Employee & Community Manager

Re: Polycom phones looses registration within cluster scenario.

Hello @zbazarov 

 

Information on Re-registration on failover can be found >here< or >here<

 

Best regards

 

Steffen Baier

----------------

Notice: This community forum is not an official Poly support resource, thus responses from Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge. If you need immediate and/or official assistance please open a service ticket through your proper support channels.
Please also ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's
Message 7 of 11
Highlighted
Occasional Advisor

Re: Polycom phones looses registration within cluster scenario.

Thanks, we have configured it, going to monitoring while weekend.. Additional issue what we have faced now - polycom is rejecting calls with '400 bad request'

Should we disable request validation for cluster at all? 
Currently we are using requestValidation by Invite method.


should we do smth like this:

voIpProt.SIP.requestValidation.1.method="Null"
voIpProt.SIP.requestValidation.1.request="Null"
voIpProt.SIP.strictUserValidation="1"



Or maybe you have better solution..  
Thanks.

Message 8 of 11
Highlighted
Occasional Advisor

Re: Polycom phones looses registration within cluster scenario.

and also I'm not able to set

voIpProt.SIP.outboundProxy.failOver.onlySignalWithRegistered="1" 
on polycom vxx411

Message 9 of 11
Highlighted
Occasional Advisor

Re: Polycom phones looses registration within cluster scenario.

 

Exported configuration from vxx411 after enabling PROFO:

 

<ALL
		attendant.behaviors.display.spontaneousCallAppearances.normal="0"
		call.callWaiting.ring="ring"
		call.defaultTransferType="Blind"
		device.prov.serverName.set="1"
		device.prov.ztpEnabled="0"
		device.prov.ztpEnabled.set="1"
		device.set="1"
		dialplan.digitmap="911|933T|411T|1[2-9]xx[2-9]xxxxxx|[2-9]xx[2-9]xxxxxxT|[2-9]xxxxxxT|011xxxxxxx.T|*xx.T|[2345678]xxxT"
		dialplan.digitmap.timeOut="3|3|3|3|3|3|3|3|3"
		dialplan.impossibleMatchHandling="2"
		feature.enhancedFeatureKeys.enabled="1"
		feature.presence.enabled="1"
		feature.urlDialing.enabled="0"
		lineKey.reassignment.enabled="1"
		nat.keepalive.interval="20"
		ptt.pageMode.displayName="1033_QA"
		ptt.pageMode.enable="1"
		ptt.volume="0"
		se.rt.custom1.name="Ring Answer"
		se.rt.custom1.ringer="10"
		se.rt.custom1.timeout="650"
		se.rt.custom1.type="ring-answer"
		softkey.feature.buddies="0"
		softkey.feature.directories="0"
		softkey.feature.mystatus="0"
		softkey.feature.newcall="0"
		tcpIpApp.port.rtp.mediaPortRangeStart="10000"
		tcpIpApp.sntp.address="time.google.com"
		tcpIpApp.sntp.address.overrideDHCP="1"
		tcpIpApp.sntp.gmtOffset="-18000"
		tcpIpApp.sntp.gmtOffset.overrideDHCP="1"
		up.oneTouchVoiceMail="1"
		voice.handset.st="10"
		voice.headset.st="10"
		voice.volume.persist.handset="1"
		voice.volume.persist.headset="1"
		voIpProt.SIP.allowTransferOnProceeding="0"
		voIpProt.SIP.outboundProxy.address="domain_here"
		voIpProt.SIP.outboundProxy.failOver.reRegisterOn="1"
		voIpProt.SIP.outboundProxy.port="port_here"
		voIpProt.SIP.strictUserValidation="1"
		attendant.resourceList.1.callAddress="1030"
		attendant.resourceList.2.callAddress="1031"
		attendant.resourceList.3.callAddress="79001"
		attendant.resourceList.4.callAddress="79002"
		attendant.resourceList.5.callAddress="79003"
		efk.efklist.1.action.string="*765$P1N4$#"
		efk.efklist.1.label="Transfer to Voicemail"
		efk.efklist.1.mname="xfervm"
		efk.efklist.1.status="1"
		efk.efkprompt.1.label="Extension:"
		efk.efkprompt.1.status="1"
		efk.efkprompt.1.type="numeric"
		lineKey.1.category="Line"
		lineKey.2.category="SpeedDial"
		lineKey.3.category="SpeedDial"
		lineKey.4.category="SpeedDial"
		lineKey.5.category="SpeedDial"
		lineKey.6.category="SpeedDial"
		lineKey.7.category="SpeedDial"
		lineKey.8.category="SpeedDial"
		lineKey.9.category="SpeedDial"
		lineKey.10.category="SpeedDial"
		lineKey.11.category="SpeedDial"
		lineKey.12.category="SpeedDial"
		lineKey.1.index="1"
		lineKey.2.index="1"
		lineKey.3.index="2"
		lineKey.4.index="3"
		lineKey.5.index="4"
		lineKey.6.index="5"
		lineKey.7.index="6"
		lineKey.8.index="7"
		lineKey.9.index="8"
		lineKey.10.index="9"
		lineKey.11.index="10"
		lineKey.12.index="11"
		msg.mwi.1.callBack="*95"
		msg.mwi.1.callBackMode="contact"
		msg.mwi.1.subscribe="username"
		ptt.pageMode.group.1.label="Page ALL"
		reg.1.address="username"
		reg.1.auth.userId="username"
		reg.1.label="test user"
		reg.1.outboundProxy.port="5078"
		softkey.1.action="!xfervm"
		softkey.2.action="9999$Tinvite$"
		softkey.1.enable="1"
		softkey.2.enable="1"
		softkey.2.insert="4"
		softkey.1.label="Xfer VM"
		softkey.2.label="Page"
		softkey.1.use.active="1"
		softkey.2.use.dialtone="1"
		softkey.1.use.hold="1"
		softkey.2.use.hold="1"
		softkey.2.use.idle="1"
		voIpProt.server.1.address="domain_here"
		voIpProt.server.1.port="port_here"
		voIpProt.server.1.register="0"
		voIpProt.SIP.alertInfo.1.class="custom1"
		voIpProt.SIP.alertInfo.1.value="Ring Answer"
		voIpProt.SIP.requestValidation.1.method="source"
		voIpProt.SIP.requestValidation.1.request="INVITE"
		reg.1.server.1.address="domain_here"
		reg.1.server.1.port="port_here"
	/>


Actually vxx411 is not able to apply this:

voIpProt.SIP.outboundProxy.failOver.failRegistrationOn="1"
voIpProt.SIP.outboundProxy.failOver.onlySignalWithRegistered="1"

 

Message 10 of 11