Re: [iaxmodem-users] IAXmodem seems to work, but no carrier
Brought to you by:
faxguy
From: James C. <clo...@jh...> - 2013-05-03 09:46:34
|
>>>>> "CO" == Chris Ott <Chris.Ott@AskAllegiance.com> writes: CO> It's interesting you mention that, because my phone guy tells me that CO> sip and h.323 are the same. I'm guessing that's not true, but I don't CO> know enough to tell him he's wrong. Can you enlighten me? The main difference is that sip comes from the IETF and h.323 from the ITU. I thought that t38modem (t38modem.sf.net) only worked over h323, but I see that it also runs over sip. If your pbx support t38 well enough, then t38modem might be the better choice. BTW, does your PBX connect to the PSTN via ISDN, non-ISDN T-1, analog or pots line(s)? If the pbx itself uses SIP to a remote provider, that is problably the problem. CO> Here's what I have, currently: CO> extensions.conf: CO> [fax-in] CO> exten => _X.,1,Dial(IAX2/iaxmodem) And a similar [fax-out], yes? CO> sip.conf: CO> iax.conf: Those do look OK. CO> /etc/iaxmodem/ttyIAX0: CO> codec alaw Might as well make that ulaw to match the others. In fact, given that you have disallow=all and allow=ulaw in iax.conf having alaw in the iaxmodem config might be the entire issue. Even though they are similar and the conversion is beyond trivial, ast probably refuses to negotiate with iaxmodem because of that. To confirm, if you want, capture the iax session in wireshark or simiar. Alaw vs ulaw is the only thing which stands out. -JimC (falling asleep at the kbd again...) -- James Cloos <cl...@jh...> OpenPGP: 1024D/ED7DAEA6 |