reSIProcate

Mailing Lists

Source Code

Google Search:



< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate-users] Sening a SIP MESSAGE (in the context of a dialog)

They'll be routed back to your ClientPagerMessage, if that is what you mean, but they won't end up back at your InviteSession. 

Best regards,
Byron Campen


Thanks Byron for the response.

I thought of a work around:
Send all SIP MESSAGEs from Server as an out-of-dialog one even though these is an existing dialog, by creating a ClientPagerMessage() in my application. And the responses I will be processing them as in-dialog, because of this code in resip/dum/ DialogSet.cxx: 

       case MESSAGE:
            if (dialog)
           {
               break;
           }
           else if (mClientPagerMessage)
           {
              mClientPagerMessage->dispatch(response);
           }
           return;

hope this will solve my problem....

-Vasanthi



-----Original Message-----
From: Byron Campen [mailto:bcampen@xxxxxxxxxxxx]
Sent: Thursday, April 30, 2009 10:49 AM
To: Vasanthi Ramasamy
Cc: resiprocate-users@xxxxxxxxxxxxxxx
Subject: Re: [reSIProcate-users] Sening a SIP MESSAGE (in the context of a dialog)
Well, you could configure SER to not Record-Route. And, I am betting there is a way to put SER into a dialog-stateless mode, which would also work. I'd go ask the SER folks whether there is some bit of configuration to tweak to get correct behavior. If you absolutely need to hack things together (and are willing to break spec in a pretty egregious way), you could use an outbound decorator to strip the Record-Route headers from the outgoing MESSAGE. (see Profile::setOutboundDecorator()) But, this really should be your last resort, and it should not be viewed as a long-term solution (or really a solution at all). 


Best regards,
Byron Campen



Hi,

I have a situation. Here is the scenario...
1. Remote client establishes a dialog with the server, which is running Resiprocate 1.4 through a proxy (Openser). So INVITE, 180, 200, Ack flow through the proxy. 2. Server has to send a SIP MESSAGE to the remote end in the context of a dialog (by calling message() in InviteSession.cxx). And that gets sent to the proxy, which throws it away with a 481 response.
Now is there a way I can tell Resiprocate server to send SIP MESSAGEs (only) directly to the remote end, instead of proxy. (Request Line in the SIP MESSAGE points to the remote client). 

Thanks,
Vasanthi

_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.238 / Virus Database: 270.12.2/2074 - Release Date: 04/30/09 06:01:00

Attachment: smime.p7s
Description: S/MIME cryptographic signature