t38modem / Discussion / Help: 2x t38modem same host: 488 Not Acceptable Here

Hi,

WHen i send a fax between 2 t38modems the first reponse to invite with "488 Not Acceptable Here" and fallback to PCMA/800.

can anyone help me?

Ubuntu 16.04
asterisk 14
hylafax 5.5.9
T38Modem Version 2.0.0 (OPAL-3.10.10/3.10.10 (svn:29150), PTLIB-2.10.10/2.10.11 (svn:30295)) by Vyacheslav Frolov on Unix Linux (4.4.0-128-generic-x86_64)

sngrep capture

t38modem load:

/usr/bin/t38modem -tttttttt -o /var/log/t38modem01.log --no-h323 -u 8001 --sip-listen udp$10.128.1.10:4571 --sip-t38-udptl-redundancy 3 --ptty +/dev/ttyT01 --route "modem:.*=sip:<dn>@10.128.1.10" --route "sip:.*=modem:<dn>"

/usr/bin/t38modem -tttttttt -o /var/log/t38modem02.log --no-h323 -u 8002 --sip-listen udp$10.128.1.10:4572 --sip-t38-udptl-redundancy 3 --ptty +/dev/ttyT02 --route "modem:.*=sip:<dn>@10.128.1.10" --route "sip:.*=modem:<dn>"

asterisk console:

faxserver*CLI> module show like fax
Module                         Description                              Use Count  Status      Support Level
res_fax.so                     Generic FAX Applications                 1          Running              core
res_fax_spandsp.so             Spandsp G.711 and T.38 FAX Technologies  0          Running          extended
2 modules loaded
faxserver*CLI>
 == Using SIP RTP CoS mark 5
       > 0x7f3154009460 -- Strict RTP learning after remote address set to: 10.128.1.10:5010
    -- Executing [986854439@from-fax:1] Set("SIP/8002-00000005", "FAXOPT(gateway)=yes") in new stack
    -- Executing [986854439@from-fax:2] Dial("SIP/8002-00000005", "SIP/8001/986854439,10") in new stack
  == Using SIP RTP CoS mark 5
    -- Called SIP/8001/986854439
    -- SIP/8001-00000006 is ringing
       > 0x7f315804d750 -- Strict RTP learning after remote address set to: 10.128.1.10:5012
    -- SIP/8001-00000006 answered SIP/8002-00000005
       > 0x7f3154009460 -- Strict RTP learning after remote address set to: 10.128.1.10:5010
    -- Channel SIP/8001-00000006 joined 'simple_bridge' basic-bridge <f09f5bf1-e2b2-47fa-9923-218df789e5f4>
       > 0x7f315804d750 -- Strict RTP switching to RTP target address 10.128.1.10:5012 as source
    -- Channel SIP/8002-00000005 joined 'simple_bridge' basic-bridge <f09f5bf1-e2b2-47fa-9923-218df789e5f4>
       > 0x7f3154009460 -- Strict RTP switching to RTP target address 10.128.1.10:5010 as source
  == Using UDPTL CoS mark 5
  == Using UDPTL CoS mark 5
       > 0x7f3154009460 -- Strict RTP learning complete - Locking on source address 10.128.1.10:5010
    -- Channel SIP/8001-00000006 left 'simple_bridge' basic-bridge <f09f5bf1-e2b2-47fa-9923-218df789e5f4>
    -- Channel SIP/8002-00000005 left 'simple_bridge' basic-bridge <f09f5bf1-e2b2-47fa-9923-218df789e5f4>

sip.conf:

[general]
t38pt_udptl = yes            ; Enables T.38 with FEC error correction.

[8001]
type=friend
qualify=yes
disallow=all
allow=alaw,ulaw
context=from-fax
host=10.128.1.10
directmedia=yes
t38pt_udptl = yes
username=8001
port=4571

[8002]
type=friend
qualify=yes
disallow=all
allow=alaw,ulaw
context=from-fax
host=10.128.1.10
directmedia=yes
t38pt_udptl = yes
username=8002
port=4572

extensions.conf:

[from-fax]
exten => _X.,1,Set(FAXOPT(gateway)=yes)
same =>  n,Dial(SIP/8001/${EXTEN},10)
same =>  n,Dial(SIP/8002/${EXTEN},10)
same =>  n,Busy()
same =>  n,Hangup()

udptl.conf:

