Sorry to come to the party late. Been a busy past few weeks. I'd like to add my $.02. Or $.05, as it were.
1) I would like to see a graphic representation of a handset's digit map before committing the change to the handset. As much as I love to fly by "trial and error", sometimes I just don't have the time. Specifically, I would like to be able to take any given digit map and any given digit string and see how the gateway is going to handle the digit string based on the specified digit map. For example, if input a digit map of "[2-9]11|0T|100|101|011xxx.T|9011xxx.T|9[2-9]xxxxxxxxx|*xx|[8]xxx|[2-7]x x" (or any portion of that digit map), a digit string of "9105552222", then click on "dial" or some such, I'd like to see exactly how that digit string is going to be handled based on the digit map, the dial plan and the dial permissions. Clear as purple crayon? Cool. (I'm happy to storyboard this if it helps.) 2) MOH. I kind of have a gripe with how this presently works. I don't like having the MOH start at the first of the file each time the user is placed on hold. It doesn't mesh very well with how my boss wants the hold music to function and is making it difficult to bring clients over to using sipx. In truth, I am not sure at all how to implement a "Rolling" or "Live" MOH system other than having a built in media player, if that would even work. In other words, I would like to see the hold music handled like a CD player, in that the music is always playing in a loop and when a caller is placed on hold, they hear the media in progress, rather than starting at the beginning of the media file. Am I being coherent? Hope so. 3) I have several clients that are using VOIP with another SIP provider (a company called Jive, based in Orem, Utah). They have heavily modified their installation of SIP (I think they are using either SipX or Asterisk) to the point where I really don't like it (such as some changes that affect only the backend server require having the handsets re-register to take effect.); however, one BIG thing they have developed that I would love to see is what they call the "DialPlan Editor". Basically this is a graphic representation of the inbound call flow. In this editor, one can make changes to the call flow using the UI. I am not suggesting anything this comprehensive; however, I think it would be useful to be able to see a graphical representation of what happens when a call is received and follow it through the call flow and maybe when a call is placed. 4) I think that the current system for AA schedules could be implemented better. I saw a suggestion on this earlier, but for full AA integration, I would like to see a better way to handle 'time conditional'. On an inbound call, between hours 8 AM to 11:59 AM, and 1 PM to 4:59 send the call to AA 1. Between the hours of 12 PM and 12:59 PM, send the call to AA 2. Between the hours of 12 AM to 7:59 AM and 5 PM and 11:59 PM, send the call to AA 3. On Saturdays and Sunday, from 12:00 AM on Saturday to 11:59 PM on Sunday, send calls to AA 4. On Holidays, send the call to AA 5. The current system of having a Default AA, Working time AA and Holiday AA only is less granular that I particularly like, especially since the Working Time AA is not flexible with the days or hours. Granularity is what I'm looking for with this feature request. 5) I would like to see the current function of loop back detection enhanced to allow a hunt group to ring an extension that has already been part of the call flow. For example, right now a caller is sent to the AA during working hours, who is then immediately transferred to extension 199 (Our office manager). If she doesn't answer within 30 seconds, the call is transferred to a hunt group that has extension 200 (also the office manager) and then if no one answers, the call dumps to the voicemail of the last extension on the hunt group (200). The problem is that to make this happen, I have to assign 2 extensions to the office manager's handset. I understand how the loop back detection is useful. But if I specify that I want the call to go to extension 200, then to a hunt group that includes 200 and finally dumps to the voicemail for 200, I want the caller to follow that pattern. I have a few more requests, but I will keep it at 5 this time. Thanks for opening it up for suggestion (in my mind's eye, I see these 5 items as simplifying how SipX works. Except maybe the MOH request.). --Jake Ballamis Systems Administrator/ Support Manager Alliance Technology Solutions, Inc. _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/ _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
