Good intro to mediaproxy setup?

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Good intro to mediaproxy setup?

Matti Zemack

Hi all,

 

Could anyone please point me in the direction of a setup guide regarding mediaproxy.

I seem to get some sort of TLS problem between a dispatcher and the relay...

 

Just trying the simple demo setup.

 

Any help much appreciated.

 

 

Mediaproxy-relay syslog output;

Jun  3 12:10:43 mediaproxy media-relay[32632]: debug: Connected to dispatcher at 172.16.245.128:25060

Jun  3 12:11:23 mediaproxy media-relay[32632]: error: missed 3 keepalive answers in a row. assuming the connection is down.

Jun  3 12:11:23 mediaproxy media-relay[32632]: error: Connection with dispatcher at 172.16.245.128:25060 was lost: TCP connection timed out.

Jun  3 12:11:25 mediaproxy media-relay[32632]: debug: Connected to dispatcher at 172.16.245.128:25060

Jun  3 12:12:05 mediaproxy media-relay[32632]: error: missed 3 keepalive answers in a row. assuming the connection is down.

Jun  3 12:12:05 mediaproxy media-relay[32632]: error: Connection with dispatcher at 172.16.245.128:25060 was lost: TCP connection timed out.

Jun  3 12:12:06 mediaproxy media-relay[32632]: debug: Connected to dispatcher at 172.16.245.128:25060

 

Mediaproxy-dispatcher syslog output;

Jun  3 18:25:10 voipserver media-dispatcher[5732]: error: Could not decode reply from relay 172.16.1.24: ping

Jun  3 18:25:19 voipserver media-dispatcher[5732]: error: Could not decode reply from relay 172.16.1.24: ping

Jun  3 18:25:29 voipserver media-dispatcher[5732]: error: Could not decode reply from relay 172.16.1.24: ping

Jun  3 18:25:39 voipserver media-dispatcher[5732]: error: Connection with relay at 172.16.1.24 was lost: A TLS packet with unexpected length was received.

Jun  3 18:25:51 voipserver media-dispatcher[5732]: error: Could not decode reply from relay 172.16.1.24: ping

Jun  3 18:26:01 voipserver media-dispatcher[5732]: error: Could not decode reply from relay 172.16.1.24: ping

Jun  3 18:26:11 voipserver media-dispatcher[5732]: error: Could not decode reply from relay 172.16.1.24: ping

Jun  3 18:26:21 voipserver media-dispatcher[5732]: error: Connection with relay at 172.16.1.24 was lost: A TLS packet with unexpected length was received.

 

 

Best Regards,

Matti Zemack, Stockhlm, Sweden

 


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Good intro to mediaproxy setup?

Dan Pascu
You seem to be mixing different versions of the dispatcher and the  
relay. Stick with the latest for both

On 3 Jun 2009, at 19:43, Matti Zemack wrote:

