This is the mail system at host posta.websolutions.it.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to <postmaster>

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

                   The mail system

<o...@smtpcleaner.websolutions.it> (expanded from 
<jfrkrvfax...@spammotel.com>): mail
    for smtpcleaner.websolutions.it loops back to myself
Reporting-MTA: dns; posta.websolutions.it
X-Postfix-Queue-ID: 7C90D14901C1
X-Postfix-Sender: rfc822; re.AC6KTKXW62X41@spammotel.com
Arrival-Date: Fri, 11 Sep 2009 03:03:52 +0200 (CEST)

Final-Recipient: rfc822; Ok@smtpcleaner.websolutions.it
Original-Recipient: rfc822;JFRKRVFAXDHB@spammotel.com
Action: failed
Status: 5.4.6
Diagnostic-Code: X-Postfix; mail for smtpcleaner.websolutions.it loops back to
    myself
--- Begin Message ---

Send Users mailing list submissions to
        users@lists.opensips.org

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.opensips.org/cgi-bin/mailman/listinfo/users
or, via email, send a message with subject or body 'help' to
        users-requ...@lists.opensips.org

You can reach the person managing the list at
        users-ow...@lists.opensips.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Users digest..."


Today's Topics:

   1. Re: Dynamic Routing - routing using source        IPaddress
      (Julien Chavanton)
   2. Re: mediaproxy relay on none default route        interface failed
      (Dan Pascu)
   3. Re: mediaproxy relay on none default route        interface failed
      (Ra?l Alexis Betancor Santana)
   4.  Voicemail doesn't work with Mediaproxy (osiris123d)
   5. Re: Voicemail doesn't work with Mediaproxy (Thomas Gelf)
   6. Re: Expire call with redirecthostport() (Thiago Rondon)
   7. Re: mediaproxy relay on none default route        interface failed
      (I?aki Baz Castillo)


----------------------------------------------------------------------

Message: 1
Date: Thu, 10 Sep 2009 18:15:24 +0100
From: "Julien Chavanton" <j...@atlastelecom.com>
Subject: Re: [OpenSIPS-Users] Dynamic Routing - routing using source
        IPaddress
To: "OpenSIPS users mailling list" <users@lists.opensips.org>,
        "OpenSIPS users mailling list" <users@lists.opensips.org>
Message-ID:
        <3a55bd693d48034787fa018dfa2403ee42a...@d3bmvc3j.atlas.private>
Content-Type: text/plain; charset="iso-8859-1"

Thank you, I will look further after using group, I am also facig some 
requirements to append prefix, when a call comes in from a defined Gateway.
Here is a recap, of what I understand after reading testing Dynamic Routing :
 
When a call is comming from a given Gateway we can not use Dynamic Routing to 
append/strip prefixes, DR module only work on destination Gateway.
 
Therefore I selected to use Dial Plan for append/strip prefix on inbound calls.
 
 
Outbound number manipulation prefix append/strip : module (Dynamic Routing) 
--------------------------------------------------------------------------------
"STRIP" : striped from the RURI when the call is going to the target gateway
"PRI Prefix" : assigned to the RURI when the call is going to the target gateway
 
 
Inbound number manipulation prefix append/strip : module (Dial Plan) 
----------------------------------------------------------------------
Prefix : a lookup in the dialplan table for the source IP address will return a 
prefix to append if any
 
Example:
 # find if there is a prefix for traffic from the IP address
 dp_translate("0", "$src_ip/$avp(s:prefix)");
 if($avp(s:prefix) && method=="INVITE" && !has_totag()){
  xlog("prefix for IP[$src_ip]=[$avp(s:prefix)]\n");
  $rU  =  $avp(s:prefix) + $rU ;
 }
 else{
  xlog("no prefix for IP[$src_ip]\n");
 }

 

________________________________

From: users-boun...@lists.opensips.org on behalf of Brett Nemeroff
Sent: Thu 10/09/2009 4:18 PM
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Dynamic Routing - routing using source IPaddress


Usually you set the group based on something else. I use memcache for this.. so 
I toss the IP against memcache, which returns a group id, then I use that in 
the do_routing() cmd.  

Of course, this requires pre-populating the cache src_ip => group_id

The newly released startup_route can do that for you now. :D

-Brett


