Hi Pranav,

Thanks for quick reply.
I have some more questions now.
It means that in case of Mirror Proxy mode , Endpoint information is not kept 
at the node.
Second Question: what is the advantage for OBP mode? Can OBP’s URI and realm 
address be different?
Third question : how Endpoint gets advantage in OBP mode?

Regards
Poonam

From: Pranav Damele [mailto:[email protected]]
Sent: Tuesday, July 15, 2014 4:17 PM
To: Poonam2 Gupta
Cc: [email protected]
Subject: Re: [Sip-implementors] hi

Hi Poonam,

OBP or Out-Bound Proxy or Access mode In OBP mode, endpoints are registered 
with, and authenticated by, an external registrar server although your node 
keeps all the information of registered endpoint.
The SIP registrar server to which S3 will forward REGISTER messages must be 
provisioned as an endpoint on your node, including specifying its SIP URI 
parameter.You will send these packets to your node's realm's address but with 
the out-bound proxy's URI.

Normally, in order to use out-bound proxy (OBP) functionality, an endpoint must 
have built-in OBP support. For endpoints that do not support OBP intrinsically, 
mirror proxy feature comes handy.
Mirror Proxy is when node acts as a proxy for the proxy registrar server.

And in non-OBP mode or inter-connect mode your define static endpoints. You 
also define call routes and plans.

I guess these features are implemented in a session border controller.

Regards,
Pranav Damele

Associate Consultant - Engineering, Product Engineering and Development
Mobile: +91-9818-92-4466
Email: [email protected]<mailto:[email protected]>
IM: pranavdamele (Skype)
[http://www.linkedin.com/img/signature/icon_in_blue_14x14.gif] 
http://in.linkedin.com/in/pranavdamele

On 15 July 2014 16:02, Poonam2 Gupta 
<[email protected]<mailto:[email protected]>> wrote:
Hi,

Need to know about OBP mode, non-OBP mode and Mirror Proxy mode in SIP.
Basically I wanted to know what all different headers are changed in each kind 
of proxy?

Regards
Poonam


"DISCLAIMER: This message is proprietary to Aricent and is intended solely for 
the use of the individual to whom it is addressed. It may contain privileged or 
confidential information and should not be circulated or used for any purpose 
other than for what it is intended. If you have received this message in error, 
please notify the originator immediately. If you are not the intended 
recipient, you are notified that you are strictly prohibited from using, 
copying, altering, or disclosing the contents of this message. Aricent accepts 
no responsibility for loss or damage arising from the use of the information 
transmitted by this email including damage from virus."
_______________________________________________
Sip-implementors mailing list
[email protected]<mailto:[email protected]>
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors



"DISCLAIMER: This message is proprietary to Aricent and is intended solely for 
the use of the individual to whom it is addressed. It may contain privileged or 
confidential information and should not be circulated or used for any purpose 
other than for what it is intended. If you have received this message in error, 
please notify the originator immediately. If you are not the intended 
recipient, you are notified that you are strictly prohibited from using, 
copying, altering, or disclosing the contents of this message. Aricent accepts 
no responsibility for loss or damage arising from the use of the information 
transmitted by this email including damage from virus."
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Reply via email to