So is T38Gateway designed to bridge two T.38 channels? What if one wants to "originate" T38? I don't wish to depend on someone to do the translation for me, the goal would be to replace Asterisk with OpenPBX as PRI gateway.
Here is the full log, ATA sends T38 INVITE, OpenPBX sends 488 not acceptable --- (9 headers 0 lines) --- web04*CLI> <-- SIP read from 64.238.173.171:5060: INVITE sip:[EMAIL PROTECTED] SIP/2.0 From: "Line 1"<sip:[EMAIL PROTECTED]>;tag=100c4488-24fba8c0-13c4-45c6fe22-56a9a201-45c6fe22 To: "13525054734"<sip:[EMAIL PROTECTED]:5060>;tag=as61f1af6e Call-ID: [EMAIL PROTECTED] CSeq: 5 INVITE Via: SIP/2.0/UDP 64.238.173.171:5060;rport;branch=z9hG4bK-45c6fe42-91513385-6cd8a7a2 Max-Forwards: 70 Supported: replaces Contact: <sip:[EMAIL PROTECTED]:5060;transport=UDP> Proxy-Authorization: Digest username="00908F03206D-L1",realm="openpbx.org",nonce="11bdc0c7",uri="sip:[EMAIL PROTECTED]",response="1e9936db2ba6661c5e610515b316c370",algorithm=MD5 Content-Type: application/sdp Content-Length: 269 v=0 o=rtp 1170669145 1170669148 IN IP4 192.168.251.36 s=- c=IN IP4 5004 t=0 0 m=image 5004 UDPTL t38 a=T38FaxVersion:0 a=T38MaxBitRate:14400 a=T38FaxMaxBuffer:1024 a=T38FaxMaxDatagram:122 a=T38FaxRateManagement:transferredTCF a=T38FaxUdpEC:t38UDPRedundancy --- (12 headers 12 lines) --- Using INVITE request as basis request - [EMAIL PROTECTED] Sending to 64.238.173.171 : 5060 (NAT) Feb 5 04:57:46 WARNING[1092139328]: chan_sip.c:4691 process_sdp: Unable to lookup host in c= line, 'IN IP4 5004' Transmitting (NAT) to 64.238.173.171:5060: SIP/2.0 488 Not acceptable here Via: SIP/2.0/UDP 64.238.173.171:5060;branch=z9hG4bK-45c6fe42-91513385-6cd8a7a2;received=64.238.173.171;rport=5060 From: "Line 1"<sip:[EMAIL PROTECTED]>;tag=100c4488-24fba8c0-13c4-45c6fe22-56a9a201-45c6fe22 To: "13525054734"<sip:[EMAIL PROTECTED]:5060>;tag=as61f1af6e Call-ID: [EMAIL PROTECTED] CSeq: 5 INVITE User-Agent: OpenPBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Max-Forwards: 70 Content-Length: 0 On 2/5/07, Mikael Bjerkeland <[EMAIL PROTECTED]> wrote: > man, 05,.02.2007 kl. 04.34 -0500, skrev Andrew Joakimsen: > > > I tried T38Gateway in following modes: > > > > > > PRI -> Cisco AS5350 -> SIP -> OpenPBX -> SpanDSP > > > ATA -> SIP -> OpenPBX -> SpanDSP > > > > Are you actually using the T38Gateway application? The AS5350 should > > support T.38 itself (and there's no reason not to use it) and the 2nd > > setup I assume you are using TxFax/RxFax? > > > > > > > I'm going to setup ZAP hardware at openpbx.org box and test this > > > issue. > > > > > I don't think it should be any different than sending the fax as ulaw > > over the LAN which is what I am trying to do. > > > > When I dial from the IAX to the SIP ATA via T38Gateway I get: > > > > WARNING[1094269248] app_t38gateway.c: Bridging frames > > > > When I dial from the SIP ATA to the IAX via T38Gateway I get: > > > > ERROR[1094003008] app_t38gateway.c: failed to get remote_channel > > IAX2/isphone-out/13525054732 > > This is possibly because T38Gateway only works with SIP. > > You should not use T38Gateway with IAX. OpenPBX.org does not support > T.38 with anything else than IAX. Connect your OpenPBX.org servers with > SIP and give it a new shot. > > > _______________________________________________ > > Openpbx-users mailing list > > [email protected] > > http://lists.openpbx.org/mailman/listinfo/openpbx-users > > _______________________________________________ > Openpbx-users mailing list > [email protected] > http://lists.openpbx.org/mailman/listinfo/openpbx-users > _______________________________________________ Openpbx-users mailing list [email protected] http://lists.openpbx.org/mailman/listinfo/openpbx-users