On Thu, Sep 10, 2009 at 8:00 AM, Julien Chavanton <j...@atlastelecom.com> wrote:


        With Dynamic Routing, how can we route based on source IP 
address/Gateway ?

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


-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://lists.opensips.org/pipermail/users/attachments/20090910/6763d8f8/attachment-0001.htm
 

------------------------------

Message: 2
Date: Fri, 11 Sep 2009 00:25:39 +0300
From: Dan Pascu <d...@ag-projects.com>
Subject: Re: [OpenSIPS-Users] mediaproxy relay on none default route
        interface failed
To: OpenSIPS users mailling list <users@lists.opensips.org>
Message-ID: <a7660503-d82e-40f2-b238-9b855abb9...@ag-projects.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes

On 10 Sep 2009, at 18:00, Ra?l Alexis Betancor Santana wrote:

> So ... "killing flies with bazookas" ...
> So ... when having to update, need to update n instances, instead of  
> only
> one ..
> So ... wasting hard disk (I know it's cheap ... but wasting  
> anyway) ...

I'm pretty sure you felt smart and clever while wording your indignant  
reply. Indeed, you absolutely had to put me into my rightful place and  
I deserved every dot and comma in it. What was in my mind trying to  
suggest some alternatives that work with the software as it is and do  
not require patching or a new version? But for a strange reason I  
cannot pinpoint, I do not feel motivated by your rhetoric. No sir.  
Shamefully I must admit that it made me think that I can spend my time  
better elsewhere. Imagine that good sir. I'm so ashamed. It also made  
me have unclean thoughts about you. It made me think that maybe you  
have a size problem and you're compensating. Can you imagine that? So,  
good sir, maybe you should fire more of your aggressive indignation  
towards me to break this unclean thinking in my mind and finally make  
me see the light. Forget about asking nicely or, God forbid,  
contributing back. That's for pussies and it only weakens one's  
character.

> I still think that a simple param like -c configfile is better.

That may be, but I made a principle of not helping people that hate me  
or abuse me verbally. Besides, free in "free software" doesn't stand  
for let's use that software that is free of charge and then feel free  
to abuse the developer. It stands for fell free to improve it and  
contribute back. Wait, scratch that. From you I wouldn't even want  
patches. The contribution you made is already more than enough...

--
Dan






------------------------------

Message: 3
Date: Thu, 10 Sep 2009 22:41:25 +0100
From: Ra?l Alexis Betancor Santana      <r...@dimension-virtual.com>
Subject: Re: [OpenSIPS-Users] mediaproxy relay on none default route
        interface failed
To: OpenSIPS users mailling list <users@lists.opensips.org>
Message-ID: <200909102241.26301.r...@dimension-virtual.com>
Content-Type: text/plain;  charset="iso-8859-1"

On Thursday 10 September 2009 22:25:39 Dan Pascu wrote:
> On 10 Sep 2009, at 18:00, Ra?l Alexis Betancor Santana wrote:
> > So ... "killing flies with bazookas" ...
> > So ... when having to update, need to update n instances, instead of
> > only
> > one ..
> > So ... wasting hard disk (I know it's cheap ... but wasting
> > anyway) ...
>
> I'm pretty sure you felt smart and clever while wording your indignant
> reply. Indeed, you absolutely had to put me into my rightful place and
> I deserved every dot and comma in it. What was in my mind trying to
> suggest some alternatives that work with the software as it is and do
> not require patching or a new version? But for a strange reason I
> cannot pinpoint, I do not feel motivated by your rhetoric. No sir.
> Shamefully I must admit that it made me think that I can spend my time
> better elsewhere. Imagine that good sir. I'm so ashamed. It also made
> me have unclean thoughts about you. It made me think that maybe you
> have a size problem and you're compensating. Can you imagine that? So,
> good sir, maybe you should fire more of your aggressive indignation
> towards me to break this unclean thinking in my mind and finally make
> me see the light. Forget about asking nicely or, God forbid,
> contributing back. That's for pussies and it only weakens one's
> character.

Every time we have "talked" about this ... you always react the same ... as If 
I was fighting against you ... I don't know from where you get that feeling 
from my words.

I'm only expressing my opinion, your are free to ignore it if you don't like 
it.

