>>> "Burden, Mike" <[email protected]> 12/14/10 9:29 AM >>> v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} <![endif]--> <o:shapedefaults v:ext="edit" spidmax="1026" /> <![endif]--> <o:shapelayout v:ext="edit"> <o:idmap v:ext="edit" data="1" /> </o:shapelayout><![endif]-->>>>When I run a siptrace of an inbound call, I see that before an INVITE is sent to any of our phones, the following >>>sequence is repeated 11 times:<o:p></o:p> <o:p> </o:p> Its normal. The call is redirect only after the proxy knows where to find the end point. All calls to the proxy look like a transfer and get bounced around several times.
The only time this becomes an issue is when the INVITE has a maximum number of hops defined. Alias and "fake users" for DID's can add up quickly to the maximum call hops. You can reduce some of these hops by using call forwarding on "fake DID" by using the full e...@sipdomain in the destination field. -M </[email protected]>
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
