Vodia PBX
-
Posts
11,110 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Vodia PBX
-
-
The PBX does what can be done. But most ITSP simply do not respect the information. SS#7 supports it, and it is a know feature in most digital systems. But today, the PSTN gateways still have a problem with it.
See http://wiki.pbxnsip.com/index.php/Outbound_Calls_on_Trunk, especially the "f" flag. You might have to try out which mode (Remote-Party-ID or RFC 3325) your provider supports.
-
That's a good one. Seems like we need a translation for UK... But we were seriously considering recording prompts because of the different accent in UK. That would be just another reason to do it.
-
You mean you want that the PBX walks through a sequence of service flags and then makes a decision if one is on? Interesting idea. I guess the short-term workaround would be merging the active times into one flag and then use that one for making routing decisions.
-
I guess you are not using STUN on the phones?
So far it seems that other installations do not have such a problem.
You can do PCAP traces both from the phone and from the PBX - then it should be easy to see where the RTP gets lost.
-
Well technically nobody is on hold in a hunt group - it just rings. Even if there are callers agead, they get not queued. That is the job of the agent group.
Once they are connected is it a regular call, that means the domain rules for MoH apply.
-
We have made a little MIB for the pbxnsip's available objects. Can anyone verify this? We are not even sure about the syntax, so please don't expect too much. But we want to get this thing off the table.
--
-- MIB for pbxnsip PBX
-- Copyright ? 2007 pbxnsip Inc.
--
PBXNSIP-PBX-POLL-MIB DEFINITIONS ::= BEGIN
IMPORTS
enterprises
FROM RFC1155-SMI
OBJECT-TYPE
FROM RFC-1212;
pbxnsip OBJECT IDENTIFIER ::= { enterprises 25060 }
poll OBJECT IDENTIFIER ::= { pbxnsip 1 }
pollCallObjects OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
ACCESS read
STATUS mandatory
DESCRIPTION
"The Call Objects shows the number of call objects that
have been allocated inside the PBX. Note that usually
there are at least two call objects for a regular call,
and during call forking you might have even more. This
object will give you a good overview on the internal
resource usage of the PBX."
DEFVAL { 0 }
::= { poll 1 }
pollRegistrations OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
ACCESS read
STATUS mandatory
DESCRIPTION
"The Registrations object shows how many extensions are
actively registered with the PBX. This object gives you a
good overview on how many active users the system has."
DEFVAL { 0 }
::= { poll 2 }
pollMessages OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
ACCESS read
STATUS mandatory
DESCRIPTION
"The Messages object shows you how many voicemail messages
the system currently has stored. Note that when you do
Email-forwarding, the messages are not stored on the PBX."
DEFVAL { 0 }
::= { poll 3 }
pollCallAttempts OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
ACCESS read
STATUS mandatory
DESCRIPTION
"The Call Attempts object is useful to measure the Busy
Hour Call Attempts (BHCA) number. This number is useful
when you want to see where the limits of your system
are. The BHCA number is a important performance number of
traditional PBX. Feel free to compare the BHCA value of
your modern CPU to the value of an old-style hardware
PBX."
DEFVAL { 0 }
::= { poll 4 }
pollSuccessfulCalls OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
ACCESS read
STATUS mandatory
DESCRIPTION
"The Successful Calls object is similar to the Call
Attempts, but is measure the number of successful
calls. The number is increased when the call
terminates. The number can be used to determine the busy
hour call performance of the system. Please note that on
this software PBX, not only the call establishment takes
resources. The call traffic itself also causes significant
traffic, especially when the CPU has to do codec
translation."
DEFVAL { 0 }
::= { poll 5 }
pollMediaCPULoad OBJECT-TYPE
SYNTAX INTEGER (0..100)
ACCESS read
STATUS mandatory
DESCRIPTION
"The Media CPU Load object show (in percent) how much
time the media CPU threads spend in processing. This
information is very important, because as this number
approaches 100 % the jitter gets worse and the CPU
eventually will not be able to process all media streams."
DEFVAL { 0 }
::= { poll 6 }
END
-
Oh, incoming? Then you can just set an alias name for the account where you want to send the call. Or use some of the extended regualr expression tricks shown on http://wiki.pbxnsip.com/index.php/Inbound_...s_the_extension.
If the gateway is not sending the Caller-ID, well then the PBX cannot fix that any more.
-
Did you try the prefix setting for the trunk? This way, you can put something in front of the extension number. In most parts of Europe and the rest of this planet except NANPA that solves the problem.
-
Can you tell us what timezones that are? Ideally in the PBX timezone format... (see http://wiki.pbxnsip.com/index.php/Localization#Time_Zones). Then we will include it in the next build. It is clear that we don't have all time zones, but don't forget that we want to support multiple zones at the same time and we want to be able to automatically provision them!
-
We started a script collection on the Wiki. Probably some scripts can do a lot of work, e.g. this nice Password script http://wiki.pbxnsip.com/index.php/Shell_Scripts. There we should also include stuff that does other useful stuff, e.g. setting up domains automatically.
-
-
2.0.3 has just been moved to the "released" state. It seems to be a great improvement to the 2.0.2, although the 2.0.2 was also not bad. See the (updated) release notes at http://wiki.pbxnsip.com/index.php/Release_Notes_2.0.3.
The big bullet points are T.38 fix and SRTP fix. For Linux, the great thing is the strict scheduler usage, in our day-to-day usage that made a big difference regarding jitter. In Windows, we now (again) support Windows 2000 (fingers crossed a little bit).
-
Well, in general you should try to avoid by all means to mix multiple-digit length extensions. Especially when they overlap.
Bad: having extension 20 201 202 203.
To the question: There are a few exceptions. If you have set direct destinations, they will be (of course) processed first.
If there is a mailbox prefix and the first digit matches that prefix, well then the length is not being checked (ops), instead the PBX waits until there is a match. The mailbox prefix case does not work if you are using an external voicemail system, because the PBX has no idea what extensions are available there.
As a rule of thumb: Use extension names starting with 2..7 and use a fixed length (= 2 or 3 digits). Use 8 as mailbox prefix. Do not use 9 as default outbound prefix (make numbers diallable as they are without any prefix).
-
In 2.0.4 we'll do a overhaul of the AA, including a multiple-language support that is parallel to the other options "for sales, press 1. For support, press 2. For Spanish, press 3." or so. Then we can make it also explicity selectable what callers hear as initial annoucement.
-
The configuration is really a black magic. That is why I would recommend to use the plug and play mechanism and set the list of watched calls. Then those calls should be visible on the phone. You can monitor CO lines as well as extensions. Make sure you have a 2.0.2 (or a 2.0.3 beta) release.
-
You can always have "dummy" extensions for parking calls.
Also, you can use ACD for "parking" calls - then they will have the real waiting experience. ACD are perfrect for stacking up callers...
IMHO the real problem is not functionality, it is usability. All those star codes are nice, but try to explain that to the plain user. Therefore, we tell people to hold the call and call it "parking", then other can just be "picked up" held calls. In TDM systems you could not have two calls on one physical cable, that is where the confusion starts. In SIP you can, and you should do it.
-
Okay, lets collect requirements for SNMP and then we do a (one) improvement round on that. But please... no SNMPv3 :-))
-
Check out http://wiki.pbxnsip.com/index.php/Inbound_Calls_on_Trunk. For example, you can use a pattern like !(.*)!\1!u!123! to default to auto attendant 123.
-
Yea so far the only card that we are supporting is Eicon/Dialogic through their SIP API. Sangoma is really a interesting topic, especially if it would be available for Windows. Need to investigate that!
-
I guess that one is fixed in 2.0.3, see http://wiki.pbxnsip.com/index.php/Release_Notes_2.0.3#Emails.
-
Did you see http://wiki.pbxnsip.com/index.php/Login? What information is missing there to solve the problem?
-
We have uploaded a brochure at http://www.pbxnsip.com/download/flyer070413.pdf. If you are interested, we can also give you professional handouts (glossy paper, offset printing). In this case, contact pbxnsip sales.
-
He can just visit his address book from the web interface and change the contact type.
-
Here we go with the first important fix (the 1707 had a very aggressive DoS protection):
http://www.pbxnsip.com/download/pbxctrl-2.0.3.1708.exe (Windows XP)
http://www.pbxnsip.com/download/pbxctrl-debian3.1-2.0.3.1708 (Debian 3.1)
http://www.pbxnsip.com/download/pbxctrl-rhes4-2.0.3.1708 (RedHat ES4)
http://www.pbxnsip.com/download/pbxctrl-suse10-2.0.3.1708 (SuSE10)
Multiple service flags
in Auto Attendant Setup
Posted
All these holidays are a pain. No doubt. Maybe there is a web site that tells if "today" is a holiday in a specific region or not. Then the PBX could go there at the beginning of the day and turn the flag on or off automatically.