Yes you gave a solucion and I arge that a better solucion (and from a desing 
point of view and from the KISS principles, easier) it's so simple add a -c 
config param.
Do you want the patch? ... they are just 4 lines, I did it for 2.3.4 version 
of mediaproxy, also for callcontrol and other very good software you have 
developed but that lacks THAT SIMPLE option, to be able to set the config 
file to use from the command line ... as 99% of other software allow you.

> > I still think that a simple param like -c configfile is better.
>
> That may be, but I made a principle of not helping people that hate me
> or abuse me verbally. 

I don't think I have abused you ... if you think soo it's your problem. I only 
express my opinion and comment other possible solutions.

> Besides, free in "free software" doesn't stand 
> for let's use that software that is free of charge and then feel free
> to abuse the developer. It stands for fell free to improve it and
> contribute back. Wait, scratch that. From you I wouldn't even want
> patches. The contribution you made is already more than enough...

Dan, sincerily .. you don't like to hear opinions that are agains yours ... 
and that's not good.
If you don't want my patches, you are free to ignore them. Not always a patch 
is needed to improve a software or to contribute to it, most of time another 
point of view about a problem it's enought.

-- 
Ra?l Alexis Betancor Santana
Dimensi?n Virtual



------------------------------

Message: 4
Date: Thu, 10 Sep 2009 16:54:46 -0500 (CDT)
From: osiris123d <duane.lar...@gmail.com>
Subject: [OpenSIPS-Users]  Voicemail doesn't work with Mediaproxy
To: users@lists.opensips.org
Message-ID: <1252619686859-3618910.p...@n2.nabble.com>
Content-Type: text/plain; charset=us-ascii


I have been trying to fix this for the last 4 days.  I have searched the
mailing list with the following keywords (mediaproxy rewritehostport one-way
audio, etc) and I find some posts that explain that my "200 ok" messages
need say that the "connection information" needs to point to my mediaproxy. 
I am trying to use fix_nated_sdp("3", "ip of mediaproxy"0), but I am sure I
am placing it and using it in the wrong spot in my script.

So here is the problem


