SIP Trunk & DoorPhone Controller

[aroldan]

Hello all,
I appreciate any input provided.
Has anyone used a SIP Trunk for a door-phone controller? If so, how difficult is it to setup? Is it not recommended? Does it even work well? What FXO Gateway(s) would be recommended?
The Door Phone is a Viking W-3000, and with a Viking C-1000B Controller. The Controller is only accessible via the network (no copper in-between the IPO and the controller). The connections should be as follows:
IPO SIP Trunk->FXO Gateway across the LAN network->FXO port physical connection to the Door-Phone Controller->Door-phone Controller physical connection to the Door-Phone
Going off-hook with the Door-phone would ring the SIP Trunk port routing to a HGroup of Users

 

[amriddle01]

You would typically use a SIP endpoint for this, if it's not a SIP door phone then use an ATA and have the door phone dial the group or use a ?D shortcode

 

[aroldan]

Yeah, unfortunately the reason I was asking about this way of setup is because going through the docs, it says that using an analog station port will not work with this particular door-phone unless of course I bypass the controller, but I'm coming in the middle of this and the door-phone & controller are already in place and can't bypass the controller due to the requirement of DTMF signaling. If it hasn't been tried, I don't wanna be the first, I'll just keep digging for alternatives or try to persuade getting a different door-phone.
I did speak with Viking and they only said "in theory it should work.

 

[derfloh]

I had it with one customer who had a Siedle door phone controller. It was kind of a complete phone system that was connected to IPO through a SIP trunk.

 

[amriddle01]

Don't they have any analogue trunk ports available? And then just run a cable/patch the connection direct to the IPO, even the cost of the card will be worth the simplification and less maintenance than an extra 2 devices in the already odd setup

It is possible using a trunk on the IPO, it's flexible like that, we have posted examples of linking other system etc this way. It's more the Viking that will break it

 

[aroldan]

Thanks guys. Tried doing a quick search on the Siedle but only saw door-phones and really want to avoid changing out their complete door-phone/controller setup if at all possible. As far as the analog trunk ports, they do have them available but the controller is in a separate building with fiber only and would take a miracle for them to agree on sending a patch all they way over. --Thanks for the tip amriddle about the Viking breaking the operation. That's exactly why I don't like being the first to try a solution like this, not to mention not having any control over the network
*On another note I misspoke about being able to bypass the controller. With the current door-phone the controller is def required

 

[amriddle01]

I'm not saying it will, I'm saying if it doesn't work it's likely that

 

[aroldan]

ah got it

 

[aroldan]

Update.
Finally got this tested and ended up using a 3rd Party Endpoint license with a Cisco SPA112 plus getting an analog door-phone E-30 required to work with the Controller. User Short Codes (?D) weren't working with the SIP User when going off-hook so ended up configuring the auto-dial within the SPA112 with the "Hotline" syntax:
(P0<:xxx>)
the x's represent extension number...
in the Dial Plan field.
Had to also configure an AA for disconnecting the door-phone after 4 or so rings because the door-phone would try to call back after being disconnected. I had documented this config procedure here: thread940-1745630
Works great!