Hi, Sorry but it's pretty difficult to know the right word for it since we work/validate with many IP PBX (hard/soft) and names changes parking room/orbit/slot/extension...
From the sipXecs web interface in Features > Call Park, it's called "Park Extension" These ones are working perfectly, you can transfer (REFER) a call to it and pick up the call by using *4X (where X is the extension number). The presence (RFC4235) is also perfectly working, you know the status of the extension and the caller ID. (I wish you could configure it so when you call a busy parking extension you actually pick up the call in it and free the extension, but that's another story :) Now regarding the conferences extensions in Features > Conferencing > Conference, they refuse call transfer (REFER) and presence subscription with the same error message: SIP/2.0 482 Loop Detected with 2 hops ago, but they do work when you call them. Regards. Tony Graziano wrote: > Wait... > > Help me understand this, because its something I was asking in the FS > list yesterday and today... > > If I use valet parking which uses mod_fifo, I can get BLF to monitor > the fifo. Which might be ultimate goodness... > > So in the interest of NOT hijacking this thread... can you explain > what you mean by "parking room". Is this a conference room or parking > slot? It would be nice to clarify, because it could start confusing me > and a few others. > > Thanks, > > Tony > > On Thu, Sep 2, 2010 at 2:49 PM, Worley, Dale R (Dale) <[email protected]> > wrote: > >> ________________________________________ >> From: [email protected] >> [[email protected]] On Behalf Of Jean-Hugues Royer >> [[email protected]] >> >> Using sipXecs 4.2.1 you can subscribe to parking rooms for RFC4235 and >> you get perfect status notifications. >> >> But if you subscribe to conference rooms for RFC4235 you get this >> unusual error: SIP/2.0 482 Loop Detected with 2 hops ago >> >> Do conference rooms support RFC4235 subscriptions ? >> >> Here are the full packets subcription / reply: >> _______________________________________________ >> >> We will need a snapshot to diagnose that. >> >> Dale >> _______________________________________________ >> sipx-dev mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-dev/ >> _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
