Hello, Thanks Richard, I made a new test and below is the output from /var/log/messages. This is probably a relevant part: Apr 2 14:10:52 u363id562 mediaproxy-ng[18742]: [oginba5h5r8h1hk3kngu - ] Got LOOKUP, but no usable callstreams found Apr 2 14:10:52 u363id562 mediaproxy-ng[18742]: Error rewriting SDP Looks like the whole call gets somehow messed up, there are several BYE messages before I end the call from either side. I wonder what causes the BYE messages to be sent? I'll get better sdp output soon... Thanks again, Olli Apr 2 14:10:47 u363id562 mediaproxy-ng[18742]: Got valid command from 127.0.0.1:39795 <http://127.0.0.1:39795>: offer - { "sdp": "v=0#015#012o=- 7083457405291314669 2 IN IP4 127.0.0.1#015#012s=-#015#012t=0 0#015#012a=group:BUNDLE audio#015#012a=msid-semantic: WMS No46lGs0HIghRI0dBCknwdhJyR8IlJ3FPqI3#015#012m=audio 64860 RTP/SAVPF 111 103 104 0 8 106 105 13 126#015#012c=IN IP4 2.2.2.2#015#012a=rtcp:64860 IN IP4 2.2.2.2#015#012a=candidate:2999745851 1 udp 2113937151 192.168.56.1 64859 typ host generation 0#015#012a=candidate:2999745851 2 udp 2113937151 192.168.56.1 64859 typ host generation 0#015#012a=candidate:3350409123 1 udp 2113937151 192.168.0.101 64860 typ host generation 0#015#012a=candidate:3350409123 2 udp 2113937151 192.168.0.101 64860 typ host generation 0#015#012a=candidate:4233069003 1 tcp 1509957375 192.168.56.1 0 typ host generation 0#015#012a=candidate:4233069003 2 tcp 1509957375 192.168.56.1 0 typ host generation 0#015#012a=candidate:2301678419 1 tcp 1509957375 192.168.0.101 0 typ host generation 0#015#012a=candidate:2301678419 2 tcp 1509957375 192.168.0.101 0 typ host generation 0#015#012a=candidate:1190865175 1 udp 1845501695 2.2.2.2 64860 typ srflx raddr 192.168.0.101 rport 64860 generation 0#015#012a=candidate:1190865175 2 udp 1845501695 2.2.2.2 64860 typ srflx raddr 192.168.0.101 rport 64860 generation 0#015#012a=ice-ufrag:Nuzos2pMurFvifge#015#012a=ice-pwd:AAcKZc38Sp21Y/kFzdYxFGjt#015#012a=ice-options:google-ice#015#012a=fingerprint:sha-256 72:54:87:EC:D2:4C:D1:70:C2:FE:69:08:20:5C:92:1D:E0:EA:BD:45:09:E0:90:62:27:B6:34:60:54:E2:99:28#015#012a=setup:actpass#015#012a=mid:audio#015#012a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level#015#012a=sendrecv#015#012a=rtcp-mux#015#012a=crypto:0 AES_CM_128_HMAC_SHA1_32 inline:ERj6OGgpgTMY1kD3wmxN3oIOD8L5vL5tKAtmHM0f#015#012a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:UT3fhVoULjUtaHJdfLkFHqTbAEfb3oKDWqBY3ahK#015#012a=rtpmap:111 opus/48000/2#015#012a=fmtp:111 minptime=10#015#012a=rtpmap:103 ISAC/16000#015#012a=rtpmap:104 ISAC/32000#015#012a=rtpmap:0 PCMU/8000#015 Apr 2 14:10:47 u363id562 mediaproxy-ng[18742]: [oginba5h5r8h1hk3kngu] Creating new call Apr 2 14:10:47 u363id562 mediaproxy-ng[18742]: Returning to SIP proxy: d3:sdp2211:v=0#015#012o=- 7083457405291314669 2 IN IP4 1.1.1.1#015#012s=-#015#012t=0 0#015#012a=group:BUNDLE audio#015#012a=msid-semantic: WMS No46lGs0HIghRI0dBCknwdhJyR8IlJ3FPqI3#015#012m=audio 30032 RTP/SAVPF 111 103 104 0 8 106 105 13 126#015#012c=IN IP4 1.1.1.1#015#012a=candidate:2999745851 1 udp 2113937151 192.168.56.1 64859 typ host generation 0#015#012a=candidate:2999745851 2 udp 2113937151 192.168.56.1 64859 typ host generation 0#015#012a=candidate:3350409123 1 udp 2113937151 192.168.0.101 64860 typ host generation 0#015#012a=candidate:3350409123 2 udp 2113937151 192.168.0.101 64860 typ host generation 0#015#012a=candidate:4233069003 1 tcp 1509957375 192.168.56.1 0 typ host generation 0#015#012a=candidate:4233069003 2 tcp 1509957375 192.168.56.1 0 typ host generation 0#015#012a=candidate:2301678419 1 tcp 1509957375 192.168.0.101 0 typ host generation 0#015#012a=candidate:2301678419 2 tcp 1509957375 192.168.0.101 0 typ host generation 0#015#012a=candidate:1190865175 1 udp 1845501695 2.2.2.2 64860 typ srflx raddr 192.168.0.101 rport 64860 generation 0#015#012a=candidate:1190865175 2 udp 1845501695 2.2.2.2 64860 typ srflx raddr 192.168.0.101 rport 64860 generation 0#015#012a=ice-ufrag:Nuzos2pMurFvifge#015#012a=ice-pwd:AAcKZc38Sp21Y/kFzdYxFGjt#015#012a=ice-options:google-ice#015#012a=fingerprint:sha-256 72:54:87:EC:D2:4C:D1:70:C2:FE:69:08:20:5C:92:1D:E0:EA:BD:45:09:E0:90:62:27:B6:34:60:54:E2:99:28#015#012a=setup:actpass#015#012a=mid:audio#015#012a=sendrecv#015#012a=crypto:0 AES_CM_128_HMAC_SHA1_32 inline:ERj6OGgpgTMY1kD3wmxN3oIOD8L5vL5tKAtmHM0f#015#012a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:UT3fhVoULjUtaHJdfLkFHqTbAEfb3oKDWqBY3ahK#015#012a=rtpmap:111 opus/48000/2#015#012a=fmtp:111 minptime=10#015#012a=rtpmap:103 ISAC/16000#015#012a=rtpmap:104 ISAC/32000#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:106 CN/32000#015#012a=rtpmap:105 CN/16000#015#012a=rtpmap:13 CN/8000#015#012a=rtpmap:126 telephon Apr 2 14:10:47 u363id562 kamailio[27059]: NOTICE: acc [acc.c:315]: acc_log_request(): ACC: call missed: timestamp=1396433447;method=INVITE;from_tag=a5uk5lnjvf;to_tag=f7a91f721d721d45;call_id=oginba5h5r8h1hk3kngu;code=488;reason=Not Acceptable Here;src_user=wsclient;src_domain=testers.com <http://testers.com>;src_ip=2.2.2.2;dst_ouser=gsclient;dst_user=gsclient;dst_domain=192.168.0.106 Apr 2 14:10:47 u363id562 mediaproxy-ng[18742]: Got valid command from 127.0.0.1:55835 <http://127.0.0.1:55835>: offer - { "sdp": "v=0#015#012o=- 7083457405291314669 2 IN IP4 127.0.0.1#015#012s=-#015#012t=0 0#015#012a=group:BUNDLE audio#015#012a=msid-semantic: WMS No46lGs0HIghRI0dBCknwdhJyR8IlJ3FPqI3#015#012m=audio 64860 RTP/SAVPF 111 103 104 0 8 106 105 13 126#015#012c=IN IP4 2.2.2.2#015#012a=rtcp:64860 IN IP4 2.2.2.2#015#012a=candidate:2999745851 1 udp 2113937151 192.168.56.1 64859 typ host generation 0#015#012a=candidate:2999745851 2 udp 2113937151 192.168.56.1 64859 typ host generation 0#015#012a=candidate:3350409123 1 udp 2113937151 192.168.0.101 64860 typ host generation 0#015#012a=candidate:3350409123 2 udp 2113937151 192.168.0.101 64860 typ host generation 0#015#012a=candidate:4233069003 1 tcp 1509957375 192.168.56.1 0 typ host generation 0#015#012a=candidate:4233069003 2 tcp 1509957375 192.168.56.1 0 typ host generation 0#015#012a=candidate:2301678419 1 tcp 1509957375 192.168.0.101 0 typ host generation 0#015#012a=candidate:2301678419 2 tcp 1509957375 192.168.0.101 0 typ host generation 0#015#012a=candidate:1190865175 1 udp 1845501695 2.2.2.2 64860 typ srflx raddr 192.168.0.101 rport 64860 generation 0#015#012a=candidate:1190865175 2 udp 1845501695 2.2.2.2 64860 typ srflx raddr 192.168.0.101 rport 64860 generation 0#015#012a=ice-ufrag:Nuzos2pMurFvifge#015#012a=ice-pwd:AAcKZc38Sp21Y/kFzdYxFGjt#015#012a=ice-options:google-ice#015#012a=fingerprint:sha-256 72:54:87:EC:D2:4C:D1:70:C2:FE:69:08:20:5C:92:1D:E0:EA:BD:45:09:E0:90:62:27:B6:34:60:54:E2:99:28#015#012a=setup:actpass#015#012a=mid:audio#015#012a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level#015#012a=sendrecv#015#012a=rtcp-mux#015#012a=crypto:0 AES_CM_128_HMAC_SHA1_32 inline:ERj6OGgpgTMY1kD3wmxN3oIOD8L5vL5tKAtmHM0f#015#012a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:UT3fhVoULjUtaHJdfLkFHqTbAEfb3oKDWqBY3ahK#015#012a=rtpmap:111 opus/48000/2#015#012a=fmtp:111 minptime=10#015#012a=rtpmap:103 ISAC/16000#015#012a=rtpmap:104 ISAC/32000#015#012a=rtpmap:0 PCMU/8000#015 Apr 2 14:10:47 u363id562 mediaproxy-ng[18742]: Returning to SIP proxy: d3:sdp925:v=0#015#012o=- 7083457405291314669 2 IN IP4 1.1.1.1#015#012s=-#015#012t=0 0#015#012a=group:BUNDLE audio#015#012a=msid-semantic: WMS No46lGs0HIghRI0dBCknwdhJyR8IlJ3FPqI3#015#012m=audio 30032 RTP/AVP 111 103 104 0 8 106 105 13 126#015#012c=IN IP4 1.1.1.1#015#012a=fingerprint:sha-256 72:54:87:EC:D2:4C:D1:70:C2:FE:69:08:20:5C:92:1D:E0:EA:BD:45:09:E0:90:62:27:B6:34:60:54:E2:99:28#015#012a=setup:actpass#015#012a=mid:audio#015#012a=sendrecv#015#012a=rtpmap:111 opus/48000/2#015#012a=fmtp:111 minptime=10#015#012a=rtpmap:103 ISAC/16000#015#012a=rtpmap:104 ISAC/32000#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:106 CN/32000#015#012a=rtpmap:105 CN/16000#015#012a=rtpmap:13 CN/8000#015#012a=rtpmap:126 telephone-event/8000#015#012a=maxptime:60#015#012a=ssrc:1883467027 cname:xLrdjUv0kmdPbie/#015#012a=ssrc:1883467027 msid:No46lGs0HIghRI0dBCknwdhJyR8IlJ3FPqI3 2cddb28d-832f-4b95-a39f-cc2e39cf620c#015#012a=ssrc:1883467027 mslabel:No46lGs0HIghRI0dBCknwdhJyR8IlJ3FPqI3#015#012a=ssrc:1883467027 label:2cddb28d-832f-4b95-a39f-cc2e39cf620c#015#012a=rtcp:30033#015#0126:result2:oke Apr 2 14:10:47 u363id562 mediaproxy-ng[18742]: Got valid command from 127.0.0.1:55835 <http://127.0.0.1:55835>: offer - { "sdp": "v=0#015#012o=- 7083457405291314669 2 IN IP4 127.0.0.1#015#012s=-#015#012t=0 0#015#012a=group:BUNDLE audio#015#012a=msid-semantic: WMS No46lGs0HIghRI0dBCknwdhJyR8IlJ3FPqI3#015#012m=audio 64860 RTP/SAVPF 111 103 104 0 8 106 105 13 126#015#012c=IN IP4 2.2.2.2#015#012a=rtcp:64860 IN IP4 2.2.2.2#015#012a=candidate:2999745851 1 udp 2113937151 192.168.56.1 64859 typ host generation 0#015#012a=candidate:2999745851 2 udp 2113937151 192.168.56.1 64859 typ host generation 0#015#012a=candidate:3350409123 1 udp 2113937151 192.168.0.101 64860 typ host generation 0#015#012a=candidate:3350409123 2 udp 2113937151 192.168.0.101 64860 typ host generation 0#015#012a=candidate:4233069003 1 tcp 1509957375 192.168.56.1 0 typ host generation 0#015#012a=candidate:4233069003 2 tcp 1509957375 192.168.56.1 0 typ host generation 0#015#012a=candidate:2301678419 1 tcp 1509957375 192.168.0.101 0 typ host generation 0#015#012a=candidate:2301678419 2 tcp 1509957375 192.168.0.101 0 typ host generation 0#015#012a=candidate:1190865175 1 udp 1845501695 2.2.2.2 64860 typ srflx raddr 192.168.0.101 rport 64860 generation 0#015#012a=candidate:1190865175 2 udp 1845501695 2.2.2.2 64860 typ srflx raddr 192.168.0.101 rport 64860 generation 0#015#012a=ice-ufrag:Nuzos2pMurFvifge#015#012a=ice-pwd:AAcKZc38Sp21Y/kFzdYxFGjt#015#012a=ice-options:google-ice#015#012a=fingerprint:sha-256 72:54:87:EC:D2:4C:D1:70:C2:FE:69:08:20:5C:92:1D:E0:EA:BD:45:09:E0:90:62:27:B6:34:60:54:E2:99:28#015#012a=setup:actpass#015#012a=mid:audio#015#012a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level#015#012a=sendrecv#015#012a=rtcp-mux#015#012a=crypto:0 AES_CM_128_HMAC_SHA1_32 inline:ERj6OGgpgTMY1kD3wmxN3oIOD8L5vL5tKAtmHM0f#015#012a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:UT3fhVoULjUtaHJdfLkFHqTbAEfb3oKDWqBY3ahK#015#012a=rtpmap:111 opus/48000/2#015#012a=fmtp:111 minptime=10#015#012a=rtpmap:103 ISAC/16000#015#012a=rtpmap:104 ISAC/32000#015#012a=rtpmap:0 PCMU/8000#015 Apr 2 14:10:47 u363id562 mediaproxy-ng[18742]: Returning to SIP proxy: d3:sdp2211:v=0#015#012o=- 7083457405291314669 2 IN IP4 1.1.1.1#015#012s=-#015#012t=0 0#015#012a=group:BUNDLE audio#015#012a=msid-semantic: WMS No46lGs0HIghRI0dBCknwdhJyR8IlJ3FPqI3#015#012m=audio 30032 RTP/SAVPF 111 103 104 0 8 106 105 13 126#015#012c=IN IP4 1.1.1.1#015#012a=candidate:2999745851 1 udp 2113937151 192.168.56.1 64859 typ host generation 0#015#012a=candidate:2999745851 2 udp 2113937151 192.168.56.1 64859 typ host generation 0#015#012a=candidate:3350409123 1 udp 2113937151 192.168.0.101 64860 typ host generation 0#015#012a=candidate:3350409123 2 udp 2113937151 192.168.0.101 64860 typ host generation 0#015#012a=candidate:4233069003 1 tcp 1509957375 192.168.56.1 0 typ host generation 0#015#012a=candidate:4233069003 2 tcp 1509957375 192.168.56.1 0 typ host generation 0#015#012a=candidate:2301678419 1 tcp 1509957375 192.168.0.101 0 typ host generation 0#015#012a=candidate:2301678419 2 tcp 1509957375 192.168.0.101 0 typ host generation 0#015#012a=candidate:1190865175 1 udp 1845501695 2.2.2.2 64860 typ srflx raddr 192.168.0.101 rport 64860 generation 0#015#012a=candidate:1190865175 2 udp 1845501695 2.2.2.2 64860 typ srflx raddr 192.168.0.101 rport 64860 generation 0#015#012a=ice-ufrag:Nuzos2pMurFvifge#015#012a=ice-pwd:AAcKZc38Sp21Y/kFzdYxFGjt#015#012a=ice-options:google-ice#015#012a=fingerprint:sha-256 72:54:87:EC:D2:4C:D1:70:C2:FE:69:08:20:5C:92:1D:E0:EA:BD:45:09:E0:90:62:27:B6:34:60:54:E2:99:28#015#012a=setup:actpass#015#012a=mid:audio#015#012a=sendrecv#015#012a=crypto:0 AES_CM_128_HMAC_SHA1_32 inline:ERj6OGgpgTMY1kD3wmxN3oIOD8L5vL5tKAtmHM0f#015#012a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:UT3fhVoULjUtaHJdfLkFHqTbAEfb3oKDWqBY3ahK#015#012a=rtpmap:111 opus/48000/2#015#012a=fmtp:111 minptime=10#015#012a=rtpmap:103 ISAC/16000#015#012a=rtpmap:104 ISAC/32000#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:106 CN/32000#015#012a=rtpmap:105 CN/16000#015#012a=rtpmap:13 CN/8000#015#012a=rtpmap:126 telephon Apr 2 14:10:52 u363id562 mediaproxy-ng[18742]: Got valid command from 127.0.0.1:40131 <http://127.0.0.1:40131>: answer - { "sdp": "v=0#015#012o=gsclient 8000 8000 IN IP4 192.168.0.106#015#012s=SIP Call#015#012c=IN IP4 192.168.0.106#015#012t=0 0#015#012m=audio 5030 RTP/AVP 0 13#015#012a=sendrecv#015#012a=rtpmap:0 PCMU/8000#015#012a=ptime:20#015#012m=audio 0 RTP/SAVPF 111 103 104 0 8 106 105 13 126#015#012", "ICE": "force", "flags": [ "force", "trust-address" ], "replace": [ "origin", "session-connection" ], "transport-protocol": "RTP/SAVPF", "call-id": "oginba5h5r8h1hk3kngu", "received-from": [ "IP4", "2.2.2.2" ], "from-tag": "a5uk5lnjvf", "to-tag": "7067a267ea14db11", "command": "answer" } Apr 2 14:10:52 u363id562 mediaproxy-ng[18742]: [oginba5h5r8h1hk3kngu - ] Got LOOKUP, but no usable callstreams found Apr 2 14:10:52 u363id562 mediaproxy-ng[18742]: Error rewriting SDP Apr 2 14:10:52 u363id562 mediaproxy-ng[18742]: Protocol error in packet from 127.0.0.1:40131 <http://127.0.0.1:40131>: Error rewriting SDP [d3:sdp216:v=0#015#012o=gsclient 8000 8000 IN IP4 192.168.0.106#015#012s=SIP Call#015#012c=IN IP4 192.168.0.106#015#012t=0 0#015#012m=audio 5030 RTP/AVP 0 13#015#012a=sendrecv#015#012a=rtpmap:0 PCMU/8000#015#012a=ptime:20#015#012m=audio 0 RTP/SAVPF 111 103 104 0 8 106 105 13 126#015#0123:ICE5:force5:flagsl5:force13:trust-addresse7:replacel6:origin18:session-connectione18:transport-protocol9:RTP/SAVPF7:call-id20:oginba5h5r8h1hk3kngu13:received-froml3:IP412:2.2.2.2e8:from-tag10:a5uk5lnjvf6:to-tag16:7067a267ea14db117:command6:answere] Apr 2 14:10:52 u363id562 mediaproxy-ng[18742]: Returning to SIP proxy: d6:result5:error12:error-reason19:Error rewriting SDPe Apr 2 14:10:52 u363id562 kamailio[27056]: ERROR: rtpproxy-ng [rtpproxy.c:1346]: rtpp_function_call(): proxy replied with error: Error rewriting SDP Apr 2 14:10:52 u363id562 kamailio[27056]: NOTICE: acc [acc.c:315]: acc_log_request(): ACC: transaction answered: timestamp=1396433452;method=INVITE;from_tag=a5uk5lnjvf;to_tag=7067a267ea14d… <http://testers.com>;src_ip=2.2.2.2;dst_ouser=gsclient;dst_user=gsclient;dst_domain=192.168.0.106 Apr 2 14:10:52 u363id562 mediaproxy-ng[18742]: Got valid command from 127.0.0.1:39795 <http://127.0.0.1:39795>: delete - { "call-id": "oginba5h5r8h1hk3kngu", "received-from": [ "IP4", "2.2.2.2" ], "from-tag": "a5uk5lnjvf", "command": "delete" } Apr 2 14:10:52 u363id562 mediaproxy-ng[18742]: [oginba5h5r8h1hk3kngu] Deleting full call Apr 2 14:10:52 u363id562 mediaproxy-ng[18742]: [oginba5h5r8h1hk3kngu] Final packet stats: Apr 2 14:10:52 u363id562 mediaproxy-ng[18742]: [oginba5h5r8h1hk3kngu] --- side A: RTP[30032] 0 p, 0 b, 0 e; RTCP[0] 0 p, 0 b, 30033 e; side B: RTP[0] 0 p, 0 b, 0 e; RTCP[0] 0 p, 30034 b, 0 e Apr 2 14:10:52 u363id562 mediaproxy-ng[18742]: [oginba5h5r8h1hk3kngu] --- side A: RTP[0] 0 p, 0 b, 0 e; RTCP[0] 0 p, 0 b, 0 e; side B: RTP[0] 0 p, 0 b, 0 e; RTCP[0] 0 p, 0 b, 0 e Apr 2 14:10:52 u363id562 mediaproxy-ng[18742]: [oginba5h5r8h1hk3kngu] --- side A: RTP[0] 0 p, 0 b, 0 e; RTCP[0] 0 p, 0 b, 0 e; side B: RTP[0] 0 p, 0 b, 0 e; RTCP[0] 0 p, 0 b, 0 e Apr 2 14:10:52 u363id562 mediaproxy-ng[18742]: Returning to SIP proxy: d7:createdi1396433447e7:streamslld3:tag10:a5uk5lnjvf6:status34:known but unconfirmed peer address5:statsd3:rtpd8:countersd7:packetsi0e5:bytesi0e6:errorsi0ee12:peer addressd6:family4:IPv47:address12:2.2.2.24:porti64860ee23:advertised peer addressd6:family4:IPv47:address12:2.2.2.24:porti64860ee10:local porti30032ee4:rtcpd8:countersd7:packetsi0e5:bytesi0e6:errorsi0ee12:peer addressd6:family4:IPv47:address12:2.2.2.24:porti64861ee23:advertised peer addressd6:family4:IPv47:address12:2.2.2.24:porti64861ee10:local porti30033eeeed3:tag16:7067a267ea14db116:status34:known but unconfirmed peer address5:statsd3:rtpd8:countersd7:packetsi0e5:bytesi0e6:errorsi0ee12:peer addressd6:family4:IPv47:address13:192.168.0.1064:porti5030ee23:advertised peer addressd6:family4:IPv47:address13:192.168.0.1064:porti5030ee10:local porti30034ee4:rtcpd8:countersd7:packetsi0e5:bytesi0e6:errorsi0ee12:peer addressd6:family4:IPv47:address13:192.168.0.1064:porti5031ee23:advertised peer addressd6:family4:IPv47:address13:192.168.0.1064:porti5031ee10:local porti30035eeeeee6:totalsd5:inputd3:rtpd7:packetsi0e5:bytesi0e6:errorsi0ee4:rtcpd7:packetsi0e5:bytesi0e6:errorsi0eee6:outputd3:rtpd7:packetsi0e5:bytesi0e6:errorsi0ee4:rtcpd7:packetsi0e5:bytesi0e6:errorsi0eeee6:result2:oke Apr 2 14:10:53 u363id562 mediaproxy-ng[18742]: Got valid command from 127.0.0.1:55835 <http://127.0.0.1:55835>: answer - { "sdp": "v=0#015#012o=gsclient 8000 8001 IN IP4 192.168.0.106#015#012s=SIP Call#015#012c=IN IP4 192.168.0.106#015#012t=0 0#015#012m=audio 5030 RTP/AVP 0 13#015#012a=sendrecv#015#012a=rtpmap:0 PCMU/8000#015#012a=ptime:20#015#012m=audio 0 RTP/SAVPF 111 103 104 0 8 106 105 13 126#015#012", "ICE": "force", "flags": [ "force", "trust-address" ], "replace": [ "origin", "session-connection" ], "transport-protocol": "RTP/SAVPF", "call-id": "oginba5h5r8h1hk3kngu", "received-from": [ "IP4", "2.2.2.2" ], "from-tag": "a5uk5lnjvf", "to-tag": "7067a267ea14db11", "command": "answer" } Apr 2 14:10:53 u363id562 mediaproxy-ng[18742]: Protocol error in packet from 127.0.0.1:55835 <http://127.0.0.1:55835>: Unknown call-id [d3:sdp216:v=0#015#012o=gsclient 8000 8001 IN IP4 192.168.0.106#015#012s=SIP Call#015#012c=IN IP4 192.168.0.106#015#012t=0 0#015#012m=audio 5030 RTP/AVP 0 13#015#012a=sendrecv#015#012a=rtpmap:0 PCMU/8000#015#012a=ptime:20#015#012m=audio 0 RTP/SAVPF 111 103 104 0 8 106 105 13 126#015#0123:ICE5:force5:flagsl5:force13:trust-addresse7:replacel6:origin18:session-connectione18:transport-protocol9:RTP/SAVPF7:call-id20:oginba5h5r8h1hk3kngu13:received-froml3:IP412:2.2.2.2e8:from-tag10:a5uk5lnjvf6:to-tag16:7067a267ea14db117:command6:answere] Apr 2 14:10:53 u363id562 mediaproxy-ng[18742]: Returning to SIP proxy: d6:result5:error12:error-reason15:Unknown call-ide Apr 2 14:10:53 u363id562 kamailio[27059]: ERROR: rtpproxy-ng [rtpproxy.c:1346]: rtpp_function_call(): proxy replied with error: Unknown call-id Apr 2 14:10:55 u363id562 mediaproxy-ng[18742]: Got valid command from 127.0.0.1:34407 <http://127.0.0.1:34407>: answer - { "sdp": "v=0#015#012o=gsclient 8000 8002 IN IP4 192.168.0.106#015#012s=SIP Call#015#012c=IN IP4 192.168.0.106#015#012t=0 0#015#012m=audio 5030 RTP/AVP 0 13#015#012a=sendrecv#015#012a=rtpmap:0 PCMU/8000#015#012a=ptime:20#015#012m=audio 0 RTP/SAVPF 111 103 104 0 8 106 105 13 126#015#012", "ICE": "force", "flags": [ "force", "trust-address" ], "replace": [ "origin", "session-connection" ], "transport-protocol": "RTP/SAVPF", "call-id": "oginba5h5r8h1hk3kngu", "received-from": [ "IP4", "2.2.2.2" ], "from-tag": "a5uk5lnjvf", "to-tag": "7067a267ea14db11", "command": "answer" } Apr 2 14:10:55 u363id562 mediaproxy-ng[18742]: Protocol error in packet from 127.0.0.1:34407 <http://127.0.0.1:34407>: Unknown call-id [d3:sdp216:v=0#015#012o=gsclient 8000 8002 IN IP4 192.168.0.106#015#012s=SIP Call#015#012c=IN IP4 192.168.0.106#015#012t=0 0#015#012m=audio 5030 RTP/AVP 0 13#015#012a=sendrecv#015#012a=rtpmap:0 PCMU/8000#015#012a=ptime:20#015#012m=audio 0 RTP/SAVPF 111 103 104 0 8 106 105 13 126#015#0123:ICE5:force5:flagsl5:force13:trust-addresse7:replacel6:origin18:session-connectione18:transport-protocol9:RTP/SAVPF7:call-id20:oginba5h5r8h1hk3kngu13:received-froml3:IP412:2.2.2.2e8:from-tag10:a5uk5lnjvf6:to-tag16:7067a267ea14db117:command6:answere] Apr 2 14:10:55 u363id562 mediaproxy-ng[18742]: Returning to SIP proxy: d6:result5:error12:error-reason15:Unknown call-ide Apr 2 14:10:55 u363id562 kamailio[27058]: ERROR: rtpproxy-ng [rtpproxy.c:1346]: rtpp_function_call(): proxy replied with error: Unknown call-id Apr 2 14:11:07 u363id562 mediaproxy-ng[18742]: Got valid command from 127.0.0.1:55835 <http://127.0.0.1:55835>: delete - { "call-id": "oginba5h5r8h1hk3kngu", "received-from": [ "IP4", "2.2.2.2" ], "from-tag": "7067a267ea14db11", "command": "delete" } Apr 2 14:11:07 u363id562 mediaproxy-ng[18742]: [oginba5h5r8h1hk3kngu] Call-ID to delete not found Apr 2 14:11:07 u363id562 mediaproxy-ng[18742]: Returning to SIP proxy: d7:warning38:Call-ID not found or tags didn't match6:result2:oke Apr 2 14:11:07 u363id562 kamailio[27074]: NOTICE: acc [acc.c:315]: acc_log_request(): ACC: transaction answered: timestamp=1396433467;method=BYE;from_tag=7067a267ea14db11;to_tag=a5uk5lnjvf;call_id=oginba5h5r8h1hk3kngu;code=481;reason=Call/Transaction Does Not Exist;src_user=gsclient;src_domain=testers.com <http://testers.com>;src_ip=2.2.2.2;dst_ouser=wsclient;dst_user=wsclient;dst_domain=testers.com <http://testers.com> 2014-04-01 21:41 GMT+03:00 Richard Fuchs &lt;rfuchs(a)sipwise.com <mailto:rfuchs@sipwise.com>>: Hey, Unfortunately your packet dumps are truncated and don't show the complete SDP bodies. It would also be interesting to see which options and parameters are passed to mediaproxy-ng when processing the SDP. You would find this info in the log produced by mediaproxy-ng, which should also include the full SDP bodies going in and out (unless your syslog daemon also truncates those messages). So, the most useful way to debug this is to post the complete log lines. cheers On 04/01/14 13:19, Olli Heiskanen wrote: could <mailto:wsclient@testers.com <mailto:wsclient@testers.com>> and <mailto:gsclient@testers.com <mailto:gsclient@testers.com>> and I try to make something so I'd solution is the ****************************************************************************** <http://1.1.1.1:5060> -> kj59uak271em.invalid;rport=38986;received=2.2.2.2;branch=z9hG4bK9891267. <mailto:sip%3Agsclient@testers.com <mailto:sip%253Agsclient@testers.com>>>. <mailto:sip%253Awsclient@testers.com>>>;tag=hhcd99tmvm. <mailto:sip%253Awsclient@testers.com>>;gr=urn:uuid:f6014564-88cb-4f57-9ae5-3b4336ef9db8;ob;alias=2.2.2.2~38986~5;alias=2.2.2.2~38986~5>. <http://2.2.2.2:38986> -> <http://2.2.2.2:5066> -> kj59uak271em.invalid;rport=38986;received=2.2.2.2;branch=z9hG4bK9891267. > Record-Route: <sip:1.1.1.1;r2=on;lr=on;nat=yes>. > Record-Route: <sip:1.1.1.1;transport=ws;r2=on;lr=on;nat=yes>. <mailto:sip%253Awsclient@testers.com>>>;tag=hhcd99tmvm. <mailto:sip%253Agsclient@testers.com>>>;tag=7875f08763872c34. <http://1.1.1.1:5060> -> > 2.2.2.2:5066 <http://2.2.2.2:5066> <http://2.2.2.2:5066> > ACK sip:gsclient@192.168.0.106:5066;transport=udp SIP/2.0. > Via: SIP/2.0/UDP > 1.1.1.1;branch=z9hG4bKb703.fbb259c1d8c17e163876ec760e086145.0. > <mailto:sip%3Agsclient@testers.com <mailto:sip%253Agsclient@testers.com>>>;tag=7875f08763872c34. <mailto:sip%253Awsclient@testers.com>>>;tag=hhcd99tmvm. <http://1.1.1.1:5060> -> kj59uak271em.invalid;rport=38986;received=2.2.2.2;branch=z9hG4bK9891267. <mailto:sip%3Agsclient@testers.com <mailto:sip%253Agsclient@testers.com>>>. <mailto:sip%253Awsclient@testers.com>>>;tag=hhcd99tmvm. <mailto:sip%253Awsclient@testers.com>>;gr=urn:uuid:f6014564-88cb-4f57-9ae5-3b4336ef9db8;ob;alias=2.2.2.2~38986~5;alias=2.2.2.2~38986~5>. 72:54:87:EC:D2:4C:D1:70:C2:FE:69:08:20:5C:92:1D:E0:EA:BD:45:09:E0:90:62:27:B6:34:60:54:E2:99:28. <http://2.2.2.2:5066> -> kj59uak271em.invalid;rport=38986;received=2.2.2.2;branch=z9hG4bK9891267. > Record-Route: <sip:1.1.1.1;r2=on;lr=on;nat=yes>. > Record-Route: <sip:1.1.1.1;transport=ws;r2=on;lr=on;nat=yes>. <mailto:sip%253Awsclient@testers.com>>>;tag=hhcd99tmvm. <mailto:sip%253Agsclient@testers.com>>>;tag=fb215901a251c9a0. INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE. <http://1.1.1.1:5060> -> kj59uak271em.invalid;rport=38986;received=2.2.2.2;branch=z9hG4bK9891267. > Record-Route: <sip:1.1.1.1;r2=on;lr=on;nat=yes>. > Record-Route: <sip:1.1.1.1;transport=ws;r2=on;lr=on;nat=yes>. <mailto:sip%253Awsclient@testers.com>>>;tag=hhcd99tmvm. <mailto:sip%253Agsclient@testers.com>>>;tag=fb215901a251c9a0. INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE. ****************************************************************************** list _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Hello, Thanks, I'll give that a try and post back. I guess I install and run it just like mediaproxy-ng?