; UDPTL Configuration (UDPTL is one of the transports for T.38)
;
[general]
;
; UDPTL start and UDPTL end configure start and end addresses
;
udptlstart=4000
udptlend=4999
;
; Whether to enable or disable UDP checksums on UDPTL traffic
;
;udptlchecksums=no
;
; The number of error correction entries in a UDPTL packet
;
udptlfecentries = 3
;
; The span over which parity is calculated for FEC in a UDPTL packet
;
udptlfecspan = 3
;
; Some VoIP providers will only accept an offer with an even-numbered
; UDPTL port. Set this option so that Asterisk will only attempt to use
; even-numbered ports when negotiating T.38. Default is no.
use_even_ports = no

Regards,

Alessan - 2018-07-13

Using version 3.11.0 fix the "not acceptable" and i can send faxes between 2 t38modems in test environment

But when i try using real t38 gateway (sangoma vega 100) t38 negotiation is not completed

any help is apreciated

T38Modem Version 3.11.0
(OPAL-3.10.15/3.10.15 (svn:30298), PTLIB-2.10.15/2.10.15 (svn:30295)) by Frolov,Holtschneider,Davidson on Unix Linux (4.4.0-130-generic-x86_64)

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Pete Davidson - 2018-07-13
  
  Please try release 3.15.3.
  
  Pete
  
  On Fri, Jul 13, 2018 at 2:06 PM, Alessan alessant77@users.sourceforge.net
  wrote:
  
  Using version 3.11.0 fix the "not acceptable" and i can send faxes between
  2 t38modems in test environment
  
  But when i try using real t38 gateway (sangoma vega 100) t38 negotiation
  is not completed
  
  any help is apreciated
  
  T38Modem Version 3.11.0
  (OPAL-3.10.15/3.10.15 (svn:30298), PTLIB-2.10.15/2.10.15 (svn:30295)) by
  Frolov,Holtschneider,Davidson on Unix Linux (4.4.0-130-generic-x86_64)
  
  2x t38modem same host: 488 Not Acceptable Here
  https://sourceforge.net/p/t38modem/discussion/508603/thread/35f63b4e/?limit=25#9845
  
  Sent from sourceforge.net because you indicated interest in
  https://sourceforge.net/p/t38modem/discussion/508603/
  
  To unsubscribe from further messages, please visit
  https://sourceforge.net/auth/subscriptions/
  
  --
  Pete Davidson
  Senior Software Developer
  Embedded Systems
  
  O +1 859 825 4999
  M +1 859 338 3426
  F +1 859 232 6267
  Pete@Lexmark.com
  
  http://www.lexmark.com/
  www.lexmark.com
  
  alternate
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - Alessan - 2018-07-14
    
    Hi Pete,
    
    Thanks for response,
    
    t38modem 3.15.3 wih opal 3.10.15 and ptlib 2.10.15?
    
    Regards,
    
    Last edit: Alessan 2018-07-15
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
    - Pete Davidson - 2018-07-16
      
      what is your problem?
      
      On Sat, Jul 14, 2018 at 3:00 AM, Alessan alessant77@users.sourceforge.net
      wrote:
      
      Hi Pete,
      
      Thanks for response, I have some problems compiling 3.15.3 ¿can i send you
      a private message?
      
      2x t38modem same host: 488 Not Acceptable Here
      https://sourceforge.net/p/t38modem/discussion/508603/thread/35f63b4e/?limit=25#9845/896e/b1ba
      
      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/t38modem/discussion/508603/
      
      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/
      
      --
      Pete Davidson
      Senior Software Developer
      Embedded Systems
      
      O +1 859 825 4999
      M +1 859 338 3426
      F +1 859 232 6267
      Pete@Lexmark.com
      
      http://www.lexmark.com/
      www.lexmark.com
      
      alternate
      
      If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
      - Alessan - 2018-07-16
        
        Hi Pete,
        
        Sorry, It was the bison yyparse error.
        
        I read your repository notes and I could compile ptlib.
        
        Now my problem is inside t38 protocol explained on next Post.
        
        Thanks,
        
        If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Hi,

Same problem with 3.15.3, t38 is established but modem training fail

t38modem log
hylafax log

