SPA-3102 stops answering incomming calls

g_strasser · ‎11-06-2009

My SPA-3102 registers with the service provider and seems to work fine. After a wile it stops answering incoming calls. Outgoing seams to be OK, and after a outgoing call the incoming calls seems to be forwarded to the POTS ports. This is the sys log while I have difficulties:

Nov 06 07:35:55 192.168.1.101 ;tag=d6d99377bf845e51o0 To: 9994172560 <sip:9994172560@CMTor1.ciktel.com> Call-ID: 229fb359-7b58ef21@127.0.0.1 CSeq: 42674 REGISTER Max-Forwards: 70 Authorization: Digest username="CIK4490352021",realm="64.34.25.118",nonce="4BB96409FE7CA9F75EDC6CC1BD473D87",uri="sip:CMTor1.ciktel.com",algorithm=MD5,response="7c2e6cd5dc880d52330536b466928422",opaque="0D598FA94A7EB99365626E8CEAFBFAA6" Contact: 9994172560 <sip:9994172560@192.168.1.101:5060>;expires=3600 User-Agent: Linksys/SPA3102-5.1.10(GW) Content-Length: 0 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER Supported: x-sipura, replaces

Nov 06 07:35:55 192.168.1.101

Nov 06 07:35:55 192.168.1.101 [0]<<64.34.25.118:5060(469)

Nov 06 07:35:55 192.168.1.101 ;tag=d6d99377bf845e51o0 To: "9994172560" <sip:9994172560@CMTor1.ciktel.com> Call-ID: 229fb359-7b58ef21@127.0.0.1 CSeq: 42674 REGISTER Contact: "9994172560" <sip:9994172560@192.168.1.101:5060>;expires=300 User-Agent: Linksys/SPA3102-5.1.10(GW) Allow: ACK, NOTIFY, OPTIONS, REFER, INFO, BYE, CANCEL, INVITE Content-Length: 0

Nov 06 07:35:55 192.168.1.101

Nov 06 07:35:55 192.168.1.101 [0]RegOK. NextReg in 296 (1)

07:36 AM: [693] 07:36:56 /cygdrive/c/temp>

mv syslog.log syslog.log1

07:37 AM: [694] 07:37:04 /cygdrive/c/temp>

tail -f syslog.log

Nov 06 07:47:58 192.168.1.101

Nov 06 07:47:59 192.168.1.101

Nov 06 07:47:59 192.168.1.101 [0]<<64.34.25.118:5060(469)

Nov 06 07:47:59 192.168.1.101 ;tag=622eb7feb50eab7ao0 To: "9994172560" <sip:9994172560@CMTor1.ciktel.com> Call-ID: fb6dca53-1d843472@127.0.0.1 CSeq: 14563 REGISTER Contact: "9994172560" <sip:9994172560@192.168.1.101:5060>;expires=300 User-Agent: Linksys/SPA3102-5.1.10(GW) Allow: ACK, NOTIFY, OPTIONS, REFER, INFO, BYE, CANCEL, INVITE Content-Length: 0

Nov 06 07:47:59 192.168.1.101

Nov 06 07:47:59 192.168.1.101 [0]RegOK. NextReg in 296 (1)

Nov 06 07:47:59 192.168.1.101 [1]RegOK. NextReg in 296 (1)

Nov 06 07:47:59 192.168.1.101 AUD:Stop PSTN Tone

Nov 06 07:49:23 192.168.1.101 AUD:Stop PSTN Tone

Nov 06 07:49:34 192.168.1.101 AUD:Stop PSTN Tone

Nov 06 07:49:42 192.168.1.101 [0]Off Hook

Nov 06 07:49:43 192.168.1.101 [0]On Hook

Nov 06 07:49:50 192.168.1.101 AUD:Stop PSTN Tone

Nov 06 07:50:02 192.168.1.101 AUD:Stop PSTN Tone

Nov 06 07:50:15 192.168.1.101 AUD:Stop PSTN Tone

Nov 06 07:50:16 192.168.1.101 CC:Clean Up

Nov 06 07:50:16 192.168.1.101 --- OBJ POOL STAT ---

Nov 06 07:50:16 192.168.1.101 OP:RTPRXB = 96 ( 96 192)

Nov 06 07:50:17 192.168.1.101 OP:RTPREB = 40 ( 40 48)

Nov 06 07:50:17 192.168.1.101 OP:RTPTXB = 64 ( 64 108)

Nov 06 07:50:17 192.168.1.101 OP:TIMEOU = 109 (120 52)

Nov 06 07:50:17 192.168.1.101 OP:SIPCOR = 0 ( 1 28)

Nov 06 07:50:17 192.168.1.101 OP:SIPCTS = 32 ( 32 1140)

Nov 06 07:50:17 192.168.1.101 OP:SIPSTS = 31 ( 32 6620)

Nov 06 07:50:17 192.168.1.101 OP:SIPAUS = 4 ( 8 588)

Nov 06 07:50:17 192.168.1.101 OP:SIPDLG = 10 ( 10 148)

Nov 06 07:50:17 192.168.1.101 OP:SIPSES = 12 ( 12 9520)

Nov 06 07:50:17 192.168.1.101 OP:SIPREG = 2 ( 4 296)

Nov 06 07:50:17 192.168.1.101 OP:SIPLIN = 0 ( 2 140)

Nov 06 07:50:17 192.168.1.101 OP:SUBDLG = 2 ( 2 6444)

Nov 06 07:50:17 192.168.1.101 OP:STUNTS = 16 ( 16 68)

Nov 06 07:50:17 192.168.1.101 OP:XMNODE = 1024 (1024 112)

Seems that the box is losing buffers ?!!

jestowe · ‎11-06-2009

Thank you for visiting Cisco Community Forums.

Please setup the Debug log and let's take a look at that. Under the System Tab, enter your IP beside Debug server, and then set Debug Level to 3. Then on Line 1 and PSTN line, set SIP Debug Option to "Full".

Thanks.

Jeff.

Alberto Montilla · ‎11-17-2009

Dear Sir;

This looks like the UDP ports is being closed by the router. Try the following:

- Go to [Line 1] and set NAT keepalive Enable to YES.

- Submit changes

- Reboot the device.

This should solve your issue.

Regards
Alberto

g_strasser · ‎11-17-2009

After removing the "sip" configuration from the PSTN screen, the issue got fixed.

The SIP registration entrie on the LINE1 & PSTN pages is confusing. The manual does not help much too.

Logicaly:

LINE1 - is servised by the SIP telephone service provider

PSTN - is srviced by the POTS port - why on earth the PSTN menu has configurable SIP server