Matthew, thank you very much for the fast reply and very likely the solution!<br>Using your hint I could locally reproduce the &quot;488 Not Acceptable&quot; on my Snom 300 with FW 8.7.3.7 by setting RTP encryption (SRTP) to on and RTP/SAVP to off (RTP/SAVP mandatory or SRTP off -&gt; all fine). The person calling me has the same phone and FW, so that should really be the problem, I will tell him to change it.<br>
However I am wondering why it&#39;s possible to configure a Snom phone in such a wrong way at all? Is that necessary for some legacy systems?<br><br>Also I am wondering if it&#39;s possible to tell asterisk to just ignore the crypto line when the profile is just RTP/AVP / not to take things that serious? In this specific case I can tell the calling person to change the setting, but unfortunately I can&#39;t tell this every person calling me (not only because they simply can&#39;t call me).<br>
<br><br><div class="gmail_quote">2012/6/18 Matthew  Jordan <span dir="ltr">&lt;<a href="mailto:mjordan@digium.com" target="_blank">mjordan@digium.com</a>&gt;</span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
----- Original Message -----<br>
<br>
&gt; From: &quot;Stefan at WPF&quot; &lt;<a href="mailto:stefan.at.wpf@googlemail.com">stefan.at.wpf@googlemail.com</a>&gt;<br>
&gt; To: &quot;Asterisk Users Mailing List - Non-Commercial Discussion&quot;<br>
&gt; &lt;<a href="mailto:asterisk-users@lists.digium.com">asterisk-users@lists.digium.com</a>&gt;<br>
&gt; Sent: Monday, June 18, 2012 3:04:32 PM<br>
&gt; Subject: [asterisk-users] Error SIP/2.0 488 Not acceptable here<br>
<div><div class="h5"><br>
&gt; Hello,<br>
<br>
&gt; a person trying to call me by my phone number is getting the error<br>
&gt; 488 Not acceptable here. I googled that error, seems like this error<br>
&gt; is normally caused by a failed codec negotation, though I have no<br>
&gt; clue how I could have read this out of the logs. Anyway, my setup is<br>
&gt; as follows:<br>
&gt; Asterisk 1.8.13.0 - NAT - Sipgate SIP Provider<br>
&gt; The user calling me is also using Sipgate and is calling my landline<br>
&gt; phone number from Sipgate (not [my sip id]@ <a href="http://sipgate.de" target="_blank">sipgate.de</a> ).<br>
<br>
&gt; My sip.conf including the codec restrictions looks like this (I left<br>
&gt; out my local sip account)<br>
<br>
&gt; &gt; [general]<br>
&gt;<br>
&gt; &gt; port=5060<br>
&gt;<br>
&gt; &gt; bindaddr=0.0.0.0<br>
&gt;<br>
&gt; &gt; context=other<br>
&gt;<br>
&gt; &gt; language=de<br>
&gt;<br>
&gt; &gt; allowguest=no<br>
&gt;<br>
<br>
&gt; &gt; qualify=no<br>
&gt;<br>
&gt; &gt; disallow=all<br>
&gt;<br>
&gt; &gt; allow=alaw<br>
&gt;<br>
&gt; &gt; allow=ulaw<br>
&gt;<br>
&gt; &gt; allow=g729<br>
&gt;<br>
&gt; &gt; allow=gsm<br>
&gt;<br>
&gt; &gt; allow=slinear<br>
&gt;<br>
&gt; &gt; srvlookup=yes<br>
&gt;<br>
<br>
</div></div>&gt; &gt; register =&gt; &lt;MY_SIP_ID&gt;:&lt;password&gt;@ <a href="http://sipgate.de/" target="_blank">sipgate.de/</a> &lt;MY_SIP_ID&gt;<br>
<div class="im">&gt;<br>
<br>
&gt; &gt; [sipgate]<br>
&gt;<br>
&gt; &gt; type=friend<br>
&gt;<br>
&gt; &gt; insecure=invite<br>
&gt;<br>
&gt; &gt; nat=yes<br>
&gt;<br>
&gt; &gt; username=&lt;MY_SIP_ID&gt;<br>
&gt;<br>
&gt; &gt; fromuser=&lt;MY_SIP_ID&gt;<br>
&gt;<br>
&gt; &gt; fromdomain= <a href="http://sipgate.de" target="_blank">sipgate.de</a><br>
&gt;<br>
&gt; &gt; secret=&lt;password&gt;<br>
&gt;<br>
&gt; &gt; host= <a href="http://sipgate.de" target="_blank">sipgate.de</a><br>
&gt;<br>
&gt; &gt; qualify=yes<br>
&gt;<br>
&gt; &gt; canreinvite=no<br>
&gt;<br>
&gt; &gt; dtmfmode=rfc2833<br>
&gt;<br>
&gt; &gt; context = from_external_voip_provider<br>
&gt;<br>
<br>
&gt; The relevant part from my full asterisk log /var/log/asterisk/full<br>
&gt; including the 488 Not acceptable here error message:<br>
<br>
&gt; &gt; [Jun 18 20:15:26] VERBOSE[1164] chan_sip.c:<br>
&gt;<br>
&gt; &gt; &lt;--- SIP read from UDP: <a href="http://217.10.79.9:5060" target="_blank">217.10.79.9:5060</a> ---&gt;<br>
&gt;<br>
</div>&gt; &gt; INVITE sip:&lt;MY_SIP_ID&gt;@ <a href="http://192.168.5.11:5060" target="_blank">192.168.5.11:5060</a> SIP/2.0<br>
<div class="im">&gt;<br>
&gt; &gt; Record-Route: &lt;sip:217.10.79.9;lr;ftag=8cgn1bajqb&gt;<br>
&gt;<br>
&gt; &gt; Record-Route: &lt;sip:172.20.40.3;lr=on&gt;<br>
&gt;<br>
&gt; &gt; Record-Route: &lt;sip:217.10.79.9;lr;ftag=8cgn1bajqb&gt;<br>
&gt;<br>
&gt; &gt; Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK8f5c.48627b3.0<br>
&gt;<br>
&gt; &gt; Via: SIP/2.0/UDP 172.20.40.3;branch=z9hG4bK8f5c.48627b3.0<br>
&gt;<br>
&gt; &gt; Via: SIP/2.0/UDP<br>
&gt; &gt; 217.10.79.9:5060;received=217.10.68.222;branch=z9hG4bK-un6p0cm50qse<br>
&gt;<br>
&gt; &gt; Via: SIP/2.0/UDP<br>
&gt; &gt; 192.168.0.8:2048;received=&lt;CALLING_PARTY_IP_ADDRESS&gt;;branch=z9hG4bK-un6p0cm50qse;rport=2048<br>
&gt;<br>
&gt; &gt; From: &quot; <a href="http://sipgate.de" target="_blank">sipgate.de</a> &quot; &lt;sip:&lt;CALLING_PARTY_SIP_ID&gt;@ <a href="http://sipgate.de" target="_blank">sipgate.de</a><br>
&gt; &gt; &gt;;tag=8cgn1bajqb<br>
&gt;<br>
</div>&gt; &gt; To: &lt;sip:0049&lt;MY_PHONE_NUMBER&gt;@ <a href="http://sipgate.de" target="_blank">sipgate.de</a> ;user=phone&gt;<br>
<div><div class="h5">&gt;<br>
&gt; &gt; Call-ID: 4fdf703d880d-ywqwnfbbj1h7<br>
&gt;<br>
&gt; &gt; CSeq: 2 INVITE<br>
&gt;<br>
&gt; &gt; Max-Forwards: 67<br>
&gt;<br>
&gt; &gt; Contact:<br>
&gt; &gt; &lt;sip:&lt;CALLING_PARTY_SIP_ID&gt;@&lt;CALLING_PARTY_IP_ADDRESS&gt;:2048;line=swnt2d3t&gt;;reg-id=1<br>
&gt;<br>
&gt; &gt; X-Serialnumber: 000413251D76<br>
&gt;<br>
&gt; &gt; User-Agent: snom300/ 8.7.3.7<br>
&gt;<br>
&gt; &gt; Accept: application/sdp<br>
&gt;<br>
&gt; &gt; Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE,<br>
&gt; &gt; PRACK, MESSAGE, INFO, UPDATE<br>
&gt;<br>
&gt; &gt; Allow-Events: talk, hold, refer, call-info<br>
&gt;<br>
&gt; &gt; Supported: timer, 100rel, replaces, from-change<br>
&gt;<br>
&gt; &gt; Session-Expires: 3600;refresher=uas<br>
&gt;<br>
&gt; &gt; Min-SE: 90<br>
&gt;<br>
&gt; &gt; Content-Type: application/sdp<br>
&gt;<br>
&gt; &gt; Content-Length: 522<br>
&gt;<br>
&gt; &gt; P-Asserted-Identity: &lt;sip:&lt;CALLING_PARTY_PHONE_NUMBER&gt;@ <a href="http://sipgate.de" target="_blank">sipgate.de</a><br>
&gt; &gt; &gt;<br>
&gt;<br>
<br>
&gt; &gt; v=0<br>
&gt;<br>
&gt; &gt; o=root 269390684 269390684 IN IP4 192.168.0.8<br>
&gt;<br>
&gt; &gt; s=call<br>
&gt;<br>
&gt; &gt; c=IN IP4 217.10.77.20<br>
&gt;<br>
&gt; &gt; t=0 0<br>
&gt;<br>
&gt; &gt; m=audio 62652 RTP/AVP 9 0 8 3 99 108 18 101<br>
&gt;<br>
&gt; &gt; a=crypto:1 AES_CM_128_HMAC_SHA1_32<br>
&gt; &gt; inline:Ed8iHaP3BXNVeXHj98PRa6sJyImNer3ImjUvDZps<br>
&gt;<br>
&gt; &gt; a=rtpmap:9 G722/8000<br>
&gt;<br>
&gt; &gt; a=rtpmap:0 PCMU/8000<br>
&gt;<br>
&gt; &gt; a=rtpmap:8 PCMA/8000<br>
&gt;<br>
&gt; &gt; a=rtpmap:3 GSM/8000<br>
&gt;<br>
&gt; &gt; a=rtpmap:99 G726-32/8000<br>
&gt;<br>
&gt; &gt; a=rtpmap:108 AAL2-G726-32/8000<br>
&gt;<br>
&gt; &gt; a=rtpmap:18 G729/8000<br>
&gt;<br>
&gt; &gt; a=fmtp:18 annexb=no<br>
&gt;<br>
&gt; &gt; a=rtpmap:101 telephone-event/8000<br>
&gt;<br>
&gt; &gt; a=fmtp:101 0-15<br>
&gt;<br>
&gt; &gt; a=ptime:20<br>
&gt;<br>
&gt; &gt; a=sendrecv<br>
&gt;<br>
&gt; &gt; a=direction:active<br>
&gt;<br>
&gt; &gt; a=nortpproxy:yes<br>
&gt;<br>
&gt; &gt; &lt;-------------&gt;<br>
&gt;<br>
&gt; &gt; [Jun 18 20:15:26] VERBOSE[1164] chan_sip.c: --- (25 headers 21<br>
&gt; &gt; lines)<br>
&gt; &gt; ---<br>
&gt;<br>
&gt; &gt; [Jun 18 20:15:26] VERBOSE[1164] chan_sip.c: Sending to<br>
&gt; &gt; <a href="http://217.10.79.9:5060" target="_blank">217.10.79.9:5060</a> (NAT)<br>
&gt;<br>
&gt; &gt; [Jun 18 20:15:26] VERBOSE[1164] chan_sip.c: Using INVITE request as<br>
&gt; &gt; basis request - 4fdf703d880d-ywqwnfbbj1h7<br>
&gt;<br>
&gt; &gt; [Jun 18 20:15:26] VERBOSE[1164] chan_sip.c: Found peer &#39;sipgate&#39;<br>
&gt; &gt; for<br>
&gt; &gt; &#39;&lt;CALLING_PARTY_SIP_ID&gt;&#39; from <a href="http://217.10.79.9:5060" target="_blank">217.10.79.9:5060</a><br>
&gt;<br>
&gt; &gt; [Jun 18 20:15:26] VERBOSE[1164] netsock2.c: == Using SIP RTP CoS<br>
&gt; &gt; mark<br>
&gt; &gt; 5<br>
&gt;<br>
&gt; &gt; [Jun 18 20:15:26] VERBOSE[1164] chan_sip.c: Found RTP audio format<br>
&gt; &gt; 9<br>
&gt;<br>
&gt; &gt; [Jun 18 20:15:26] VERBOSE[1164] chan_sip.c: Found RTP audio format<br>
&gt; &gt; 0<br>
&gt;<br>
&gt; &gt; [Jun 18 20:15:26] VERBOSE[1164] chan_sip.c: Found RTP audio format<br>
&gt; &gt; 8<br>
&gt;<br>
&gt; &gt; [Jun 18 20:15:26] VERBOSE[1164] chan_sip.c: Found RTP audio format<br>
&gt; &gt; 3<br>
&gt;<br>
&gt; &gt; [Jun 18 20:15:26] VERBOSE[1164] chan_sip.c: Found RTP audio format<br>
&gt; &gt; 99<br>
&gt;<br>
&gt; &gt; [Jun 18 20:15:26] VERBOSE[1164] chan_sip.c: Found RTP audio format<br>
&gt; &gt; 108<br>
&gt;<br>
&gt; &gt; [Jun 18 20:15:26] VERBOSE[1164] chan_sip.c: Found RTP audio format<br>
&gt; &gt; 18<br>
&gt;<br>
&gt; &gt; [Jun 18 20:15:26] VERBOSE[1164] chan_sip.c: Found RTP audio format<br>
&gt; &gt; 101<br>
&gt;<br>
&gt; &gt; [Jun 18 20:15:26] VERBOSE[1164] chan_sip.c: Found audio description<br>
&gt; &gt; format G722 for ID 9<br>
&gt;<br>
&gt; &gt; [Jun 18 20:15:26] VERBOSE[1164] chan_sip.c: Found audio description<br>
&gt; &gt; format PCMU for ID 0<br>
&gt;<br>
&gt; &gt; [Jun 18 20:15:26] VERBOSE[1164] chan_sip.c: Found audio description<br>
&gt; &gt; format PCMA for ID 8<br>
&gt;<br>
&gt; &gt; [Jun 18 20:15:26] VERBOSE[1164] chan_sip.c: Found audio description<br>
&gt; &gt; format GSM for ID 3<br>
&gt;<br>
&gt; &gt; [Jun 18 20:15:26] VERBOSE[1164] chan_sip.c: Found audio description<br>
&gt; &gt; format G726-32 for ID 99<br>
&gt;<br>
&gt; &gt; [Jun 18 20:15:26] VERBOSE[1164] chan_sip.c: Found audio description<br>
&gt; &gt; format AAL2-G726-32 for ID 108<br>
&gt;<br>
&gt; &gt; [Jun 18 20:15:26] VERBOSE[1164] chan_sip.c: Found audio description<br>
&gt; &gt; format G729 for ID 18<br>
&gt;<br>
&gt; &gt; [Jun 18 20:15:26] VERBOSE[1164] chan_sip.c: Found audio description<br>
&gt; &gt; format telephone-event for ID 101<br>
&gt;<br>
&gt; &gt; [Jun 18 20:15:26] WARNING[1164] chan_sip.c: We are requesting SRTP,<br>
&gt; &gt; but they responded without it!<br>
&gt;<br>
&gt; &gt; [Jun 18 20:15:26] VERBOSE[1164] chan_sip.c:<br>
&gt;<br>
&gt; &gt; &lt;--- Reliably Transmitting (NAT) to <a href="http://217.10.79.9:5060" target="_blank">217.10.79.9:5060</a> ---&gt;<br>
&gt;<br>
&gt; &gt; SIP/2.0 488 Not acceptable here<br>
&gt;<br>
&gt; &gt; Via: SIP/2.0/UDP<br>
&gt; &gt; 217.10.79.9:5060;branch=z9hG4bK8f5c.48627b3.0;received=217.10.79.9;rport=5060<br>
&gt;<br>
&gt; &gt; Via: SIP/2.0/UDP 172.20.40.3;branch=z9hG4bK8f5c.48627b3.0<br>
&gt;<br>
&gt; &gt; Via: SIP/2.0/UDP<br>
&gt; &gt; 217.10.79.9:5060;received=217.10.68.222;branch=z9hG4bK-un6p0cm50qse<br>
&gt;<br>
&gt; &gt; Via: SIP/2.0/UDP<br>
&gt; &gt; 192.168.0.8:2048;received=&lt;CALLING_PARTY_IP_ADDRESS&gt;;branch=z9hG4bK-un6p0cm50qse;rport=2048<br>
&gt;<br>
&gt; &gt; From: &quot; <a href="http://sipgate.de" target="_blank">sipgate.de</a> &quot; &lt;sip:&lt;CALLING_PARTY_SIP_ID&gt;@ <a href="http://sipgate.de" target="_blank">sipgate.de</a><br>
&gt; &gt; &gt;;tag=8cgn1bajqb<br>
&gt;<br>
&gt; &gt; To: &lt;sip:0049&lt;MY_PHONE_NUMBER&gt;@ <a href="http://sipgate.de" target="_blank">sipgate.de</a><br>
</div></div><div class="im">&gt; &gt; ;user=phone&gt;;tag=as6364b798<br>
&gt;<br>
&gt; &gt; Call-ID: 4fdf703d880d-ywqwnfbbj1h7<br>
&gt;<br>
&gt; &gt; CSeq: 2 INVITE<br>
&gt;<br>
&gt; &gt; Server: Asterisk PBX 1.8.13.0~dfsg-1<br>
&gt;<br>
&gt; &gt; Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY,<br>
&gt; &gt; INFO, PUBLISH<br>
&gt;<br>
&gt; &gt; Supported: replaces, timer<br>
&gt;<br>
&gt; &gt; Content-Length: 0<br>
&gt;<br>
<br>
&gt; I am having problems to see to what &quot;488 Not acceptable here&quot; relates<br>
&gt; to? What is not acceptable? Is it maybe about<br>
<br>
&gt; &gt; [Jun 18 20:15:26] WARNING[1164] chan_sip.c: We are requesting SRTP,<br>
&gt; &gt; but they responded without it!<br>
&gt;<br>
<br>
</div>Yes, that would be the problem.<br>
<br>
The SIP UA is doing something a little wrong here by offering a security<br>
description (crypto) without specifying that the audio/video protocol that<br>
should be used as SRTP (RTP/SAVP).  Because the UA appears to be attempting<br>
to negotiate a SRTP connection, Asterisk is checking if the peer has encryption<br>
enabled.  Since the peer corresponding with the UA does not have encryption<br>
enabled for it, Asterisk is responding with a 488 response.<br>
<br>
SRTP security descriptions (such as &#39;crypto&#39;) must only be used with the<br>
SRTP transport specified, e.g., RTP/SAVP or RTP/SAVPF.<br>
<br>
--<br>
Matthew Jordan<br>
Digium, Inc. | Software Developer<br>
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA<br>
Check us out at: <a href="http://digium.com" target="_blank">http://digium.com</a> &amp; <a href="http://asterisk.org" target="_blank">http://asterisk.org</a><br>
<br>
--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
New to Asterisk? Join us for a live introductory webinar every Thurs:<br>
               <a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</a><br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
   <a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
</blockquote></div><br>