I'll also try different sip clients like zoiper etc. One thing that occurred to me based on the fact that the sdp is faulty, as I did this test from the slides here: http://www.slideshare.net/crocodilertc/webrtc-websockets I wonder if the configuration (from page 53 in the slides) need tweaking/fixing? Here's a snippet from my config:

Olli Heiskanen writes: in order to simplify the above, how about introducing a new function sdp_with_transport_like(transport)? that function would return 1 if string of the param is included in the transport string. then the above two lines would become if (sdp_with_transport_like("SAVPF")) ... if ok, i can write the new function. -- juha _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Olli Heiskanen writes: I'll what comes to peter's slideshare failure_route example, i think it only works in very simple unrealistic scenario when there is no forking or serial routing. also, its nathelper handling is unnecessary when websocket sip ua, such as jssip, supports gruu. -- juha _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

On 04/08/14 03:00, Olli Heiskanen wrote: Those should be fixed now. cheers _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Indeed, which works for simple demos and fits on a single slide - the whole purpose of that presentation. If someone is building a production system they really need to understand the various use-cases they will see and write their Kamailio configuration properly. Regards, Peter On 6 April 2014 19:58, Juha Heinanen &lt;jh(a)tutpro.com&gt; wrote: -- Peter Dunkley Technical Director Acision _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

