Jump to content

Vodia PBX

Administrators
  • Posts

    11,085
  • Joined

  • Last visited

Posts posted by Vodia PBX

  1. With the PAC coming up that is no more a problem (see the new PAC forum). However on the snom 360 I think it is currently not possible. Maybe in a new version the phone is able to present a short light flashing when there is a MWI on the extension.

  2. Is there a hard limit to the amount of buttons that can be added to a button group? are only line an extension buttons supported, or all other button types are also suported?

     

    You mean limit on the PAC? On the PBX, there is no limit...

  3. 1) see below we recieve an "INVITE" from exchange but passs it through to broadvox as a "UPDATE" can it be passed through as an "INVITE"?

     

    2) and more important can we limit the protocols to just T38 so there is no choise?

     

    1) There is a global setting called "support_update", if you set it to false the PBX will use INVITE (see http://wiki.pbxnsip.com/index.php/Global_Configuration_File on how to set it).

     

    2) Yea, I agree that the audio with port 0 is really strange (well, that's how we get it!). Maybe Broadvox can try with the INVITE and if that does no work we can make a version that takes the audio part out in this case.

  4. Do i need some special settings for the teles.Gateway(ISDN) Trunk?

     

    No. What is the outbound proxy for the ISDN trunk? It should be something like 127.0.0.1:5062 if the gateway listens on port 5062.

     

    Also what is the user dialling? Something like 06912345 to get a number in Frankfurt?

  5. Okay, that should be simple. If you have two trunks with the name "ISDN" and "VoIP", then the dial plan would look like this:

     

    Priority=200; Trunk=ISDN; Pattern=06*; Replacement=06* (if you want to keep the 06 in the front, otherwise just *)

     

    Priority=300; Trunk=VoIP; Pattern=*; Replacement=*

  6. The particular phone, as well as the other 360 in the office run the following firmware, since running the latest 6.5.17 or 7.1.30 render both phones incapable of connecting with PBXnSIP.

     

    Well, at least the 7.1.30 should work find with the PBX.

     

    Maybe you should also use the registration tracking emails to see when exactly the phone goes offline.

     

    And also keep in mind that sometimes the network also has active components that go offline for some time. We have had switches that needed to be rebootet from time to time. Then if you see that the registration problem occurs on specific parts of the network that might be a useful hint.

  7. I have two NICS (192.168.1.1 and 192.168.0.1) but I keep seeing this entry in the status general file: 127.0.0.1 [::1] 192.168.1.1 [fe80::5efe:c0a8:101] 192.168.0.1 [fe80::5efe:c0a8:1] 192.168.36.16 [fe80::5efe:c0a8:2410]

     

    I also noticed in my logs that I keep getting: SNMP: Received packet from non-trusted source 192.168.36.53:49246

     

    So, can someone tell me what this means since I have two NICS only and there appears to be a third ip address connecting to the management interface. Could it be that someone on my VPN is attempting to get into the admin settings of PbxnSip, I dont allow remote connection though?

     

    The [...] are good news - your system supports IPv6. If you don't use it, it is not a problem for you. Later, if you use IPv6 it will automatically work.

     

    192.168.36.53 obviously tries to get SNMP information from the PBX. This is not unusual, there are many SNMP programs out there that try to connect information from the network. Because that IP address is not listed in the trusted IP addresses, the PBX will not respond to the requests - no security leak.

  8. Is any way to that when a call comes in it should display both the name and the number. It is only displaying the name on my test system, if the name is not availible it displays the number.

     

    There is a settings called "Number Display Style" in the settings of the phone. Did you try "Name + Number"?

×
×
  • Create New...