cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3343
Views
0
Helpful
6
Replies

SOLVED: SPA2102, WRP400, SPA8000, SRP521 and SRP521-U FAX NSE fails with empty Payload c0000000

aemcomcco
Level 1
Level 1

Hi Experts.

In my SIP network there is a Cisco PGW 9.6(1) used as PSTN gateway. PGW call agent controls many Cisco AS5400 via MGCP. We use Linksys SPA2102 to connect fax and modem devices.


Both PGW and AS5400 are configured to support FAX passthrough upspeeding via NSE event. Also SPA2102 devices are configured to support FAX passthrough NSE.

After many tests and debugs I see that SPA2102 doesn't recognize NSE event sent from AS5400.

From debug and wireshark traces you can see that AS5400 sends NSE 192 event correctly (see attachments).

So I've try to compare this scenario with a working one. The only difference is in the Payload content of NSE messages.
With AS5400 the Payload is c0000000. I think tath this is an empty payload while with different gateway or ATA the payload is c096c4e. In this last case SPA detects correctly NSE message.

Is this a BUG of SPA2102?

Thanks.

6 Replies 6

Alberto Montilla
Cisco Employee
Cisco Employee

Dear Sir;

I've escalated your question, you will receive a response shortly.

Regards
Alberto

Hi Alberto, have you got a news for us?

Thanks.

Hi, I've studied NSE messages.
The Payload Type present in RTP Header 100 is right. Also RTP Payload c0000000 is right.

In my case the RTP Payload is c0000000 where c0 = NSE 192 but the rest is all 0 (see pcap file attached in the first post).

I think that SPA2102 doesn't understand NSE RTP Payload with all 0.

I've attached new logs from SPA.

Thanks.

Hi Alberto, I worked with Nelso Seto and developers for this bug on WRP400.
It was described in issue CSCtk46492 and resolved with beta firmware WRP400_2.00.16_000_120610_1543_FCC.bin.

Can you replace the same bug fix on SPA2102 too?

Thanks.

Hi experts, I updated this post after several months because we need information about the status of this issue.
Now we are using the firmware 2.00.21 for WRP400 (a beta) and the firmware 5.2.10 for SPA2102 devices.
No news about next release of WRP400 and the last software for SPA 5.2.12 doesn't fix this issue.


Now we must take a decision for buying thousand CPE for current year. If this issue will not fixed during this month we will be forced to change products and vendor !!!


I hope in a your positive response.

Regards.

SPA2102: fixed in firmware 5.2.13

WRP400: fixed in firmware 2.00.21

SPA8000: fixed in firmware 6.1.11

SRP521: fixed in firmware 1.1.26

SRP521-U: fixed in firmware 1.2.4

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: