I have implemented onramp and offramp for my customer. Onramp fax is working fine but the offramp fax is not working. When we test with facsBridge T37 we do not see fax coming on CME router.
Router configuration is
I have enabled the mta and foip debugs but no logs are generated. But when I run the wireshark debugs on laptop on which facsBridge application is running, I see acknowledgement from router. But Microsoft fax application which uses facsBridge as modem do the retransmission 2-3 times and then give fatal error.
I am not sure if issue is with config or i am hitting bug. Please guide me how to resolve this issue.
one update...on wireshark i am seeing RST, ACK from router which means it is reseting the session...but could not find reason for that. i tired with app_faxmail_offramp.18.104.22.168.tcl and app_faxmail_offramp.22.214.171.124.tcl script, but results are same.
Below is config of cme.
fax receive called-subscriber $d$ fax send transmitting-subscriber $s$ fax interface-type fax-mail mta send subject Fax from On-Ramp GW mta send with-subject $s$ mta send postmaster email@example.com mta send mail-from hostname xxxxsolutions.com mta send mail-from username info mta receive aliases xxxxxsolutions.com mta receive aliases smtp.gmail.com mta receive aliases 10.1.30.13 mta receive generate mdn mta receive generate permanent-error !
service onramp flash:/its/app_faxmail_onramp.126.96.36.199.tcl ! service offramp flash:/its/app_faxmail_offramp.188.8.131.52.tcl ! service offramp1 flash:/its/app_faxmail_offramp.184.108.40.206.tcl ! service fax_detect flash:/its/app_fax_detect.220.127.116.11.tcl param redirect-number 106 param mode default-fax
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.