In the polycoms (and I presume pretty much any other multi-line phone) you can register external lines that register direct from the handset to a voip provider. SipXecs manages the phone configuration in this case but otherwise doesn't get involved. The normal sipXecs lines continue to work normally.
This wouldn't be seamless but it might be useful in your situation as the talk path would go direct from the branch office to Verizon. I use this sort of setup on the 650's as a backup in case the sipXecs server goes down and I want to dial 911 via a local Patton bridge. Unless verizon supports it you wouldn't get forward on no answer to voice mail, likely that would kill the idea right there. Verizon may also not support multiple registrations on a given DID number so each user would need a separate external phone #. Likely its not appealing at all, just a possible tool in the toolbox. -Eric On Feb 1, 2010, at 4:03 PM, [email protected] wrote: > Thank you. So, it this completely a function of the SBC? If I used an > SBC that supported this feature, should it work from a Sipx point of > view then? > I'm not saying I would go this route, but I just want to see what my > options are. If I'm going to consider putting a device at each facility, > then I would have to also consider switching to a different SBC. > Obviously, that would have been poor planning on my part. I was given a > short time line to get this done at my corporate office because of an > unplanned relocation. Oh well :) > > On 2/1/2010 3:41 PM, Scott Lawrence wrote: >> On Mon, 2010-02-01 at 16:09 -0500, Tony Graziano wrote: >> >>> >>> On Mon, Feb 1, 2010 at 3:49 PM, Scott Lawrence >>> <[email protected]> wrote: >>> On Mon, 2010-02-01 at 14:25 -0600, [email protected] >>> wrote: >>>> Does anyone know if this is even a common feature among SIP >>> servers? >>>> Verizon is indicating they have never worked with a client >>> setup that >>>> didn't support this. Maybe something is getting lost in >>> translation >>>> here. >>> >>> >>> I'm not clear on what you're going to have in the branch. >>> What is the >>> complete sequence of devices and network segments between the >>> phone in a >>> branch and your central sipXecs, and where are the connections >>> to >>> Verizon? >>> >>> >>> >>> He wants sipx in the HQ with the remote branch phones registering to >>> it, using sipXbridge as the gateway for the trunks, but with the media >>> anchored at the handsets in the branches to the Verizon Gateway (not >>> to sipXbridge). >>> >> Right... the feature you're looking for is: >> >> http://track.sipfoundry.org/browse/XX-5034 >> >> it's not expressed the same way, but that's what you would need. If >> implemented, it would allow sipXbridge to get out of the media path. >> >> That issue is not yet scheduled for any specific release. >> >> >> >> > > _______________________________________________ > sipx-users mailing list [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users > sipXecs IP PBX -- http://www.sipfoundry.org/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
