I don't think I was getting the call info Subscribe from the shared line, but I didn't look very closely. I had to install the phones I was using to test with. I'm going to give it a fresh shot with a Cisco SPA504g.

Thanks for the help so far. It may just be a matter of having the correct setting on the phone side at this point.

Yes, Line key is checked.
If I call in, I can see that the correct ARS rule is being triggered, though the ring group 200, but the calls still just ring to 100010 and 100011.

Ok, so I can create an authentication user line-100010 on the radius server It creates a PBX user for each authentication user that is created, so I used 20 for the PBX user ID. The phone now registers with both 100010 and line-100010. I need to take a moment to set up the rest of the phones. As of ...

Yes, it is. Oh, so I actually have to create a line-100010 user. Do I have to set both the user and the Assigned ID to line-100010? We normally set up users in RadiusCat Billing, though this will not work here because I think it uses numeric instead of varchar for user IDs. I'll have to try it out ...

1. Brekeke Product Name and version: SIP Server and PBX 2.4.5.5 M-T 2. Java version: 3. OS type and the version: Win 2008 R2 4. UA (phone), gateway or other hardware/software involved: I'm currently trying to set this up on Yealink SIP-T26P 6.60.0.120 and Panasonic_KX-TGP500B04/12.10, but it wouldn ...

In case anyone is wondering, I just used ARS to look for the extra "1" and deploy in the correct format.

1. Brekeke Product Name and version: SIP Server and PBX 2.4.5.5 M-T 2. Java version: 3. OS type and the version: Win 2008 R2 4. UA (phone), gateway or other hardware/software involved: Linksys PAP2. They are using digital ESI phones 5. Select your network pattern from http://www.brekeke-sip.com/bbs ...