[SIPForum-discussion] Forking mechanism in Proxy server

Karthikeyan Selvaraj karthikeyan.selvaraj at sasken.com
Wed Jul 27 03:51:30 UTC 2011

  The below one is correct. the different between normal proxy and forking proxy is.
   The forking proxy will fork the all sip request to many proxy.
  but forking proxy send one replay (ie.Final conformation) to UAC (who is orginator of sip request).

   UAC send INVITE to forking proxy,
  UAC does't receive any 100,180. UAC directly receive 200 OK from forking proxy. so forking proxy taken care for multiple 100,180 messages. but these information is does't foraward to UAC. When it receive the final response. That message only the forking proxy send to orginator the request.

But normal proxy forward all 100,and 180 message to orginator of the request.

(Note: If any thing wrong kindly reply).

Karthikeyan S

From: discussion-bounces at sipforum.org [mailto:discussion-bounces at sipforum.org] On Behalf Of Gopalakrishnan A.N
Sent: Tuesday, July 26, 2011 9:24 AM
To: Divya Reddy
Cc: discussion at sipforum.org
Subject: Re: [SIPForum-discussion] Forking mechanism in Proxy server

Forking proxies are used to split your sip request to multiple destinations. Logically similar by using fork spoon to eat noodles.

For example if a subscriber has registered to multiple address (for multiple devices) and has a service that facilitates routing of calls to all devices a forking proxy would then take the original request and split into multiple request. These multiple request would then be sent to all of the destination registered for the subscriber.

FYI: The above said example has been taken from the book Session Initiation Protocol, McGraw Hill Communications.
On 25 Jul 2011 23:06, "Divya Reddy" <devyareddy at gmail.com<mailto:devyareddy at gmail.com>> wrote:
> Hi,
> please explain forking mechanism in Proxy server
> regards,
> Devya Reddy

SASKEN BUSINESS DISCLAIMER: This message may contain confidential, proprietary or legally privileged information. In case you are not the original intended Recipient of the message, you must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message and you are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. Nothing contained in this message shall be construed as an offer or acceptance of any offer by Sasken Communication Technologies Limited ("Sasken") unless sent with that express intent and with due authority of Sasken. Sasken has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email.
Read Disclaimer at http://www.sasken.com/extras/mail_disclaimer.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20110727/de19128e/attachment-0002.html>

More information about the discussion mailing list