>>>>> "GF" == Gianni Fioretta <[email protected]> writes:

GF>     -- Executing [0224300258@fax:1] Dial("IAX2/modem2-3460", 
"SIP/centralino/0224300258") in new stack
GF>   == Using SIP RTP CoS mark 5
GF>     -- Called SIP/centralino/0224300258
GF>     -- SIP/centralino-00000284 is making progress passing it to 
IAX2/modem2-3460
GF>     -- SIP/centralino-00000284 is ringing
GF>     -- SIP/centralino-00000284 is making progress passing it to 
IAX2/modem2-3460
GF>     -- SIP/centralino-00000283 is making progress passing it to 
IAX2/modem4-8449
GF>     -- SIP/centralino-00000283 is ringing
GF>     -- SIP/centralino-00000283 is making progress passing it to 
IAX2/modem4-8449
GF>     -- SIP/centralino-00000284 answered IAX2/modem2-3460
GF> [Jul  4 16:49:55] WARNING[22988]: chan_sip.c:9123 process_sdp: Failing due 
to no acceptable offer found

That last line above shows that an outgoing fax attempt failed because
the sip end wasn't able to negotaiate a codec for that part of the call.

It looks like it was modem2's call which failed; modem4's call seems not
yet to have been answered.

I don't know whether that is what triggers the wedge, but the failure to
negotiate a codec for the sip/rtp leg probably is a configuration bug.

Which version of asterisk?  Self compiled or a distribution's version?

The sip.conf and iax.conf might help debug it.  (Elide passwords, of course.)

If you run the conf files through something like:

:; egrep -v '^[[:blank:]]*;' iax.conf|egrep -v '^$' >/tmp/short-iax.conf

before editing the password lines it will be easier to read them.

-JimC
-- 
James Cloos <[email protected]>         OpenPGP: 1024D/ED7DAEA6

--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
               http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to