When a user calls someone and they are busy or not there the caller will be
directed to voicemail by using the rewritehostport("ip of voicemail")
command.  The caller is nated behind a router.  The caller doesn't hear the
voicemail voice prompts, but the caller IS able to leave a voicemail and be
heard.  So there is one-way audio going on where the caller can't hear, but
voicemail can.  When I do a sniff I see that this is because the caller's
RTP is going directly to the Voicemail Servers Public IP address and the
Voicemails RTP is going to the Mediaproxy.
Here is the code in question
failure_route[1] {
        ##--
        ##-- If cancelled, exit. 
        ##--
        if (t_was_cancelled()) {
                exit;
        };
        ##--
        ##-- If busy send to the e-mail server, prefix the "b"
        ##-- character to indicate busy. 
        ##--
        if (t_check_status("486")) {
                revert_uri();

                append_hf("P-App-Name: voicemail\r\nP-App-Param:
Email-Address=blah.blahmail.com;Mode=both;usr=$tU;d...@$td\r\n");

                rewritehostport("VoicemailIP");
                append_branch();
                route(1);
                exit;
        };
        ##--
        ##-- If timeout (408) or unavailable temporarily (480),
        ##-- prefix the uri with the "u"character to indicate 
        ##-- unanswered and send to the e-mail
        ##-- sever
        ##--
        if (t_check_status("408") || t_check_status("480")) {
                revert_uri();

                append_hf("P-App-Name: voicemail\r\nP-App-Param:
Email-Address=blah.blahmail.com;Mode=both;usr=$tU;d...@$td\r\n");

                rewritehostport("VoicemailIP");
                append_branch();
                route(1);
                exit;
        };
}

onreply_route[1] {
        #
        #-- On-replay block routing --
        #
        if ((isbflagset(6) || isbflagset(7)) &&
(status=~"(180)|(183)|2[0-9][0-9]")) {
                xlog("L_INFO", "----- Inside OnReply Route 1 with bflag
being 6 or 7 and a bunch other stuff");
                if (search("^Content-Type:[ ]*application/sdp")) {
                        xlog("L_INFO", "----- Inside OnReply Route 1 with
content type equaling sdp");
                        append_hf("P-hint: onreply_route|usemediaproxy
\r\n");
                        use_media_proxy();
 
               };
        };

        if (client_nat_test("1")) {
                xlog("L_INFO", "----- Inside OnReply Route 1 and client nat
equaled 1");
                append_hf("P-hint: Onreply-route - fixcontact \r\n");
                fix_contact();
        };

        exit;
}


So how do I solve this issue?


-- 
View this message in context: 
http://n2.nabble.com/Voicemail-doesn-t-work-with-Mediaproxy-tp3618910p3618910.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.



------------------------------

Message: 5
Date: Fri, 11 Sep 2009 00:35:26 +0200
From: Thomas Gelf <tho...@gelf.net>
Subject: Re: [OpenSIPS-Users] Voicemail doesn't work with Mediaproxy
To: users@lists.opensips.org
Message-ID: <h8buvd$cv...@ger.gmane.org>
Content-Type: text/plain; charset=ISO-8859-15

osiris123d wrote:
> I am trying to use fix_nated_sdp("3", "ip of mediaproxy"0), but I am sure I
> am placing it and using it in the wrong spot in my script.

Don't do that. If you are using fix_nated_sdp together with mediaproxy,
you will for sure mess up something. Calling "use_media_proxy" in your
INVITE route, your reply route and also for your in-dialog ReINVITES
will automagically fix your SDP.

> failure_route[1] {
>   ...
>   append_branch();

What OpenSIPS version are you using? In recent versions append_branch
is not needed here.

Best regards,
Thomas Gelf

-- 
 mail: tho...@gelf.net
  web: http://thomas.gelf.net/




------------------------------

Message: 6
Date: Thu, 10 Sep 2009 19:48:48 -0300
From: Thiago Rondon <thi...@aware.com.br>
Subject: Re: [OpenSIPS-Users] Expire call with redirecthostport()
To: OpenSIPS users mailling list <users@lists.opensips.org>
Message-ID: <4aa98250.4080...@aware.com.br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed



I want to control the maximum duration of the entire call.

Thanks!
-Thiago Rondon

Bogdan-Andrei Iancu escreveu:
> Hi Thiago,
>
> by this expire_call_in_seconds(300); you want to control the maximum 
> duration of the entire call ? or only the setup time of the call ?
>
> Regards,
> Bogdan
>
> Thiago Rondon wrote:
>   
>> Hi,
>>
>> Today I use redirecthostport() to forward calls for another provider, 
>> can I make a static limit for all calls that I send to ?
>>
>> Like:
>>
>>        expire_call_in_seconds(300); # ????
>>        redirecthostport( "host:5060");
>>
>> Thanks!
>> -Thiago Rondon
>>
>> _______________________________________________
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>   
>>     
>
>
> _______________________________________________
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>   




------------------------------

Message: 7
Date: Fri, 11 Sep 2009 01:09:21 +0200
From: I?aki Baz Castillo <i...@aliax.net>
Subject: Re: [OpenSIPS-Users] mediaproxy relay on none default route
        interface failed
To: users@lists.opensips.org
Message-ID: <200909110109.21866....@aliax.net>
Content-Type: Text/Plain;  charset="iso-8859-1"

El Jueves, 10 de Septiembre de 2009, Dan Pascu escribi?:
> > That's not true, you could run as many Realys as you want on the  
> > same server,
> > only have to patch mediaproxy-relay to be able to call it with a
> > diferent .cfg as the default one, have diferent listen ports and no  
> > more.
> 
> You don't need to patch anything. Just unpack mediaproxy in as many  
> different directories as you need, run ./build_inplace and modify each  
> config.ini in those directories as needed. Then run mediaproxy from  
> those directories and each of them will use the local config.ini from  
> its own directory.

Is this really preferable to a single and so common "-c CONFIG_FILE" 
commandline option?

A "-c" option would break nothing since the absence of it means "default 
config file". Also a "-c" option allows deb usual installation and upgrade 
(the only requeriment would be create N init scripts having each one a 
different "-c" config file and PID file).

Perhaps you suggest the above solution as a feasible workaround without 
patching the code. I expect it because I cannot imagine how managing N full 
installations of N mediaproxies can be better than a simple "-c" option 
involving a single installation of the software.

Of course this is just my opinion. Take is as a suggestion and not as a 
demand.

Regards.

-- 
I?aki Baz Castillo <i...@aliax.net>



------------------------------

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


End of Users Digest, Vol 14, Issue 34
*************************************


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

Reply via email to