On 04/10/14 09:26, Olli Heiskanen wrote: Unfortunately the log lines are cut off and don't include the entire command packet to rtpengine, but my guess is that you omitted the ICE handling parameter, which (as of a few days ago) forces rtpengine into passthrough mode, which means that most of the RTP/SAVPF attributes are left in place. My guess is that this confuses the grandstream. You should use either ICE=force or ICE=remove (formerly "+" or "-" flags) to make sure rtpengine is actually able to bridge between the protocols. You should also add the "rtcp-mux-demux" flag (through rtpengine module) in case the grandstream gets confused by rtcp-mux being offered. With those two in place, the resulting RTP/AVP SDP should be very small and clean. cheers _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

On 04/12/14 09:31, Olli Heiskanen wrote: Type. I see that you're trying to talk RTP/SAVPF in all cases. Is this what you want? Or do you want to bridge between RTP/AVP and /SAVPF? Assuming that the granstream doesn't support SRTP, you should replace the first and the last occurrences in this snippet with "RTP/AVP". It's not rtpengine which is cutting off the log lines, it's probably the syslog daemon handling them. On my system I have rsyslogd and it's handling very long log lines quite nicely. I believe ngrep works on a per-packet basis only, which fails as soon as the UDP packets get fragmented. I have more luck using wireshark as it reassembles fragments. cheers _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

