Andrew Joakimsen
2008-Jan-15 21:54 UTC
[asterisk-users] WARNING[31046]: chan_sip.c:4978 process_sdp: Unable to lookup host in c= line, 'IN IP4 100101'
Anyone else have issues with T.38 where the call drops after T.38 is attempted to be negotiated, with a message like the below? WARNING[31046]: chan_sip.c:4978 process_sdp: Unable to lookup host in c= line, 'IN IP4 100101'
What are the values for type for chan_mobile? headset and phone ??? I get my Treo650 to pair. hcitool scan shows the device. hcitool con comes up empty. I go into Asterisk cli. mobile search shows the device (while I am waiting for a response, I see the phone showing a connection being set up). And I am shown that I have a device that is: NOT available and is a headset OOPS. So I think I need to force Asterisk to see this as a phone? Or is there something I need in a bluetooth config file?
Mark Michelson
2008-Jan-15 23:25 UTC
[asterisk-users] WARNING[31046]: chan_sip.c:4978 process_sdp: Unable to lookup host in c= line, 'IN IP4 100101'
Andrew Joakimsen wrote:> Anyone else have issues with T.38 where the call drops after T.38 is > attempted to be negotiated, with a message like the below? > > WARNING[31046]: chan_sip.c:4978 process_sdp: Unable to lookup host in > c= line, 'IN IP4 100101'The problem is that 100101 is neither a valid IPv4 address nor a fully-qualified domain name.
Apparently Analagous Threads
- WARNING: chan_sip.c:3470 process_sdp: Unknown SDP media type in offer: image 5004 udptl t38
- process_sdp: Unsupported SDP media type in offer: audio , Failing due to no acceptable offer found
- process_sdp: Multiple audio streams are not supported
- Asterisk 1.6.1.13 and T.38 faxing
- chan_sip bug? (Asterisk 1.4)