[SIPForum-discussion] Problem with fax communication

[Ayyanar PK]

 Hi Trung Do,Thanks for the suggestions, but I have seen the fax working with same speed 9600 and with more media attributes. The fax call works very rarely and fails most of the time. See the working trace too, which is much similar to the nonworking. I captured the trace on only one end for the OK scenario (i.e Calling side)Regards,Ayyanar Original message From:trungdo< trungdo at patton.com >Date: 19 Aug 09 11:31:20Subject:Re: [SIPForumdiscussion] Problem with fax communicationTo: Ayyanar PKHi Ayyanar,The problem seem be from Calling site. He send invite message 2 time.The first time in frame 31 is normally. The second time is frame 34 with username and password ( you can remove the codec G.723 )And the third time is frame 49 with only codec G.711A ).The second problem is from SIP server ( it’s Asterisk server right )The called send invite message switch to T.38 with speed 14400 but when this message went though SIP server, the SIP server only send to calling site with spee
 d 9600. The second issue that the SIP server send SIP 200 OK with SDP T.38 have many media Attribute ?The calling site didn’t receiver all V.21 preable frame and DNS message ?Please check again your confiugre T.38 in SIP server.ThanksTrung DoTrung Do Systems Engineer APAC Patton Electronics email: trungdo at patton.com Cell Phone: +84.12.1981.0108 Ofc. +848 6290 6264Ext. 224 Fax. +848 3827 2688 sky: trungdo.tien MSN: trungdo.tien at hotmail.com website: www.patton.com On 8/19/09 12:38 PM, "Ayyanar PK"wrote:he traces were captured from both the calling and called end 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20090819/eca6d062/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: t38_ok_pub.pcap
Type: application/octet-stream
Size: 0 bytes
Desc: not available
URL: <http://sipforum.org/pipermail/discussion/attachments/20090819/eca6d062/attachment-0002.obj>