Thanks a lot, Hope

We have tested both our scenarios using the July 18 dial plan and the above ARS IN rule, and it works fine. So we are now free to upgrade our PBXes.

Thanks again for taking the time to help out.

thanks again Hope Still no positive result. We have run Wireshark, and looked at the SIP packets. The incoming call is offered (INVITE) to 1000 - which is a valid user / extension on the PBX. The PBX replies "486 busy here" and the caller gets busy tone... Is there some other option we can try? Or ...

Thanks Hope That doesn't quite do what we want. Sending all the calls from a VoIP device to one number defeats the object. For example, we have an ISDN gateway (Patton SN4960) which accepts incoming calls from PSTN. There is a number range associated with this, to give a DDI (Direct Dial In ...

We have tried the second SIP server dial plan - no change, still doesn't work. The called PBX replies "486 Busy Here" and the call fails. Calls from the new PBX to the old version (2.1.5.6) work fine. I'm not sure what should be typed in the ARS "IN" pattern. The deploy pattern "To:" says PBX_user ...

1. Brekeke Product Name and version: Brekeke PBX V2.1.5.6 & V2.4.9.0 2. Java version: Java 6 Update 25 3. OS type and the version: Windows XP 32 bit patched up to date 4. UA (phone), gateway or other hardware/software involved: Brekeke PBX 5. Select your network pattern from http://www.brekeke-sip ...