Vodia PBX

The source if the TFTP address can tell the PBX what interface to use. BTW there is nothing like an "internal" or "external" address. Think about a system that has ten IP addresses (LAN, WAN, VPN1, VPN2, WiFi, IPv6, ...). The OS routing table is responsible for determining what IP address to use.

It should do that (of course). It should be possible to provision internal and external phones through the same TFTP socket.

No, TLS is used to send out the INVITE through a secure channel. In SIP, you have to allocate the RTP ports when sending out the INVITE (unless you want to end up in an endless discussion about offer/answer). So it is a pretty expensive operation. Apart from that, I think if all 50 phones are ringing when someone calls in, not sure if that is what you want in an office.......

Is it really related to the MWI? Maybe it is something stupid like instable power? Kind of hard to believe SPA reboots on MWI events...

Hmm. Seems that the logic is screwed up again. That clarification for the explicit times was missing one negation - in other words the times you specify there are the times when the PBX would not call the cell phone. We'll turn it around, that will make life a lot easier.

Even if there is no RTP 50 INVITE are a challenge. Think about TLS, DNS, ENUM and all the blows & whistles that need to be taken care of. Plus people are waiting in line for address book lookups for all these 50 agents in their personal address book. Ouch!

Well, as said - the FAX recognition did work in our test environment. To me it looks more like a problem with the environment. Maybe the PSTN gateway does signal out of band, and then the PBX does not analyze FAX tones any more. Maybe try turning RFC2833 DTMF off on the gateway and tell the PBX to perform inband detection (admin/settings). And also set the codec preference to prefer ulaw, maybe there is a problem with alaw. If that works we can find out what we can do to use the out of band-detection cabability of the gateway to save CPU power.

I would change the preferences a little bit to 100 and 101 to make crystal clear what the preference is. But apart from that, that looks fine.

You mean "reset" like in "reboot, crash"? Does this happen out of the blue? Or is there a specific event, like an incoming phone call? Maybe it is just re-retching the configuration and for some reason thinks that it changed (which causes a reboot on the SPA devices).

Well, you can deal with that. But then you have to work with timeouts (in the AA, direct destinations). It works, but is not very beautiful.

Hmm. Does the PBX show the right time (e.g. in the log)? Maybe the domain is in a different time zone...

That is usually caused by routers that are not "ready for SIP" - their NAT implementation changes the ports. Or your refresh interval is too short and the router already closes the NAT binding. The result is that intermittently you cannot call the extension. It is a serious problem and you should fix this either by changing the router or by making the interval short enough for these routers.

Oh, so you are using multiple domains on the system? I assume that the inbound traffic does not have the domain name in the request?

This is a case of having seperate domains that want to call each other. Although they are located in different states, the case is not so much different than having the domains in the same data center, but on different CPU. First of all, you probably need two trunks in gateway mode. Both of them should trust each other, e.g. turn the accept redirect on (that should help with the question 2 below). I would stay away from prefix 1, it has a lot of problems (1xxxxxxxxxx being one of them). Better choose something in the 3xx-6xx area, if the business cards are not printed yet... You can use pattern 3xx and no replacement to route calls that have three digits. If you want to make a routing entry for x11 then you can just give that one a lower priority. You need to set the setting "Assume that call comes from user" for that. Then the PBX can use the dial plan of that extension, and it can also charge that extension. Hmm. Ideas are: A. Use the direct destinations (if there is still space available). B. Set up "ghost" extensions with static registrations that point to the other system, have no mailbox and an impossible-to-guess password. Not very beautiful, but that might solve the problem if there are noo many extensions in the other location.

Hmm. That seems to be a problem only for the SPA942; other phones don't have that problem, right? Any chance to get more insight? Maybe you can the "Log Watch List (IP)" in the Logging to the IP of the phone and monitor the traffic. Does the counter change or the "Messages-Waiting" (yes/no)?

It is generally not a good idea to ring all agents "immediately" because this creates a major hickup in the system, sometimes even in the network. IMHO gradually calling all agents is not so bad.

In the hosted environment, CO-licenses should not be the problem. But the good news is that we could just use the trunk allocation mechanism to limit the number of calls in that domain.

What version are you running? Could be a bug that was fixed in the latest & greatest.

That sounds like the PBX provides a contact in the SIP invite that cannot be routed in the phone. Does the Contact header contain something that the phone can reach? Maybe you can post the INVITE (from the PBX log) here and check if the IP address in the contact header is what you expect.

It will be included in 3.1.

It gets straight to the point and says "978-746-2777 is trying to reach you. Press 1". That has the benefit that you hear the original caller-ID (solving a common problem when redirecting the call) and you hear it right at the beginning.

:-S Yea we had the same issue with the calendar document. Seems it is something with the certificate and the https paranoia. Maybe you need to get a thousand dollar certificate before your browser eats this........

Are you getting anything? What does the web browser say? Are you using https?

Try "save as..." and then open it with a text editor.

At the moment the meaning is "call", not call legs or "trunk calls". We had this discussion recently, and the result is not clear yet...