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

SPA 112 rejecting incoming calls (TP Parser error: 15)

Hi,

I have two SPA 112 that can be registered without problems.But they are not accepting incoming calls and reject them with the following error code (TP Parser error: 15)

[0]<<10.174.86.146:5060(1065)
[0]<<10.174.86.146:5060(1065)
INVITE sip:991999999201@10.10.20.10:5060 SIP/2.0 Via: SIP/2.0/UDP 10.174.86.146:5060;branch=z9hG4bK46i41g206g9gjo46q7q0.1 Max-Forwards: 68 From: "991999999200" <sip:991999999200@domain.com>;tag=SDi0gf101-mavodi-0-7e-34-3-ffffc07f-_000000000000-4d0c-3a649710-69-5321caa8-41908 To: sip:991999999201@domain.com Call-ID: SDi0gf101-440d1389c67eef03ae3def6570ba277c-cd5ec61 CSeq: 1 INVITE Contact: <sip:991999999200@10.174.86.146:5060;transport=udp> Supported: replaces P-Asserted-Identity: sip:991999999200@domain.com User-Agent: Cisco/SPA112-1.0.2 (006) Allow: ACK Allow: BYE Allow: CANCEL Allow: INFO Allow: INVITE Allow: NOTIFY Allow: OPTIONS Allow: REFER Content-Length: 335 Content-Type: application/sdp  v=0 o=- 1377483 1377483 IN IP4 10.174.87.146 s=- c=IN IP4 10.174.87.146 t=0 0 m=audio 10244 RTP/AVP 0 2 8 18 100 101 a=rtpmap:0 PCMU/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729a/8000 a=rtpmap:100 NSE/8000 a=fmtp:100 192-193 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:30 a=sendrecv

TP Parser error: 15 

This issue seems to affect incoming calls only, as ATAs are able to make outgoing calls destinated to other devices. 

Can someone help to clarify why incoming calls are rejected with that error code?

Thanks

Everyone's tags (2)
3 REPLIES
VIP Gold

There is something in the

There is something in the INVITE packet that will make SPA112 unhappy.
 

Not so helpfull response, isn't it ? But I have advice despite I can't analyze the problem just now.

 

The firmware 1.0.2(006) is not ready for production. I'm not speaking about few problems - it just doesn't work most of time. Upgrade to latest firmware and try again.

 

I'm almost sure you problem will not survive the upgrade.

New Member

Hi Dan,Thanks for the

Hi Dan,

Thanks for the response.

Both SPAs have been upgraded to 1.3.3 firmware and still facing the same issue. Please find below a new call log (this time originating device is a 3CX softphone)

 

INVITE sip:201999999201@10.10.20.10:5060 SIP/2.0 Via: SIP/2.0/UDP 10.174.86.146:5060;branch=z9hG4bK9nvl3720c8k140bg5240.1 Max-Forwards: 68 From: "201999999203" <sip:201999999203@domain.com:5060>;tag=SDl025601-mavodi-0-7e-1e-3-ffffc07f-_000000000000-54cd-ce781710-37-53295d93-4118b To: sip:201999999201@domain.com:5060 Call-ID: SDl025601-5e31d94405e98f62723f8af3c383d196-cd5ec61 CSeq: 1 INVITE Contact: <sip:201999999203@10.174.86.146:5060;transport=udp> Supported: replaces P-Asserted-Identity: sip:201999999203@domain.com User-Agent: 3CXPhone 6.0.26523.0 Allow: INVITE Allow: ACK Allow: CANCEL Allow: OPTIONS Allow: BYE Allow: REGISTER Allow: SUBSCRIBE Allow: NOTIFY Allow: REFER Allow: INFO Allow: MESSAGE Content-Length: 407 Content-Type: application/sdp  v=0 o=3cxVCE 275886060 104302905 IN IP4 10.174.87.146 s=3cxVCE Audio Call c=IN IP4 10.174.87.146 t=0 0 m=audio 11904 RTP/AVP 0 8 3 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:3 GSM/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv m=video 11906 RTP/AVP 34 c=IN IP4 10.174.87.146 a=rtpmap:34 H263/90000 a=fmtp:34 QCIF=1;CIF=1;SQCIF=1;CIF4=1 a=sendrecv 

TP Parser error: 15

VIP Gold

Unfortunatelly, it's not

Unfortunatelly, it's not possible to analyze the issue from the INVITE you posted here. "Parser error" mean there is something wrong with formatting of the packet - missing or excessive line delimiter, some wrong characetr, including the non-printable one or so. But formatting is destroyed already on text you posted as well as exact lien delimiters as well as possible non-printable chars.

You need to catch the INVITE in question by a packet dumper. Then attach it here as binary dump.

Installing and Using Wireshark for Capturing Network Traffic

 

311
Views
0
Helpful
3
Replies
CreatePlease to create content