root@t38:~# /home/main/t38modem-3.15/t38modem -ttttt -o /var/log/t38modem-ttyT3801.log --no-h323 -u 8001 --sip-listen udp$192.9.201.192:4571 --sip-t38-udptl-redundancy 3 --ptty  +/dev/ttyT3801 --route "modem:.*=sip:<dn>@172.26.0.5" --route "sip:.*=modem:<dn>" --sip-register 8001@172.26.0.5,p0v1s4p4ss
T38Modem Version 3.15.3
 (OPAL-3.10.15/3.10.15 (svn:30298), PTLIB-2.10.15/2.10.15 (svn:30295)) by Frolov,Holtschneider,Davidson on Unix Linux (4.4.0-31-generic-x86_64)

T38Modem pid: 2525  ppid: 1924
Disabled H.323 protocol
Waiting for incoming SIP calls from udp92.9.201.192:4571
Route table:
  modem:.*=sip:<dn>@172.26.0.5
  sip:.*=modem:<dn>

Last edit: Alessan 2018-07-16

Alessan - 2018-07-16

If I compare an iaxmodem with a t38modem hylafax log i can found that our gateway is reporting MMR support using T.38 and no MMR support on a normal SIP call....

It is posible that gateway is shadowing remote fax capabilities and fail becouse MMR is not supported? I try disabling 2D-MMR on hylafax tomorrow.

iaxmodem:

jul 16 13:16:24.68: [ 2656]: REMOTE best rate 14400 bit/s
jul 16 13:16:24.68: [ 2656]: REMOTE max A4 page width (215 mm)
jul 16 13:16:24.68: [ 2656]: REMOTE max unlimited page length
jul 16 13:16:24.68: [ 2656]: REMOTE best vres 7.7 line/mm
jul 16 13:16:24.68: [ 2656]: REMOTE format support: MH, MR
jul 16 13:16:24.68: [ 2656]: REMOTE best 10 ms/scanline
jul 16 13:16:24.68: [ 2656]: USE 14400 bit/s
jul 16 13:16:24.68: [ 2656]: SEND file "docq/doc2.pdf;1d81"
jul 16 13:16:24.68: [ 2656]: USE A4 page width (215 mm)
jul 16 13:16:24.68: [ 2656]: USE unlimited page length
jul 16 13:16:24.68: [ 2656]: USE 7.7 line/mm
jul 16 13:16:24.68: [ 2656]: USE 2-D MR
jul 16 13:16:24.68: [ 2656]: USE 10 ms/scanline
jul 16 13:16:24.68: [ 2656]: SEND training at v.17 14400 bit/s

t38modem:

