Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#13 t38modem update and CallerID change

pending
nobody
None
5
2011-07-05
2011-06-19
F. Ribera
No

Hello guys,

I updated from t38modem 1.0 to t38modem 2.0 and now I am having problems with the destination number in order to dispatch the fax (I am running Hylafax 4.0 and SIP). Anyhow the information provided by t38modem 2.0 regarding to the destination number has changed. I can see that when the modem is ringing Hylafax correctly gets all NDID, NMBR and NAME but these fields don't correspond to the ones provided by the version 1.0. I have roll back to 1.0 but I would be interested in knowing if there is anything I can do to fit it to my scenario.
This is a special case in which the call comes from a PBX which is forwarding the call to the t38modem (but it is not the actual recipient of the call).

Does this anything to do with the new opal version?May I modify something on the source to get the ancient values?

Thank you very much
Felipe

Discussion

  • Any logs that demonstrate incompatible changes?

     
    • status: open --> pending