SPA8800 can not send and recive RTP packets.

[DarkPrinceRGS]

I create case ID: 638671195.

We have a problem with the SPA8800 configuration. Logical topology: CUCM <-> Asterisk <-> SPA8800. Firmware on device 6.1.11(XU). The configuration files in the attachment. 

The problem is not permanent. These three connections are one installed normally. I create mirroring port on SPA8800 and get packet dump. The dump file in the attachment. According dump shows that the device does not receive or send RTP stream, but forms ICMP package unreachable. 

Also, the web interface stops working after 20-30 minutes. This problem is persistent.

I hope that I could interest you. Thank you.

[Philip D'Ath]

Yucky.  That sounds like a software bug.  It does not sound like it is going to be resolved very easily.

If you have a thick skin and a Cisco Maintenance contract you could try logging a case with Cisco TAC.

[Dan Lukes]

I analyzed the dump you provided. There's just one ICMP Destination unreachable, the subcode "Fragmentation needed". Such kind of packet is required by TCP protocol and it mean no issue of any kind.  RTP use no TCP so neither TCP stream nor the ICMP in question seems to be related to a SIP call.

CSC is volunteer forum. Volunteers have no access to content of support tiskets. And Cisco support staff never respond here. So you need describe the issue in full. Captured dump is valuable, but you should comment it. May be a call captured has not received RTP stream, but I found no such call.

[DarkPrinceRGS]

settings for ease of analysis 

 filter (ip.src == 10.35.122.62) or (ip.dst == 10.35.122.62)

VoIP Calls 

Start packet No 943

The package contains an error No 961

[Dan Lukes]

I see the Asterisk is claiming 10.35.1.34 to be source IP, but the RTP stream have source IP of 10.35.1.53. Thus the RTP packet is rejected as it has arrived from IP unrelated to the SIP session.

[DarkPrinceRGS]

At first I thought so, too.

I add row in config file "canreinvite = no" and create new dump.

[Dan Lukes]

Well, now it look like SPA8800 issue with no doubt. But I see nothing special in the Asterisk's INVITE that can explain it.

Turn on syslog&debug (highest level) and catch them. May be it will help us to identify the cause.

[DarkPrinceRGS]

New dump and full syslog&debug

2 call. The first call fails, a second call is good.

[Dan Lukes]

 ---- Call 1, failing --------------

[ 788] Asterisk's INVITE claim audio endpoint to be 10.35.1.34:17762

[ 800] SPA8800 allocate socket pair 10.35.122.62:16386-7

[ 840] SPA8800 200 OK response claim audio endpoint to be 10.35.122.62:16386

[ 854] SPA8800 claim connection to 10.35.1.34:17762 failed,

[xxx] no RTP packets sent by SPA8800

[ 859] first RTP packed arrived from Asterisk - rejected

 ---- Call 2, success --------------

[1575] Asterisk's INVITE claim audio endpoint to be 10.35.1.34:28266

[1587] SPA8800 allocate socket 16388

[1670] SPA8800 200 OK response claim audio endpoint to be 10.35.122.62:16388

[xxxx] No 'connection failed' warning (it belong just before [1684])

[1686] first packet sent from SPA8800

[1689] first packet received from Asterisk, no issue

---

Well, I see no difference in call setup but port number.

It look like firmware bug. You should call SMB support center.

As a workaround, you may try change the port number range used by Asterisk not to overlap with range used by SPA8800. Try range 25000-29000. See this for more. Or you can shift range used by SPA8800 (RTP Port Min/RTP Port Max options). Remember to modify firewall (if any) accordingly.

Such workaround may or may not help.

[DarkPrinceRGS]

This setting does not help. I will call SMB support center.