On 20/07/14 01:15 PM, Olli Heiskanen wrote: ... There may be something off in my Asterisk configs since it's Asterisk This looks a lot like the issue discussed here: http://lists.sip-router.org/pipermail/sr-dev/2014-July/024507.html The solution was: http://lists.sip-router.org/pipermail/sr-dev/2014-July/024519.html cheers _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

On 07/23/14 05:03, Olli Heiskanen wrote: ... Yes, I see there's an a=setup:actpass in the answer, which shouldn't be there. Could you post the entire log for the whole call (just the rtpengine part) so I can see why it's putting that there? cheers _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

On 07/23/14 11:01, Olli Heiskanen wrote: ... I can't seem to reproduce this, when I run through the same sequence, the answer comes out as a=setup:active as it should. Are you sure you're using the latest version from master? cheers _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

On 24/07/14 09:27 AM, Olli Heiskanen wrote: I can't imagine what. The selection of active/passive is pretty straightforward and doesn't depend on much of anything. The offer/answer/delete commands as reproduced in full in the log are all the input that rtpengine gets, and with the same input it should always produce the same result. The only thing to consider is that in your pasted log, the "offer" command is truncated in the SDP and so some of the flags are missing. I don't think they would make a lot of difference though, and I tried a few different variations and still couldn't reproduce it. cheers _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users