Tandberg Endpoint fails to register to VCS-Control due to "out of resources"

[codbell]

Hello All,

I have a few codecs that I have seen this happen on and would like to see if I can find a reason why the codec is showing this error:

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2013.11.07 16:11:14 =~=~=~=~=~=~=~=~=~=~=~=
533713.72 SipStack I: SIPEVNOTIFY_Active_doSipEvNotify GO Inactive
533713.76 SipStack I: Applying new sip config received while old config was being applied.
533713.76 SipStack I: SIPEVNOTIFY_Active_doSipEvNotify GO Inactive
533714.05 SipReg W: Transport failed to send registration (sipexcept: 4 Out of resources)
533739.59 SipStack I: SIPEVNOTIFY_Active_doSipEvNotify GO Inactive
533739.61 SipStack I: Applying new sip config received while old config was being applied.
533739.61 SipStack I: SIPEVNOTIFY_Active_doSipEvNotify GO Inactive
533739.91 SipReg W: Transport failed to send registration (sipexcept: 4 Out of resources)
533774.86 SipReg W: Transport failed to send registration (sipexcept: 4 Out of resources)
533864.90 SipReg W: Transport failed to send registration (sipexcept: 4 Out of resources)
log output off

OK
log ctx SipPacket off

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2013.11.07 16:11:14 =~=~=~=~=~=~=~=~=~=~=~=

As you can see, the codec is seeing some "out of resources" error when attempting to register SIP. I have restarted the codec and SIP registered just fine. Since this has happened a few times already with different codecs, I am trying to see when/why this errors appears and have been unsuccessful so far.

Thank you,

Cody

[Chad Patterson]

Just curious,

How many registration licenses do you have on the VCS your systems register to?

[codbell]

we have 1500 licenses on the VCS-C and less than 300 endpoints. I believe this was actually caused from asynchronous routing, the endpoint was booting up and we could see intermittent connectivity issues to the VCS when it was taking multiple paths.