Again,
Below is the output of /var/log/messages:
Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528)
Regards,
Ronald
________________________________
Van: serusers-bounces@iptel.org [mailto:serusers-bounces@lists.iptel.org] Namens Ronald Voermans Verzonden: maandag 26 september 2005 8:41 Aan: serusers@lists.iptel.org Onderwerp: [Serusers] Problem/Question regarding mediaproxy
Hello,
I'm using Ser in combination with Mediaproxy. The situation is as follow: My SER has a private ip address (10.254.254.1), and my UAs also have private IP addresses, they can all see SER, and SER can see the UAs. Next, our company has a Voice Interconnect with a telco. (it's using Cirpack as softswitch). SER can see Cirpack and vice versa. However, the UAs cannot see the Cirpack. So I want to use Mediaproxy to overcome this. I can make outbound calls, but when calling inbound, I sometimes have one-way-voice of no voice at all. I think the problem is related to Cirpack, but I have a question thouh:
- When calling mediaproxy, how does mediaproxy decide which one is the caller and which one is the called? Is this based on the From and To header? Because, if i call from PSTN -> SIP, i get serveral thousands (!) of messages saying that the called person signed in (no caller signs in in mediaproxy). This could be due to the fact that the from and to headers are incorrect.
My ser.cfg is the one from onsip.org (pstn with nat). I can post configs/traces if someone needs them!
Regards, Ronald
Yes, as you can see, both 192.168.0.146 and 10.166.38.109 are referred to as "called". When use_media_proxy() is called, the IP found in c= in the SDP payload of the INVITE and the OK will be modified to be mediaproxy's address. If mediaproxy is reachable from local address to your UAs and on a public address to the GW, you have a problem (either INVITE or OK will show the wrong address). You need mediaproxy on a public address. Thus, both caller and called should be identified by a public address in your mediaproxy logs. g-) ----- Original Message ----- From: "Ronald Voermans" r.voermans@global-e.nl To: serusers@lists.iptel.org Sent: Monday, September 26, 2005 12:20 PM Subject: RE: [Serusers] Problem/Question regarding mediaproxy
Again,
Below is the output of /var/log/messages:
Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 192.168.0.146:5004 (RTP) (will return to 192.168.0.146:5004) Sep 26 12:17:57 ser mediaproxy[2876]: session 00-00147-52dbda11-7c108ad21@tpsip01.ipvoice.enertel.nl: called signed in from 10.166.38.109:37528 (RTP) (will return to 10.166.38.109:37528)
Regards,
Ronald
Van: serusers-bounces@iptel.org [mailto:serusers-bounces@lists.iptel.org] Namens Ronald Voermans Verzonden: maandag 26 september 2005 8:41 Aan: serusers@lists.iptel.org Onderwerp: [Serusers] Problem/Question regarding mediaproxy
Hello,
I'm using Ser in combination with Mediaproxy. The situation is as follow: My SER has a private ip address (10.254.254.1), and my UAs also have private IP addresses, they can all see SER, and SER can see the UAs. Next, our company has a Voice Interconnect with a telco. (it's using Cirpack as softswitch). SER can see Cirpack and vice versa. However, the UAs cannot see the Cirpack. So I want to use Mediaproxy to overcome this. I can make outbound calls, but when calling inbound, I sometimes have one-way-voice of no voice at all. I think the problem is related to Cirpack, but I have a question thouh:
- When calling mediaproxy, how does mediaproxy decide which one is the
caller and which one is the called? Is this based on the From and To header? Because, if i call from PSTN -> SIP, i get serveral thousands (!) of messages saying that the called person signed in (no caller signs in in mediaproxy). This could be due to the fact that the from and to headers are incorrect.
My ser.cfg is the one from onsip.org (pstn with nat). I can post configs/traces if someone needs them!
Regards, Ronald
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-
Greger V. Teigre -
Ronald Voermans