Jag98

Hello, Could you provide this configuration? I'm having trouble setting up SPA3102 with pbxnsip Thanks

Hi Matt, I also tried changing the {Port_0/0_Destination} to the trunk account numbers on pbxnsip and this didn't work either. I've got a linksys SPA 3102 which i could use for the third line instead of the patton which would eliminate the need for this config. Unfortunately I understand the new firmware on the linksys won't work too well with pbxnsip. Jag

Hi Matt, Thanksvery much for the above. I tried it out - changing the {Port_0/0_Destination} strings to the hunt group 200 and 300 for {Port_0/2_Destination} but had no luck. When I dial into port 0/2 which is a different number it rings only the hunt group 200. I'm using the following trunk configs on the PBXnSIP: Trunk 1 (for first two lines) account: 1000 pw: 1000 Proxy Address: 172.16.0.4:5060 Trunk 2 (for 3rd line) account: 1002 pw: 1002 Proxy Address: 172.16.0.4:5060 I think I may be doing something wrong here. Thanks Jag

Hi Matt, I'm probably being a bit thick but how do i do that exactly? I've tried changing the line table to authenticate to the extension instead but I've had no joy. Thanks again. Jag

Thanks for posting this Matt. It's very useful. I've been trying without luck to configure my 4114 to have two lines ring one group of extensions and another single line to ring a separate extension but cannot seem to figure out how to do this. I've tried playing with the ports on both the patton and the trunk setup on pbxnsip but it just doesn't seem to work. Can you offer any advice on how I might be able to do this? Thanks Jag

I agree with Matt here. Since 3CX offer auto provisioning of at least the popular gateways it makes sense for pbxnsip to do the same. I recently purchased a Patton 4114 from recommendations by other users on this forum which seems to be one of the best. However the configuration was not straight forward (as is it with 3CX) and all the features of the Patton do not seem to be available as they are with 3CX. I think at least a best practice "template config file" wouldn't hurt combined with a pbxnsip template to set up the trunks. Administrators could then focus on the excellent features of pbxnsip rather than trawling the forums for answers to basic setup queries. By the way, pbxnsip is far superior to 3cx in my opinion and a making it easier to set up can only lead to good things. Jag