jul 02 13:40:06.63: [30975]: REMOTE best rate 14400 bit/s
jul 02 13:40:06.63: [30975]: REMOTE max A4 page width (215 mm)
jul 02 13:40:06.63: [30975]: REMOTE max unlimited page length
jul 02 13:40:06.63: [30975]: REMOTE best vres 7.7 line/mm
jul 02 13:40:06.63: [30975]: REMOTE format support: MH, MR, MMR
jul 02 13:40:06.63: [30975]: REMOTE supports T.30 Annex A, 256-byte ECM
jul 02 13:40:06.63: [30975]: REMOTE best 10 ms/scanline
jul 02 13:40:06.63: [30975]: USE 14400 bit/s
jul 02 13:40:06.63: [30975]: USE error correction mode
jul 02 13:40:06.63: [30975]: SEND file "docq/doc245.ps;1d81"
jul 02 13:40:06.63: [30975]: USE A4 page width (215 mm)
jul 02 13:40:06.63: [30975]: USE unlimited page length
jul 02 13:40:06.63: [30975]: USE 7.7 line/mm
jul 02 13:40:06.63: [30975]: USE 2-D MMR
jul 02 13:40:06.63: [30975]: USE 0 ms/scanline
jul 02 13:40:06.63: [30975]: SEND training at v.17 14400 bit/s

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Pete Davidson - 2018-07-16
  
  It is really hard to say without seeing the network traces between all the
  devices.
  
  On Mon, Jul 16, 2018 at 1:15 PM, Alessan alessant77@users.sourceforge.net
  wrote:
  
  If I compare an iaxmodem with a t38modem hylafax log i can found that our
  gateway is reporting MMR support using T.38 and no MMR support on a normal
  SIP call....
  
  It is posible that gateway is shadowing remote fax capabilities and fail
  becouse MMR is not supported? I try disabling 2D-MMR on hylafax tomorrow.
  
  iaxmodem:
  
  jul 16 13:16:24.68: [ 2656]: REMOTE best rate 14400 bit/s
  jul 16 13:16:24.68: [ 2656]: REMOTE max A4 page width (215 mm)
  jul 16 13:16:24.68: [ 2656]: REMOTE max unlimited page length
  jul 16 13:16:24.68: [ 2656]: REMOTE best vres 7.7 line/mm
  jul 16 13:16:24.68: [ 2656]: REMOTE format support: MH, MR
  jul 16 13:16:24.68: [ 2656]: REMOTE best 10 ms/scanline
  jul 16 13:16:24.68: [ 2656]: USE 14400 bit/s
  jul 16 13:16:24.68: [ 2656]: SEND file "docq/doc2.pdf;1d81"
  jul 16 13:16:24.68: [ 2656]: USE A4 page width (215 mm)
  jul 16 13:16:24.68: [ 2656]: USE unlimited page length
  jul 16 13:16:24.68: [ 2656]: USE 7.7 line/mm
  jul 16 13:16:24.68: [ 2656]: USE 2-D MR
  jul 16 13:16:24.68: [ 2656]: USE 10 ms/scanline
  jul 16 13:16:24.68: [ 2656]: SEND training at v.17 14400 bit/s
  
  t38modem:
  
  jul 02 13:40:06.63: [30975]: REMOTE best rate 14400 bit/s
  jul 02 13:40:06.63: [30975]: REMOTE max A4 page width (215 mm)
  jul 02 13:40:06.63: [30975]: REMOTE max unlimited page length
  jul 02 13:40:06.63: [30975]: REMOTE best vres 7.7 line/mm
  jul 02 13:40:06.63: [30975]: REMOTE format support: MH, MR, MMR
  jul 02 13:40:06.63: [30975]: REMOTE supports T.30 Annex A, 256-byte ECM
  jul 02 13:40:06.63: [30975]: REMOTE best 10 ms/scanline
  jul 02 13:40:06.63: [30975]: USE 14400 bit/s
  jul 02 13:40:06.63: [30975]: USE error correction mode
  jul 02 13:40:06.63: [30975]: SEND file "docq/doc245.ps;1d81"
  jul 02 13:40:06.63: [30975]: USE A4 page width (215 mm)
  jul 02 13:40:06.63: [30975]: USE unlimited page length
  jul 02 13:40:06.63: [30975]: USE 7.7 line/mm
  jul 02 13:40:06.63: [30975]: USE 2-D MMR
  jul 02 13:40:06.63: [30975]: USE 0 ms/scanline
  jul 02 13:40:06.63: [30975]: SEND training at v.17 14400 bit/s
  
  2x t38modem same host: 488 Not Acceptable Here
  https://sourceforge.net/p/t38modem/discussion/508603/thread/35f63b4e/?limit=25#65db
  
  Sent from sourceforge.net because you indicated interest in
  https://sourceforge.net/p/t38modem/discussion/508603/
  
  To unsubscribe from further messages, please visit
  https://sourceforge.net/auth/subscriptions/
  
  --
  Pete Davidson
  Senior Software Developer
  Embedded Systems
  
  O +1 859 825 4999
  M +1 859 338 3426
  F +1 859 232 6267
  Pete@Lexmark.com
  
  http://www.lexmark.com/
  www.lexmark.com
  
  alternate
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - Alessan - 2018-07-16
    
    Previous fax network capture
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Alessan - 2018-07-17

Seems disable MMR and ECM don´t work.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Alessan - 2018-07-17

Hi All,

Finally I found one BIIGGGG problem

Geting a packet capture on gateway i can see second network interface responding to t38 pcakets.... and this interface is on other subnet without connection to asterisk.....

https://image.ibb.co/nfWxby/vegacapture.png

Tomorrow I fix this and try, after a month testing i have hope!!!!

Last edit: Alessan 2018-07-17

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Alessan - 2018-07-17

I'm sad,

Seems the bad ip is a wireshark delusion, each packet is arrived on asterisk and passed to t38modem :(

Last edit: Alessan 2018-07-17

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Alessan - 2018-07-27
  
  Refered interface is a vitual interface that cant be deactivated, waiting for Sangoma response.
  
  Thanks,
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

2x t38modem same host: 488 Not Acceptable Here

Forums

Help

2x t38modem same host: 488 Not Acceptable Here document.SUBSCRIPTION_OPTIONS = { "thing": "topic", "subscribed": false, "url": "subscribe", "icon": { "css": "fa fa-envelope-o" } };

2x t38modem same host: 488 Not Acceptable Here