> Hi all,
>
> Could anyone please point me in the direction of a setup guide  
> regarding mediaproxy.
> I seem to get some sort of TLS problem between a dispatcher and the  
> relay...
>
> Just trying the simple demo setup.
>
> Any help much appreciated.
>
>
> Mediaproxy-relay syslog output;
> Jun  3 12:10:43 mediaproxy media-relay[32632]: debug: Connected to  
> dispatcher at 172.16.245.128:25060
> Jun  3 12:11:23 mediaproxy media-relay[32632]: error: missed 3  
> keepalive answers in a row. assuming the connection is down.
> Jun  3 12:11:23 mediaproxy media-relay[32632]: error: Connection  
> with dispatcher at 172.16.245.128:25060 was lost: TCP connection  
> timed out.
> Jun  3 12:11:25 mediaproxy media-relay[32632]: debug: Connected to  
> dispatcher at 172.16.245.128:25060
> Jun  3 12:12:05 mediaproxy media-relay[32632]: error: missed 3  
> keepalive answers in a row. assuming the connection is down.
> Jun  3 12:12:05 mediaproxy media-relay[32632]: error: Connection  
> with dispatcher at 172.16.245.128:25060 was lost: TCP connection  
> timed out.
> Jun  3 12:12:06 mediaproxy media-relay[32632]: debug: Connected to  
> dispatcher at 172.16.245.128:25060
>
> Mediaproxy-dispatcher syslog output;
> Jun  3 18:25:10 voipserver media-dispatcher[5732]: error: Could not  
> decode reply from relay 172.16.1.24: ping
> Jun  3 18:25:19 voipserver media-dispatcher[5732]: error: Could not  
> decode reply from relay 172.16.1.24: ping
> Jun  3 18:25:29 voipserver media-dispatcher[5732]: error: Could not  
> decode reply from relay 172.16.1.24: ping
> Jun  3 18:25:39 voipserver media-dispatcher[5732]: error: Connection  
> with relay at 172.16.1.24 was lost: A TLS packet with unexpected  
> length was received.
> Jun  3 18:25:51 voipserver media-dispatcher[5732]: error: Could not  
> decode reply from relay 172.16.1.24: ping
> Jun  3 18:26:01 voipserver media-dispatcher[5732]: error: Could not  
> decode reply from relay 172.16.1.24: ping
> Jun  3 18:26:11 voipserver media-dispatcher[5732]: error: Could not  
> decode reply from relay 172.16.1.24: ping
> Jun  3 18:26:21 voipserver media-dispatcher[5732]: error: Connection  
> with relay at 172.16.1.24 was lost: A TLS packet with unexpected  
> length was received.
>
>
> Best Regards,
> Matti Zemack, Stockhlm, Sweden
>
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users


--
Dan




_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Good intro to mediaproxy setup?

Matti Zemack
Hi Dan,

Thanks. Indeed I was running 2.3.2 on the dispatcher, and 2.3.4 as
relay.
:-)
And after googling tonight I found the notices regarding new keep alive
in 2.3.3...

Regards,
/Matti


-----Original Message-----
From: Dan Pascu [mailto:[hidden email]]
Sent: den 4 juni 2009 01:44
To: Matti Zemack
Cc: [hidden email]
Subject: Re: [OpenSIPS-Users] Good intro to mediaproxy setup?

You seem to be mixing different versions of the dispatcher and the  
relay. Stick with the latest for both


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Good intro to mediaproxy setup?

bay2x1
Hi Matti,

I am only encountering only this error error: Connection with relay at 172.16.1.24 was lost: A TLS packet with unexpected length was received.  I have already check both version for my dispatcher and relay they have the same version 2.3.4.  The configuration before was working properly, I didn't change any mediaproxy related configuration that is why I am wondering what I did wrong?  

I am also encountering this warning everytime I run both mediaproxy relay and dispatcher:

Stopping MediaProxy Dispatcher:                            [  OK  ]
Starting MediaProxy Dispatcher: /usr/lib/python2.5/site-packages/application/configuration/__init__.py:137: DeprecationWarning: get_option is deprecated in favor of get_setting and will be removed in 1.2.0.
  warn("get_option is deprecated in favor of get_setting and will be removed in 1.2.0.", DeprecationWarning)
                                                           [  OK  ]



Matti Zemack wrote
Hi Dan,

Thanks. Indeed I was running 2.3.2 on the dispatcher, and 2.3.4 as
relay.
:-)
And after googling tonight I found the notices regarding new keep alive
in 2.3.3...

Regards,
/Matti


-----Original Message-----
From: Dan Pascu [mailto:dan@ag-projects.com]
Sent: den 4 juni 2009 01:44
To: Matti Zemack
Cc: users@lists.opensips.org
Subject: Re: [OpenSIPS-Users] Good intro to mediaproxy setup?

You seem to be mixing different versions of the dispatcher and the  
relay. Stick with the latest for both


_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users