Hi,
Sorry Tony, but that's not the point, I was reporting a packet
mis-ordering of sipXecs (subject of the message), I just gave a
subscribe/notify scenario as an example.
In that scenario (which could be any other kind of communication between
two phones through sipXecs), sipXecs did mis/re-order the packets.
And regarding the scenario example, if I want to subscribe to RFC3245
directly to phones through sipXecs (and not use the RLS) it's totally legit.
Regards.
Tony Graziano wrote:
I think this might help.
http://wiki.sipfoundry.org/display/xecsuserV4r2/Manually+Configuring+Phone+BLF
Essentially, when monitoring a phone via sipx, the phone must support
dialog events (RFC4235 <http://www.apps.ietf.org/rfc/rfc4235.html>).
The subscribe format is RFC4662
<http://www.apps.ietf.org/rfc/rfc4662.html> (Broadworks style). So
when you say you are trying to monitor the phone, I just assumed you
would use the PresenceServer in sipx, If your UA has a peer-to-peer
function it assumes a lot that all of the other phones in "any"
environment are capable of acknowledging a peer-to-peer request. This
is why the function was centralized in sipx, and it seems to work well.
Does your UA support using a presence server?
On Sun, Sep 12, 2010 at 6:18 PM, Tony Graziano
<[email protected] <mailto:[email protected]>>
wrote:
Well, I don't know what the user agent is, but the "mode" if it is
set as peer-to-peer should not contact the proxy. The only example
I can think if is with x-lite, it does presence via peer-to-peer,
but with bria you subscribe to presence via presence server.
It might really be a config question assuming the UA is capable of
peer-to-peer and is set properly to use it.
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
