Hi, This results in BLF's being broken in some cases. Also, at one client of ours this seems to result in the sipXproxy running out of resources because they have loads of call forwardings.
In my opinion a SUBSCRIBE is only ment for the endpoint you are subscribing to and should not be forwarded, hence my question :) Kind regards, Met vriendelijke groet, Elwin Formsma Telecats BV ----- Elwin Formsma | Telecats bv | KvK Enschede 06069106 | Tel: 053 488 99 44 | Fax: 053 488 99 10 | E-mail: [email protected]<mailto:[email protected]> | Op 31 okt. 2012, om 18:33 heeft Melcon Moraes <[email protected]<mailto:[email protected]>> het volgende geschreven: Hmm, that's what I saw when trying to figure why Yealink sets do not work well with BLF when user has callforward. When registrar returns all contacts for the user, the SUBSCRIBE gets forked to all of them, and which one replies firts "wins". What were you doing to get this, Met? - MM On Wed, Oct 31, 2012 at 12:46 PM, Elwin Formsma <[email protected]<mailto:[email protected]>> wrote: Hello, Just a quick question. Is there any specific reason why a SUBSCRIBE would follow SipXecs call forwardings? See attached screenshot. Kind regards, Met vriendelijke groet, Elwin Formsma Telecats BV ----- Elwin Formsma | Telecats bv | KvK Enschede 06069106 | Tel: 053 488 99 44 | Fax: 053 488 99 10 | E-mail: [email protected]<mailto:[email protected]> | <Schermafbeelding 2012-10-31 om 15.44.07.png> _______________________________________________ sipx-users mailing list [email protected]<mailto:[email protected]> List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list [email protected]<mailto:[email protected]> List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
