Jump to content

Vodia PBX

Administrators
  • Posts

    11,085
  • Joined

  • Last visited

Posts posted by Vodia PBX

  1. its has been days but i havent heard anything from your side

     

    is it possible also to fix this problem or should i forget about support

     

    Go to System/PSTN Gateway. There you find settings for Tone 1 (Busy) and Tone 2 (Dialtone). Check if the dial tone settings there match the local behavior in Kuwait. Usually it should be enough to turn Busy tone detection on. After saving, you need to restart the system.

  2. Is a Manual State Change accessing the WEB PAGE as the domain administrator?

     

    Or is a Manual State Change dialing the FLAG and are restrictions placed on which extension can dial the flag?

     

    The way I see it dialing the FLAG resets it, but not means other than WEB or SCHEDULE time to set the flag at this revision level?

     

    I was talking about dialling the flag. You can set the restrictions in the web interface.

     

    Maybe just set up a flag with a 5-minute service duration and try things out...

  3. We have two phone lines connected to the cs410 and both of them will go to our hunt group. We configure three polycom phones that have line 1 for hunt group 100 and line 2 for hunt group 200. Is there any way to configure the inbound calls from FXO1 going to hunt group 100 and from FXO2 going to hunt group 200? This way we will know that the inbound call is coming from which PSTN lines.

     

    The reason is we would like to know whether the call is coming from our customer or our internal people. Since we always give line 1's phone number (FXO1) for our customer and line 2's phone number (FXO2) for our internal people.

     

    That can be done. The FXO gateway has four DID numbers that will be in the To-Header that identify the line being used. You can use the rule in http://wiki.pbxnsip.com/index.php/Inbound_Calls_on_Trunk to route the inbound call then.

  4. Can you explain how the service flag now supports dynamically being changed?

     

    The PBX just accepts manual state changes also for automatic flags. Then when the automatic transition kicks in, it keeps the state if the desired state is already present.

     

    In other words: If the secretary shows up early in the morning before the flag is actually active, she can dial the flag number and then the day mode is on already. Later when the automatic flag change would fire, the flag stays where it is.

     

    Things are a little bit more complicated in the evening. If she decides to stay later, she has to wait until the flag goes to night mode, then dial the number to change it back to day mode. Before she goes home, she needs to set the flag to night mode manually again.

  5. after much testing.... I find changing the settings to "Presence Agent" does not help either....

    The status is online updated correctly upon startup..... any other time its not working right....

    Please advice...

     

    You got any SIP traffic for the update that does not work?

  6. I am sure they took it out. I even found documentation confirming it on their web site. I have been using the * code for now, I would just like something a little better since the customers love the look, sound quality, and stability of the phones.

     

    I tend to agree. Plus an attended transfer into a conference that has a PIN really makes sense. You can call an external party, then dial into the conference and perform the attended transfer into the conference.

     

    I guess we have to put this on the feature list.

  7. We have install 4 Polycom Soudpoint IP 550 in our company. Periodically, we are seeing 500 internal error message from Polycom Phones and we don't know what is causing that. Here is the logfile we are seeing the error message.

     

    The "SIP/2.0 500 Internal Server Error" is for the NOTIFY and usually it has to do with subscriptions that are still in the server but already expired on the phone. After a reboot this is normal if the phone comes up within the subscription duration and there is no reason for concern.

     

    The reason why the call gets rejected is "SIP/2.0 488 Not Acceptable Here". In the INVITE you can see that the PBX obviously does not offer any codec to the phone, which makes that understandable. Check your codec settings for the system, it seems the problem is there.

  8. So far there was no need to have attended transfer into a mailbox. Are you sure those phones don't have blind transfer any more (check the more button)? I can't imagine Cisco took such a basic feature out.

     

    Workaround would be to use the *77 transfer code, but that would make the phones really look extremly basic.

  9. If I just give the phone the IP of the pbx:

     

    Profile Rule: 192.168.32.30

     

    Then the phone doesn't register. In fact there are no log entries so it looks like it doesn't even try.

     

    Hmm. Maybe better forget about TFTP... Check out the attached files (you can also put them into the html directory, if it does not exist yet create it). There it says you should out http://192.168.1.2//spa$MA.cfg (if 192.168.1.2 is a PBX IP address) into the Profile Rule.

     

    I assume you have put a MAC address or just a star into one of your extensions? There is some general information at http://wiki.pbxnsip.com/index.php/Prepare_...r_Plug_and_Play.

    spa_1st.txt

    spa_phone.txt

  10. I am trying to setup call accounting, and I am having a problem seeing the extension of the conference bridge if a call comes in, goes through an auto attendant, and then into the conference bridge.

     

    My CDR format is:

    $m $e $b $B $d $o $c $f $t

     

    The output I am getting is:

    voip.office.twincitytelephone.com 20080604 163107 42 <sip:4193922384@voip.office.twincitytelephone.com> conference

     

    I would expect to see the conference bridge extension number right between the domain, and the date.

     

    Maybe the workaround is to stick to the "conference" string for clear identification it was a conference call.

     

    In 2.1.11 we'll change the type to 'v' because 't' was supposed to give the To-header. The extension is empty because the call does not go to a registered extension.

  11. Doesn't look like the SPA942 has tftp options via the interface. Is it just a matter of specifying the tftp port after the IP of the pbx?

    Just put the IP address in... Then the phone will automatically choose TFTP.

     

    And by setting passwords - do you mean the extension passwords? There is no place to specify password in Admin/Ports/TFTP

     

    The setting is called "Allow TFTP Password" - just set it to "always", then later when everything works you can lock this down.

  12. Does anyone have the lines necessary to add to the provisioning script to auto provision the Linksys SPA942 phones?

     

    Just point the tftp server to the PBX. It should work already... Also make sure that you do provision the passwords (Admin/Ports/TFTP). The problem is here that Linksys requires their own little secret algorithm for encrypting config files, which they won't gibt to use (the secret, not the program :rolleyes: ).

     

    Also, it helps if you are using Option 66 on DHCP.

  13. After doing some research here, i found that the problem is with CO lines. If i remove all the CO lines from our system, the incoming calls roll out to the cell as expected. If i put the CO lines back, the calls immediately hang up.

    I'd really like CO lines so we can monitor what lines are in use on our SNOM360's. But in the short term, removing them has my system working.

     

    So you are sure that there are enough CO-lines on the trunk? Check the account overview on the web interface, if the PBX seizes a line it will show it there (you'll see the caller-ID associated with the CO-line).

  14. btw. the number 59 under RdrctNum=59 is the one we use in the trunk for the OCS Mediation Server. Setting "Assume that all calls come from user:"

     

    The "Assume that all calls come from user" was a workaround to get things working at all - the Caller-ID presentation had lower priority. But maybe there is a way to configure the PSTN gateway to use the From-header for rendering the Caller-ID.

  15. However, I would like to know How to get the correct "presense information" displayed on the other party?

     

    I do not see the icon change in xlite from something offline to online... regardless of whether the other party is registered or not....

     

    For that you need to put the party into the contacts list. There you can also see your own presence status. We tried it, and it works okay. The PBX is just a relay of the status, not looking into it.

  16. We have a 5 static ip plan (4 available). However, the WRT54G obviously isn't capable of muli-wan ip's.

     

    Is there an affordable and reliable router (with at least some basic QOS) you could suggest?

     

    If you are just using IP on the WAN side, it might be an option to use the WAN interface of the CS410 for the public IP. Then you just need a hub/switch to connect the WAN to the router and the CS410. Then the CS410 will use one public IP address (and a private IP address, make sure it is a static one to avoid problems with the default IP gateway) and the router will use another public IP address. However in this setup, QoS will remain a problem.

     

    In the ultra-low cost segment, I only know about OpenWRT project where you essentially load Linux on the router. That gives you a lot of options if you are able to setup Linux routing.

     

    We did search for low-cost router solution some time ago. In the end we gave up on it and bought a standard Cisco router on eBay.

  17. I can't find (in PBX, Wiki and forum) how to set a delay before the AT picks up, now it directly answers but it causes things like somebody doesn't here the complete message.

     

    So I want to hear the " ringing" tone for e.g. 5 sec before the AT picks up, where can I set this option?

     

    AT the moment there is no such settings. IMHO it would not be a auto attendant setting, as the same problem also exists with all other types (e.g. mailbox, IVR node). And it also depends on who is calling, e.g. a call from an extension to the auto attendant might be very very fast while a call from a trunk might be very slow. Maybe it would be a trunk setting. OR maybe it even has to be a setting of the PSTN gateway?

×
×
  • Create New...