Vodia PBX

What do you mean by locking up? Do you have to reboot the phone? Or does the PBX simply do not react to DTMF any more? Maybe there is a audio prompt misssing, so that the playback stops and the PBX waits for more input. Are there any other cases when the playback gets garbled? When listening to voicemail, "1" and "3" are backward and fast forward; which is always a little bit garbled. Maybe that is the problem?

Where did you get the white box? So it has only one Ethernet port on the back? Maybe you can try to swap it into a black box with two ports. The problem with that box is that if you apply the software update, it will get tricky to get back to the back, as the IP config probably got screwed up.

I have no idea. But usually it is a good idea to use the latest service pack.

If the secretary's phone is able to send the neccessary subscription for MWI then that is no problem. When using the "buttons" feature it is also possible to put the MWI on a button. PAC also supports this.

Okay, so he wants a kind of glorified park orbit. Yes that makes sense. The first step would be trying that without OCS - just a deflection into the agent group. If that works (can't try it right now) then we have an OCS issue. Could be a good feature also without OCS. Maybe worth a button on a phone.

Very strange. Does it work properly if someone from outside (PSTN) calls and gets into the mailbox?

For presence, the extension itself is responsible for updating the state. I believe they have no effect when using the agent mode. Well, the PBX is a "stupid" presence agent. We were thinking about making it a smart agent, which calculates the presence state based on registration and calls. However, the whole presence story so far must be seen as a kind of sales hype; practically nobody used it in the PBX context (AFAIK). In the PBX environment, people look more for BLF and SLA. Maybe Microsoft OCS will change that.

Great! The next 3.3.1 version will have it in the GA build.

Why don't you send the call to the agent group in the first place? This agent group would have only one agent (small group), which may use a static registration that points to the OCS. I believe the redirect will get very tricky. Maybe we need to set something up in our environment as well, to see how we can deal with this.

Is the hearing limited to the Aastra handsets? That would be very strange. If you can get a wireshark trace it should be possible to see what is going on on the media level. Filter for the IP address during the capture, then we don't have to screen MB of data.

If you are running the HTTP port on port 80, then you don't have to put the port there. If you are using a snom 370, then the URL should look like this: http://xxx.xxx.xxx.xxx/provisioning/snom370.htm.

401 means that the authentication did not work. Are you sure that you have chosen the right password (the web password)? It does not matter if you disable the MAC trust or not. If you are not in the LAN than that flag has no effect. I tried it again from here. It worked if the phone uses a standard port (80). Using a non-standard port did not work.

http://pbxnsip.com/protect/pbxctrl-debian4.0-3.3.1.3171

Oh you want a callback when a hunt group becomes available? Call back only works if you dial a specific extension. (It is hard to imagine how you would find out if a hunt group becomes available again.)

What OS?

No, there is also a change regarding the identification of the device that is being provisioned. If the ARP cache contains the IP address of the device and it also matches a known MAC address, then the PBX trusts that MAC address (can be disabled). Otherwise, it will always use HTTP authentication.

When you provision outside of the LAN, then the MAC plays no role any more; you better remove it. The PBX identifies the account only by the authentication info that you provide.

Currently the callback is really just for the callback. You cannot do something else than dialling the person that became available. Did you try to press "*"? I am not sure, but it could be that this is a escape code that brings you back to the auto attendant.

Any chance to try 3.3.1 out? What OS?

Hmm. The PBX sends the T.38-reinvite to the gateway, but there is no response in the log. Does the gateway reply at all? If there is no reply, it is understandable that the FAX does not work.

If you are not in the same LAN; you must set the username and password now. I used a string like "http://pbx.pbxnsip.com:2345/provisioning/snom820.htm", and that worked without problems. Using 3.3.1.3171, though. If you need a build to try this out, let us know.

Better don't use that version. Move to 3.2.

Is the "prvisioning" a typo (should be "provisioning")?

Didn't we have this topic yesterday already?!

What version of the PBX? I had the same problem myself today