Menu ▾ ▴

Incoming T.38 Faxes get rejected with 488...

Help
clemix
2010-01-22
2013-05-28

  • clemix

    clemix - 2010-01-22

    my configuration: 

    T38Modem Version 1.2.0
 (OPAL-3.6.6/3.6.6, PTLIB-2.6.5/2.6.5) by Vyacheslav Frolov on Unix Linux (2.6.27-11-generic-i686)
$ ldd /opt/bin/t38modem 
        linux-gate.so.1 =>  (0xb7f07000)
        libopal.so.3.6.6 => /opt/opal/lib/libopal.so.3.6.6 (0xb777c000)
        libpt.so.2.6.5 => /opt/ptlib/lib/libpt.so.2.6.5 (0xb7527000)
        libpthread.so.0 => /lib/tls/i686/cmov/libpthread.so.0 (0xb750d000)
        librt.so.1 => /lib/tls/i686/cmov/librt.so.1 (0xb7504000)
        libldap_r-2.4.so.2 => /usr/lib/libldap_r-2.4.so.2 (0xb74c2000)
        liblber-2.4.so.2 => /usr/lib/liblber-2.4.so.2 (0xb74b4000)
        libssl.so.0.9.8 => /usr/lib/i686/cmov/libssl.so.0.9.8 (0xb746d000)
        libcrypto.so.0.9.8 => /usr/lib/i686/cmov/libcrypto.so.0.9.8 (0xb7320000)
        libexpat.so.1 => /usr/lib/libexpat.so.1 (0xb72f9000)
        libresolv.so.2 => /lib/tls/i686/cmov/libresolv.so.2 (0xb72e5000)
        libdl.so.2 => /lib/tls/i686/cmov/libdl.so.2 (0xb72e1000)
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb71f3000)
        libm.so.6 => /lib/tls/i686/cmov/libm.so.6 (0xb71cd000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb71bd000)
        libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0xb705f000)
        /lib/ld-linux.so.2 (0xb7eed000)
        libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0xb7047000)
        libgnutls.so.26 => /usr/lib/libgnutls.so.26 (0xb6faa000)
        libtasn1.so.3 => /usr/lib/libtasn1.so.3 (0xb6f98000)
        libz.so.1 => /usr/lib/libz.so.1 (0xb6f82000)
        libgcrypt.so.11 => /lib/libgcrypt.so.11 (0xb6f18000)
        libgpg-error.so.0 => /lib/libgpg-error.so.0 (0xb6f14000)

    Registrar: 192.168.10.14
    User: 310:test
    Local-IP: 192.168.10.200
    I start t38modem with: 

     sudo /opt/bin/t38modem --sip-listen 192.168.10.200 --sip-proxy 310:test@192.168.10.14 --sip-register 310@192.168.10.14,test --no-h323 -p +/dev/ttyzz  -u 310

    and after it is registered I send the fax with: 

    sudo /usr/bin/efax -d /dev/ttyzz -t my_fax.txt

    If I send a fax to t38modem I get the following SIP trace: 

    > INVITE sip:310@192.168.10.200 SIP/2.0
> Via: SIP/2.0/UDP 192.168.10.14:5060;branch=z9hG4bKF876BEF216BB2B10882B4D0BFFDDC601;rport
> From: 20 <sip:20@192.168.10.14;user=phone>;tag=4C68F76D0EBB2B1085B54D0BFFDDC601
> To: <sip:310@192.168.10.14;user=phone>
> Call-ID: 1C49BEF216BB2B10882A4D0BFFDDC601
> CSeq: 1 INVITE
> Contact: <sip:310@192.168.10.14:5060;transport=udp>
> Max-Forwards: 70
> Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, MESSAGE, SUBSCRIBE, PRACK, REFER
> Supported: 100rel, replaces, timer
> User-Agent: tr200bw
> Allow-Events: refer, message-summary, dialog
> P-Preferred-Identity: 20 <sip:20@192.168.10.14;user=phone>
> Session-Expires: 1800
> Content-Type: application/sdp
> Content-Length: 359
>
> v=0
> o=- 17317 1 IN IP4 192.168.10.14
> s=SIP call
> c=IN IP4 192.168.10.14
> t=0 0
> m=audio 10604 RTP/AVP 0 8 18
> a=rtpmap:0 PCMU/8000
> a=rtpmap:8 PCMA/8000
> a=rtpmap:18 G729/8000
> a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:3Nx0RBXXxor+qnXHuTCXYfTx2ur2CvKNrxFSqB4w
> a=crypto:2 AES_CM_128_HMAC_SHA1_32 inline:IS17B+a4ktBnbGjxzNnLZrlqZ0ht+X3qomjBBYq8
> a=sendrecv
< SIP/2.0 100 Trying
< CSeq: 1 INVITE
< Via: SIP/2.0/UDP 192.168.10.14:5060;branch=z9hG4bKF876BEF216BB2B10882B4D0BFFDDC601;rport
< From: 20 <sip:20@192.168.10.14;user=phone>;tag=4C68F76D0EBB2B1085B54D0BFFDDC601
< Call-ID: 1C49BEF216BB2B10882A4D0BFFDDC601
< To: <sip:310@192.168.10.14;user=phone>
< Contact: <sip:310@192.168.10.200>
< Content-Length: 0
< SIP/2.0 488 Not Acceptable Here
< CSeq: 1 INVITE
< Via: SIP/2.0/UDP 192.168.10.14:5060;branch=z9hG4bKF876BEF216BB2B10882B4D0BFFDDC601;rport
< User-Agent: T38Modem/1.2.0
< From: 20 <sip:20@192.168.10.14;user=phone>;tag=4C68F76D0EBB2B1085B54D0BFFDDC601
< Call-ID: 1C49BEF216BB2B10882A4D0BFFDDC601
< Organization: Vyacheslav Frolov
< To: <sip:310@192.168.10.14;user=phone>;tag=3ec9ed05-ce05-df11-95e9-0019d188fe1c
< Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING
< Content-Length: 0

    T38Modem just say: 

    Disabled H.323 protocol
