AS5400hpx SIP Fax Relay Problems

Unanswered Question
Mar 8th, 2010
User Badges:

Hello,

I'm trying to use t.38 fax relay with our as5400hpx.

It's running 12.4(19)

I'm also running 10.9.0 for spe firmware


I am recieving the following as soon as the t.38 negotiation completes. (fax t.30 debugging is on)

The call is hungup immediatly.

It doesn't matter if it's inbound or outbound.



.Mar  8 13:49:24.409: %NP-3-NAKRSP: NAK Response Received - command 0xF201, result code 0x800E, msg id 0xF2FF, session id 0x1B1, msg tag 0x0, slot/port 4/1
.Mar  8 13:49:26.409:   34w4d   : Module Trace Event:
.Mar  8 13:49:26.409:      Module     : 4/0/0
.Mar  8 13:49:26.409:      Trace Event: 0x7
.Mar  8 13:49:26.409:      Data Format: ASCII
.Mar  8 13:49:26.409:      Data Len   : 110
.Mar  8 13:49:26.409:      Data       : EST:INVALID_PARAMETER_VALUE Session_ID: 0x01b1 Message_ID: 0xf201 Serv
ice: 0x16000000 ID: 0x0001 Value: 0x009b
.Mar  8 13:49:26.409: %NP_EST-6-CTRL_NAK_RSP: (NP address 4/0/0/255), Msg ID=0xF201, Result=INVALID_PARAMETER_VALUE, Data format=Binary, Data len=44, Data=00 0B 01 B1 00 00 F2 01 00 08 00 00 00 00 00 06 00 01 00 9B 00 02 00 00 00 04 FF F6 00 05 00 01 00 0D 00 00 00 11 00 00 00 0E 00 00



Here is the relevant config info.


voice service pots
fax protocol t38 ls-redundancy 1 hs-redundancy 1 fallback pass-through g711ulaw
!
voice service voip
redirect ip2ip
fax protocol t38 ls-redundancy 1 hs-redundancy 1 fallback pass-through g711ulaw
h323
  call service stop
sip
!

dial-peer voice 4281 voip
service session
destination-pattern XXXXXXXXXX$
translate-outgoing called 1
rtp payload-type cisco-fax-relay 99
rtp payload-type cisco-codec-fax-ind 98
voice-class codec 1
session protocol sipv2
session target ipv4:xxx.xxx.xxx.xxx
session transport udp
dtmf-relay rtp-nte
fax rate 14400

fax protocol t38 ls-redundancy 1 hs-redundancy 0 fallback none
ip qos dscp 5 media
no vad
!

sip-ua
no remote-party-id
retry invite 3
retry response 3
retry bye 3
retry cancel 3
timers trying 1000
timers buffer-invite 5000
sip-server ipv4:xxx.xxx.xxx.xxx
!

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Daniele Giordano Sun, 04/04/2010 - 10:36
User Badges:
  • Gold, 750 points or more

Try to use wireshark. It's more usefull and easy during debug. You can see SIP Session negotiation and T.38 phase.


From your output I think that the problem is a SIP malformed message but I'm not sure: ...Result=INVALID_PARAMETER_VALUE, Data format=Binary, Data len=44, Data=00  0B 01 B1 00 00 F2 01 00 08 00 00 00 00 00 06 00 01 00 9B 00 02 00 00 00  04 FF F6 00 05 00 01 00 0D 00 00 00 11 00 00 00 0E 00 00...

Attachment: 

Actions

This Discussion