Hi İ think he may be asking for the number of maximum routes ( proxies ) in a scenario .
Max forwards header has such type of usage on SIP. MAximum is 70 proxies. See explanation in RFC3261 8.1.1.6 Max-Forwards The Max-Forwards header field serves to limit the number of hops a request can transit on the way to its destination. It consists of an integer that is decremented by one at each hop. If the Max-Forwards value reaches 0 before the request reaches its destination, it will be rejected with a 483(Too Many Hops) error response. A UAC MUST insert a Max-Forwards header field into each request it originates with a value that SHOULD be 70. This number was chosen to be sufficiently large to guarantee that a request would not be dropped in any SIP network when there were no loops, but not so large as to consume proxy resources when a loop does occur. Lower values should be used with caution and only in networks where topologies are known by the UA. Cheers. 2012/2/12 Paul Kyzivat <[email protected]> > On 2/12/12 11:54 AM, radhakrishnan jayachandran wrote: > > How many number of routes can I have at maximum in the INVITE? > > Suppose, If I have an Application Server (chains of application server > and > > all B2BUAs) connected to the S-CSCF, and the INVITE request goes through > a > > complex routing mechanism, how much routes can I traverse? (to optimise > the > > overall usage of Application Sequencing). > > Can I have infinite number of routes or Does the standard restricts us to > > limit to a maximum of "n" number of routes? > > SIP has no limits of this sort. > > Perhaps IMS has some, but you will have to check the IMS specs for that. > > (I'm not certain what you have in mind regarding multiple routes and > complex routing. What comes to my mind is sip-level forking of requests, > or else DNS-level alternative addresses. Or are you concerned with > *long* routes, due to visits from the S-CSCF to many application > servers? But it doesn't really matter - the answer is the same.) > > Thanks, > Paul > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
