Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

SPA112 FW bug confirmed: registration broken during and after outbound call

After receiving and configuring my new SPA112, everything seemed to work out just fine: registration to the SIP proxy, inbound calls, etc. However, at some point I discovered that outbound calls would typically only work for a certain amount of time, after which the connection to the callee would be lost, just like the my registration to the SIP proxy. In the SPA112's Web interface, the device reports "Registration State: Failed" in such cases. Only a reboot of the device will result in a successful registration again. Firmware version: 1.3.5(004).

To diagnose the problem, I enabled both syslog and debug logging and started capturing and analyzing what is going wrong:

[Before call]
SIP.REGISTER
SIP.TRYING
SIP.UNAUTHORIZED (with nonce)
SIP.REGISTER
SIP.TRYING
SIP.OK

Also the debug logging reports "LOCAL3.DEBUG: [0]RegOK. NextReg in X".

So far, so good.

[During/after call]

We see two (periodic) registration sequences:

SIP.REGISTER
SIP.TRYING
SIP.UNAUTHORIZED (with nonce)
LOCAL3.DEBUG: SIP_tsClientEventProc(event: 28)
LOCAL3.DEBUG: SIP_regTsEventProc(event: 28)
LOCAL3.DEBUG: SIP_tsClientEventProc(event: 28)
LOCAL3.DEBUG: SIP_regTsEventProc(event: 28)
LOCAL3.DEBUG: SIP_regTsEventProc(event: 28)
LOCAL3.DEBUG: SIP_tsCreateClient()
SIP.REGISTER
SIP.TRYING
LOCAL3.DEBUG: SIP_tsClientEventProc(event: 28)
LOCAL3.DEBUG: SIP_regTsEventProc(event: 28)
SIP.OK
LOCAL3.DEBUG: SIP_tsClientEventProc(event: 28)
LOCAL3.DEBUG: SIP_regTsEventProc(event: 28)
LOCAL3.DEBUG: [0]RegOK. NextReg in X

Which is OK and the same as before the call. This one is however shortly followed by the following (second registration sequence of) debug messages:

LOCAL3.DEBUG: SIP_tsClientEventProc(event: 4)
LOCAL3.DEBUG: tryAltIp_delay()
LOCAL3.DEBUG: RSE_DEBUG: getting alternate from domain:<proxy>
LOCAL3.DEBUG: SIP_regTsEventProc(event: 4)
LOCAL3.DEBUG: SIP_regTsEventProc(event: 32)
LOCAL3.DEBUG: 2. RSE:GetServerAddrErr(<proxy>,0)=-101
LOCAL3.DEBUG: SIP_tsCreateClient(), 1781, uiTmrF=1600, SIP_TMR_F_INIT=1600
LOCAL3.DEBUG: [0]Reg Addr Change(0) 29dfc552:5060->0:5060
LOCAL3.DEBUG: tpError at [SIP_tsCreateClient:1817]

These two registration sequences (regular SIP messages at the one hand and the debug messages at the other hand) are alternating, and the succesfull registration is followed by the failing registration in a short time, so most typical state is "Failed".

Any suggestion on what I could try to solve the issue is welcome!

5 REPLIES
VIP Gold

I'm able to reproduce the

I'm able to reproduce the problem in my test lab.

It seems that device can't fetch IP address of the SIP proxy from it's internal cache during active call (GetServerAddrErr error -101). And the issue doesn't solve in full even after the calls end.

It is not networking issue between device and DNS server as no DNS query has been issued (the IP address is cached from previous query that has been responded successfully).

 

As a workaround I configured proxy IP instead of name.

 

It work.

 

It seems we hit (another) firmware bug.

 

New Member

Thanks for your reply, Dan! I

Thanks for your reply, Dan! I can confirm that using the proxy's IP address instead of FQDN resolves the issue of failing registrations.

New Member

Just got the following reply

Just got the following reply from Cisco support:

The device does not support FQDN and you need to specify the proxy address. Hence the device is functioning as it should.

I will go ahead and close this case.

VIP Gold

If the option is intended to

If the option is intended to be set to IP address, it should not accept name - and work with it partially. So it may not be bug itself, but it's error prone behavior with no doubt.

 

And such feature should be clearly described in documentation.  So if it's not recognized as bug in documentation, it should be recognized as lack of documentation.

 

Of course "it work as expected" is most unearned answer ...

 

VIP Gold

See also: Problem with

562
Views
5
Helpful
5
Replies
CreatePlease to create content