×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

SPA112 reinvites to T.38 on voice calls.

Unanswered Question
Jul 9th, 2013
User Badges:

We have many of these devices in the field.  Recently one has started behaving strangely.  When an outbound call is initally setup there will be brief audio and then the ATA will reinvite and start a T.38 fax session even though there are no fax tones in the audio.  The end user doesn't own a fax machine.  If a second call is placed it will go through just fine.


Any help tracking down why the ATA is switching to fax mode would be greatly appreciated.


Here are the relevant parts of the syslog output:

2013-07-09 13:51:42: HOSTNAME #012[Cordless] #012  ### Update channel function called #012RDRD p_rtp_EvntInit pMember 3758838576, pMember->bPtEvt 65#012RDRD p_rtp_EvntInit pMember 3758839544, pMember->bPtEvt 65#012Function p_rtpapp_UpdateChan;Line 3145; No Codec Restart: STATE CHANGE: to 2#012Function create_voice_message; Sending coma response 20#012D #012 [Cordless]

2013-07-09 13:51:42: RTP session 0 updated

2013-07-09 13:51:42: HOSTNAME uchSetDTMFMute(), ENABLE

2013-07-09 13:51:42: HOSTNAME #012[Cordless] #012  Inside  uch_ProcessReq  with Cmd 20 #012 CH_SMU_DLY FOR EP 2 and PARAM 1 #012 Sending Data from FIQ with SeqNum 20 NodeId 0 EP 0 Res 34 #012 IN FTUCH Inst 2 and XInfo 1 #012n #012 [Cordless]

2013-07-09 13:51:42: HOSTNAME [AUD]RTP Rx Up

2013-07-09 13:51:43: HOSTNAME [0:0]CC:ALLOC T38 0

2013-07-09 13:51:43: HOSTNAME [0]CC:Force T.38 FAX

2013-07-09 13:51:43: HOSTNAME dbg_tmp: initSdp bOneCodec: 0, sdp->ucNumCodec: 1

2013-07-09 13:51:43: HOSTNAME SIP_tsInviteClientEventProc(event:27)

2013-07-09 13:51:43: HOSTNAME SIP_tsInviteClientEventProc(event:27)

2013-07-09 13:51:43: HOSTNAME SIP_tsInviteClientEventProc(event:27)

2013-07-09 13:51:43: HOSTNAME SIP_tsInviteClientEventProc(event:27)

2013-07-09 13:51:43: HOSTNAME SIP:Peer Confirm T38

2013-07-09 13:51:43: HOSTNAME SIP:Peer Confirm T38

2013-07-09 13:51:43: HOSTNAME cordless_stop_rtp(), releasing RTP channel:0

2013-07-09 13:51:43: HOSTNAME #012[Cordless] #012 FTRTP: RTP_STOP_CHAN#012 ### $$$ RTCP MODE RX So do not send RTCP BYE #012Function p_rtpapp_Stop;Line 2817; STATE CHANGE: to 3#012 ## RTP STOP Total Pkt Recv 1239  Total pkt Dropped 0 #012return value of p_rtpapp_Stopis 0#012t #012 [Cordless]

2013-07-09 13:51:43: HOSTNAME #012[Cordless] #012  p_rtpapp_AUCCallback is getting called #012 p_rtpapp_AUCCallback is getting called #012 Posting FTRTP_ENCDEC_STOP event to FTRTP #012R #012 [Cordless]

2013-07-09 13:51:43: HOSTNAME #012[Cordless] #012  ENC/DEC stopped by DSP remove session and stop JB #012Function p_rtp_session_jb_stop;Line 2892; STATE CHANGE: to 4#012 #012 ##### AUC Channel STOPPED sending COMA REPLY ##### #012Function create_voice_message; Sending coma response 7#012G #012 [Cordless]

2013-07-09 13:51:43: HOSTNAME #012[Cordless] #012 Function create_voice_message; Sending coma response 16#012t #012 [Cordless]

2013-07-09 13:51:43: HOSTNAME [17517524.548000]  RTCP is running so calling rtcp stop

2013-07-09 13:51:43: HOSTNAME [17517524.548000]  chan->kmode is present not null

2013-07-09 13:51:43: HOSTNAME [17517524.556000]  ###### RTCP sock_sendmsg return 172

2013-07-09 13:51:43: HOSTNAME [17517524.560000]  ###### sock_sendmsg return 172

2013-07-09 13:51:43: HOSTNAME [17517524.560000]

2013-07-09 13:51:43: HOSTNAME [17517524.560000]  #### RTP STOP Flag set in this channel break ####

2013-07-09 13:51:43: HOSTNAME #012[Cordless] #012 Function create_voice_message; Sending coma response 9#012#012 #012 [Cordless]

2013-07-09 13:51:43: HOSTNAME cordless_stop_rtp(), RTP session 0 stopped succussfully

2013-07-09 13:51:43: staring T38 call cordless_start_t38

2013-07-09 13:51:43: HOSTNAME cordless_start_t38(), remote IP: 216.17.0.216 0

2013-07-09 13:51:43: T38 Remote IP 216.17.0.216 and port 4159

2013-07-09 13:51:43: T38 Remote IP 216.17.0.216 and port 4159

2013-07-09 13:51:43: HOSTNAME #012[Cordless] #012 Function create_voice_message; Sending coma response 1#012#012 #012 [Cordless]

2013-07-09 13:51:43: HOSTNAME ##### RTP_SEQ_NUM_EVT 4159

2013-07-09 13:51:43: HOSTNAME #012[Cordless] #012 Function create_voice_message; Sending coma response 3#012#012 #012 [Cordless]

2013-07-09 13:51:43: HOSTNAME #012[Cordless] #012 FTRTP: RTP_START_CHAN#012voice_start_chan: Request to start a T38 session#012 ### Allocating static mem for ptT38DPStatic ### #012 Node 0 ep1 2:ep1 3: Return EP1 l=  2 And Passed EP 3 #012 Other FXS EP 2 Connected to VoIP EP 3 #012 SSW INST 84d and SSR INST 827 #012t38_session_start: Started T38 chan 0 #012Function create_voice_message; Sending coma response 5#012d #012 [Cordless]


I have attached the full log as well.

Attachment: 
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
nseto Thu, 07/11/2013 - 15:36
User Badges:
  • Silver, 250 points or more

Can you try the latest 1.3.2 from cisco.com?

The log shows 1.3.1(003)

If still a problem, we'd need to see the wireshark and the unit config.

Steven Wheeler Mon, 07/15/2013 - 14:42
User Badges:

Thanks for the reply, I will give that a try and let you know what I find.


Edit: I am willing to provide the packet capture, but for privacy & security reasons I would prefer not to post it on this forum.

Steven Wheeler Mon, 06/02/2014 - 10:01
User Badges:

Sorry for taking so long to get back. We have a different customer experiencing the same problem. I have tried upgrading them to 1.3.3 (015) but they are still having problems. I would be happy to provide you with a packet capture of the call, but I am unable to post it publicly on the forum as it contains end user information. Can I send it to you directly?

Actions

This Discussion

Related Content