488 / Not Acceptable Here

1,396 views
Skip to first unread message

josejuan

unread,
Jan 23, 2013, 6:19:49 PM1/23/13
to csipsim...@googlegroups.com
Hi!
I'm doing some modifications of CSipSimple and I've done a mess, while I was trying to modify the way the SipProfile is created and the codecs are ordered I get a 488 / Not Acceptable Here when I try to make a call, can somebody please help me to know they way the codecs originally are set up, I just need to activate G729, G711a and G711u and modify them priorities, It could be possible?

Shiam SHABBIR HIMEL

unread,
Jan 24, 2013, 12:06:38 AM1/24/13
to csipsim...@googlegroups.com
i am also new to csipsimple but you can change priority of codecs in com.csipsimple.utils.compatibility.java class. in that class all available codecs are given a priority number. you can change the priority number of g729 etc. higher than the other. then they would be auto selected in the list. 

josejuan

unread,
Jan 24, 2013, 5:15:38 PM1/24/13
to csipsim...@googlegroups.com
I've already test modifying priorities in com.csipsimple.utils.Compatibility but still having 488 / Not Accepted. If I try to modify codecs order by using the GUI for that the error still there, someone knows how to know which codecs are being used when calling? 

Régis Montoya

unread,
Jan 25, 2013, 4:46:18 AM1/25/13
to CSipSimple dev group
Normally the codecs used are the codecs you see in the UI (just be carefull with the fact there is a list for slow networks (as 3G etc) and one for fast networks).
You can probably collect logs (see HowToCollectLogs wiki page) to get all SIP traces and see exactly why the remote side doesn't accept the SDP.
Sometimes, 488 is not related to codecs : sometimes it's something in the SDP that your sip server doesn't understand -- SDP are always sip rfc compliant but some servers are buggy and when see parameters that it doesn't understand gets broken. (There is some workaround settings available in those cases).
But I think that logs from the app could help to understand the problem. If you can produce logs for incoming and for outgoing calls will be interesting (as for incoming sdp is generally produced first by remote and could give an idea of what it expect and what parameters it doesn't includes and it might misunderstood).

Best regards,
Régis


2013/1/24 josejuan <josejua...@gmail.com>

josejuan

unread,
Jan 25, 2013, 5:53:23 PM1/25/13
to csipsim...@googlegroups.com
From incoming call Logs says:

01-25 16:46:42.973: E/libpjsip(29601): 16:46:42.973  pjsua_media.c  ....pjmedia_stream_info_from_sdp() failed for call_id 1 media 0: Unsupported address family (PJ_EAFNOTSUP)
01-25 16:46:42.973: E/libpjsip(29601): 16:46:42.974   pjsua_call.c  ...Unable to create media session: No active media stream after negotiation (PJMEDIA_SDPNEG_ENOMEDIA) [status=220048]
01-25 16:46:43.113: E/libpjsip(29601): 16:46:43.115   pjsua_call.c  .Error creating response: Not Acceptable Here [status=170488]
01-25 16:46:46.953: E/SensorManager(29601): unregisterListener:: all sensors,  listener = com.csipsimple.ui.incall.AccelerometerListener$1@49fb3d78
01-25 16:46:46.953: E/SensorHAL(29601): __data_data_close 

And for outgoing call:

01-25 16:51:31.043: W/libutils.threads(29620): Thread (this=0x2a8a80): don't call waitForExit() from this Thread object's thread. It's a guaranteed deadlock!
01-25 16:51:31.043: E/AudioTrack(29620): AudioTrack::start called from thread
01-25 16:51:34.043: E/ToneGenerator(29620): --- Immediate start timed out, status -110
01-25 16:51:34.043: W/ToneGenerator(29620): Tone start failed!!!, time 44070031
01-25 16:51:34.853: W/libutils.threads(29620): Thread (this=0x264da8): don't call waitForExit() from this Thread object's thread. It's a guaranteed deadlock!
01-25 16:51:34.853: E/AudioTrack(29620): AudioTrack::start called from thread
01-25 16:51:35.783: D/PhoneWindow(29620): couldn't save which view has focus because the focused view android.view.View@4a052bd0 has no id.
01-25 16:51:36.643: E/SensorManager(29601): registerListener :: handle = 0  name= BMA220 delay= 240 Listener= com.csipsimple.ui.incall.AccelerometerListener$1@4a061fa8
01-25 16:51:36.643: E/SensorManager(29601): =======>>>Sensor Thread RUNNING <<<========
01-25 16:51:36.643: E/SensorHAL(29601): __data_data_open  90 91
01-25 16:51:36.923: I/ActivityThread(29601): queueIdle
01-25 16:51:36.923: W/ActivityNative(29601): send ACTIVITY_IDLE_TRANSACTION
01-25 16:51:37.853: E/ToneGenerator(29620): --- Immediate start timed out, status -110
01-25 16:51:37.853: W/ToneGenerator(29620): Tone start failed!!!, time 44073844
01-25 16:51:40.003: E/SensorManager(29601): unregisterListener:: all sensors,  listener = com.csipsimple.ui.incall.AccelerometerListener$1@4a061fa8
01-25 16:51:40.053: E/SensorHAL(29601): __data_data_close 
01-25 16:51:40.223: I/ActivityThread(29620): queueIdle
01-25 16:51:40.223: W/ActivityNative(29620): send ACTIVITY_IDLE_TRANSACTION
01-25 16:51:49.613: W/KeyCharacterMap(29620): No keyboard for id -1
01-25 16:51:49.613: W/KeyCharacterMap(29620): Using default keymap: /system/usr/keychars/qwerty.kcm.bin

Could you please help me to know what is happening?



Régis Montoya

unread,
Jan 26, 2013, 6:08:57 AM1/26/13
to csipsim...@googlegroups.com
Hi,


I would be very interested by what comes before in logs for the incoming call case with logs of level 4 are activated -> http://code.google.com/p/csipsimple/wiki/HowToCollectLogs?wl=en (here with only error level it's hard to say).

I think the SDP contains something related to the remote media address that is not understood by pjsip. Maybe ipv6? (in which case ipv6 should be enabled in csipsimple settings). Or maybe something else that the app doesn't understand.
--
 
 

josejuan

unread,
Jan 28, 2013, 6:26:27 PM1/28/13
to csipsim...@googlegroups.com
I've fixed it!!

I've had activated ipv6mediatransport and my SIP Provider doesn't support ipv6 so PJSIP can't mach media.
Just disabled ipv6mediatransport and it worked!!

Thanks!!
Reply all
Reply to author
Forward
0 new messages