Hi Mauro,

afaik local_route is meant to be used only with OpenSIPS self generated requests (like CANCEL to forking branches) not with WeSIP. That is the reason why we implemented the SPIRAL_HDR feature. When you activate SPIRAL_HDR the messages generated by WeSIP will "enter" again in OpenSIPS thus you can catch them in the route function (not local_route). In order to identify them look for the X-WeSIP-SPIRAL header and then modify the message and relay it with t_realy. Code would look something like this

route{

    if(is_present_hf("X-WeSIP-SPIRAL")){
       /* modify your message here as required */
       t_relay();
    }else{
       as_relay_t("app_server_one");
    }
}       

Regards

Ginés

Hola Gines,

I’m in a test environment and the domain that I use for every user is resolved with the production SIP server IP…(I haven’t a DNS domain name associated to my test openser), obviously the production SIP server responde to every request with a 403 Forbidden message.

I don’t know if this is the problem but with the wesip SPITAL_HDR set to true, I see only the messages that start in the local_route function.

To avoid this problem, I’m trying to manipulate the message in the local_route function without good result L…

Is there another way to do this??

Regards
     MD

Da: Ginés Gómez [mailto:[email protected]]
Inviato: venerdì 20 marzo 2009 12:46
A: Mauro Davi’
Cc: [email protected]
Oggetto: Re: [OpenSIPS-Users] Wesip and Opensips

Ciao Mauro,

first, you can manipulate messages from WeSIP itselft before you send them out. Once they are sent out you can manipulate them in OpenSIPs script if you configure WeSIP to work in spiral mode. When working in spiral mode outgoing messages from WeSIP loop through OpenSIPs script in a new transaction before leaving. You can recognize them, and work accordingly if you look for the particular a header that is added by WeSIP. The header is X-WeSIP-SPIRAL

NON-SPIRAL-MODE (Default)

Origin       [OpenSIPS     WeSIP]      Destination
   | ----t1----->| ----------->|------t2----->
                                   Internal
                               Delivery


SPIRAL-MODE

Origin   [OpenSIPS       WeSIP]                OpenSIPS   Destination
     | ----t1-----> | ----------->|-----------t2------->| ----t3---> |
                                       Internal       X-WeSIP-Spiral
                                   Delivery

More on this kind of configuration at 
http://www.wesip.com/mediawiki/index.php/Configuration#com.voztele.javax.sip.SPIRAL_HDR

Hope that helps

Regards

Ginés




Hi All,

I’m setting up the Click2Dial wesip application, and I’m trying to use it.

When I start the call in the opensips script I need to manipulate it.

So in the local_route branch I try to see if the To party is an alias but I can’t use alias_db_lookup function in the local_route branch…

Is this correct? How I can manipulate the messages generated by wesip ?

Thanks in advance
            MD
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to