Enabled audio formats for SIP (in preference order):
  G.711-uLaw-64k
  G.711-ALaw-64k
Waiting for incoming SIP calls from 192.168.10.200
Route table:
  modem:.*=sip:<dn>@192.168.10.14
Call[lf9db294f1] from sip:310@192.168.10.14;user=phone to sip:310@192.168.10.200, route to sip:udp$192.168.10.200:5060
Call[webeb21a02] from sip:310@192.168.10.14;user=phone to sip:310@192.168.10.200, route to sip:udp$192.168.10.200:5060
Call[lf9db294f1] cleared
Call[webeb21a02] cleared

    with -ttt I get following: 

    Call[i077b9bfd1] from sip:310@192.168.10.14;user=phone to sip:310@192.168.10.200, route to sip:udp$192.168.10.200:5060
2010/01/22 15:22:30.042         Pool:0xb6a79b90 Call[i077b9bfd1] from sip:310@192.168.10.14;user=phone to sip:310@192.168.10.200, route to sip:udp$192.168.10.200:5060
2010/01/22 15:22:30.042         Pool:0xb6a79b90 SIP     OnIncomingConnection succeeded for INVITE from sip:310@192.168.10.200 for Call[i077b9bfd1]-EP<sip>[685cf73d-cf05-df11-9d0f-0019d188fe1c]
2010/01/22 15:22:30.042         Pool:0xb6a79b90 Call    GetOtherPartyConnection Call[i077b9bfd1]-EP<sip>[685cf73d-cf05-df11-9d0f-0019d188fe1c]
2010/01/22 15:22:30.042         Pool:0xb6a79b90 Call    OnSetUp Call[i077b9bfd1]-EP<sip>[685cf73d-cf05-df11-9d0f-0019d188fe1c]
2010/01/22 15:22:30.042         Pool:0xb6a79b90 MySIPConnection::SetUpConnection Call[i077b9bfd1]-EP<sip>[04bbf73d-cf05-df11-9d0f-0019d188fe1c] name=310
2010/01/22 15:22:30.042         Pool:0xb6a79b90 MySIPConnection::SetUpConnection new name=20
2010/01/22 15:22:30.042         Pool:0xb6a79b90 SIP     SetUpConnection: sip:310@192.168.10.200
2010/01/22 15:22:30.042         Pool:0xb6a79b90 OpalCon SetPhase from UninitialisedPhase to SetUpPhase for Call[i077b9bfd1]-EP<sip>[04bbf73d-cf05-df11-9d0f-0019d188fe1c]
2010/01/22 15:22:30.043         Pool:0xb6a79b90 OpalUDP Binding to interface: 192.168.10.200:5060
2010/01/22 15:22:30.043         Pool:0xb6a79b90 OpalUDP Started connect to 192.168.10.14:5060
2010/01/22 15:22:30.047         Pool:0xb6a79b90 SIP     Creating INVITE request
[b]2010/01/22 15:22:30.047         Pool:0xb6a79b90 SIP     No media formats of type audio, not adding SDP
2010/01/22 15:22:30.047         Pool:0xb6a79b90 SIP     No media formats of type video, not adding SDP[/b]
2010/01/22 15:22:30.048         Pool:0xb6a79b90 OpalCon SetPhase from SetUpPhase to ReleasingPhase for Call[i077b9bfd1]-EP<sip>[04bbf73d-cf05-df11-9d0f-0019d188fe1c]
2010/01/22 15:22:30.048         Pool:0xb6a79b90 OpalCon Releasing Call[i077b9bfd1]-EP<sip>[04bbf73d-cf05-df11-9d0f-0019d188fe1c]
[b]2010/01/22 15:22:30.048         Pool:0xb6a79b90 OpalCon Call end reason for Call[i077b9bfd1]-EP<sip>[04bbf73d-cf05-df11-9d0f-0019d188fe1c] set to EndedByCapabilityExchange[/b]
2010/01/22 15:22:30.048    OnRelease:0xb6a38b90 SIP     OnReleased: Call[i077b9bfd1]-EP<sip>[04bbf73d-cf05-df11-9d0f-0019d188fe1c], phase = ReleasingPhase

    Are there some issues with INVITES which doesn't have a type image from begining?

    Thx 4 any help
    clemix

     

  • clemix

    clemix - 2010-01-22

    For better understanding some more text:
    I can send T.38/SIP faxes with t38modem and efax very well! I see first the call get established with G.711 and after re-invite they send T.38 hdlc frames.

    But on incoming calls the t38modem always reject the calls with "488 Not Acceptable Here" as u can see in the trace above!

     

  • Vyacheslav Frolov

    Vyacheslav Frolov - 2010-01-22

    Try incoming calls with the SimpleOPAL (for example). If you get the same issue then report to opalvoip-user list.

     

Log in to post a comment.