Jump to content

Vodia PBX

Administrators
  • Posts

    11,106
  • Joined

  • Last visited

Posts posted by Vodia PBX

  1. I read some things about receiving fax via auto attendant but the wiki states you have to use a pattern with f but I don't understand where I have to add it.

     

    I want a normal trunk to be directed to an extension or auto attendant (what is necessary to make it work) so Zoiper can receive faxes.

     

    It's NOT an option to have a PSTN fax there. They are mobile.

     

    The perfect solution would be fax2email.

     

    Can't I force the codec to be T.38 on an extension so Zoiper will answer the call as a fax instead of Ulaw? (which now happens whan an analog fax calls the faxnumber)

     

    Thanks in advance.

     

    So you want the AA detect the CNG tone and then redirect the call to a specific FAX extension? Use the DTMF tone "F" for that (F is CNG in the PBX). It is like someone pushes the "F" key instead of e.g. "1".

  2. Is there any plans to change this in pbxnsip ?

     

    Yea, the whole QoS story is not over yet. DiffSrv is extremly basic, that is clear. What Microsoft did in 2000 was a good start, but in the meantime so much stuff happened. For example, MPLS might be very interesting to ensure that the user has a TDM-like QoS experience.

     

    The other problem is that we still want to support Linux (and BSD-style OS). That Windows API does not exist in Linux. Having something that works in both OS would be the best solution.

  3. Just ran into a second situation I did not think about. What if you need to do it to an ITSP that requires registration? Can you some how include the username/password in the static registration, or can you tell it to use the trunk's?

     

    Well, you can't run the call phone call with a static registration "through" a trunk - however you can still point the call to the service provider. There is a little chance it will also work, but not high.

  4. i think now my pbxnsip and my freepbx is can integrated ,

     

    i see in pbxnsip trunk is regitered, and on freepbx is the same registere too,

     

    pbxnsip can dial extention on freepbx , but from freepbx still can't dial extention in pbxnsip

     

    I would use the "gateway" mode on the pbxnsip trunk. If both the pbxnsip and the free PBX is on a routable address than this will be much easier and you don't have the registration traffic. Just make sure that you are using the outbound proxy in the pbxnsip trunk.

  5. This works without the authentication problem that I was having when using the HTML folder, however some phones send additional info in the url that causes your web server to return a 404 error. IIS ignores the additional info. The following is the get command from a packet capture.

     

    GET /services.xml?locale=English_United_States&name=SEP00070E16446E HTTP/1.1\r\n

     

    Is there any way to allow your built in web server to allow this, and ignore everything after the ? since I am not utilizing the different localles

     

    I guess from the MAC address this is a Cisco phone...

     

    The filename never contains the parameters after the question mark, the PBX does that part right. But because there is no path in front of the "services.xml", the PBX thinks that this file is for the user-interface of the PBX, not the provisioning part.

     

    Usually there is a way to tell the phone from where to fetch the information. If you find any way to provision something like "/provisioning/services.xml?..." then life will be a lot easier.

  6. I have upgraded snom 300 & 320 to version 7 (7.1.30 ), after upgrades I no longer see call history - missed calls, received calls and dial calls. Afer an incoming or outgoing calls when I go into the call history to review it display "no data available". I further upgrades to 7.1.33 and the results are the same - still no missed calls, received calls and dial calls data

     

    If those calls were for a hunt group and someone else picked the call up that is supposed to be a feature...

  7. Sorry, I think we are talking about different things. I will discribe it in more details:

     

    Phone "A" Internal user "A" in Button-Group 1

    Phone "B" Internal user "B" in Button-Group 1

    Phone "C" Internal user "C" with Number "1234"

     

    "C" is calling "A" and "B" picks this call with a Button on the phone. The Snom display ( Phone B ) shows "*6015775" and not the number from Phone "C" as the calling party.

     

    Oh got you.

     

    Hmm, the best thing would be if the phone displays the label in the screen right from the beginning (maybe make a call to "label" <sip:*601xxx@domain>, then the display method on the phone can figure out what to display). If the PBX changes the display after the connection, there would be a fickering on the screen before the PBX can send the proper display input.

  8. That doesn't seem to be what is happening.

     

    It is getting the message to turn on button 13, but the symbol isn't appearing. Button 13 on the pbx is a DND and I changed the function key for DND to a button type instead of key event and put in 13.

     

    Anything else I need to set to make it appear?

     

    Don't call the button "13", better call it "dnd".

     

    That feature requires version 7.1.33 on snom.

  9. Both identical, at exactly the same time, with exactly the same content :

     

    Ouch, probably because first the extension is busy, and then the call gets disconnected without being connected. Both reasons to send an email out.

     

    The good news is that it does not get forgotten!

  10. I always seem to get two emails for missed calls, not one. It's done this for as long as I can remember but I'm not sure why?

     

    You mean you get one email for the missed call and another email for the CDR? Or are they exactly the same?

  11. It is possible to see the number from the person who is calling and not *601<call-identifier>?

     

    Not in the star code. But the PBX sends along with the star code a label for the button, which provides additional information.

     

    If you want to hard code a specific number, then you can still use the *87xxx starcode for "end-user" initiated call pickup.

  12. I saw that with 7.1.33 the DND function key can be set up to use the buttons package with PBXNSIP. If using it in this way does it show the DND icon on the display to show the status from the pbx instead of showing the light next to a standard function key?

     

    Exactly. The "LED" is in the screen and looks like a DND symbol.

  13. I have been experiencing an intermittent problem with DND not turning off using snom's with 7.1.33. It seems like the phone is dialing the *79 to deactivate it because I see the call appearance light up when I press that key and the DND icon goes away on the phone goes away, but the pbx doesn't turn it off. I can't be 100% sure that the pbx is getting the *79 invite because by the time it is noticed that DND is still enabled, there have been several calls and it has been pushed out of the logs. Has anyone else been experiencing this?

     

    Yes, the whole DND cloud is a "pain in the neck" problem.

     

    Therefore, we introduces a couple of things in 3.0:

    • At midnight the PBX may reset DND on all extensions
    • The buttons may now have a name "dnd" (snom phones) which are synchronized with the state of the PBX. This works with the defeult configuration of the PBX.

    The problem remains if users turn DND on locally on the phone. If that is the case, the PBX has no chance to fix the problem.

  14. We have groups of people who are able to pickup calls within their pickup-group. This is done with the buton feature from snom/pbxnsip. When someone pickup a call from another an increasing originator-numer is shown.

     

    1. pickup "*6015775"

    next "*6015781"

    next "*6015784"

    ....

     

    On the called phone the right originator is shown. Do I have something to configure?

     

    That translates into *601 meaning pick a call up and 5775 being the call-identifier.

     

    The PBX automatically tells the phone what code to use for the next pickup. So you don't have to configure anything.

  15. SDP looks fine - setup is Vega ISDN->asterisk->PBXnSIP. It's been working fine until (as far as I can tell) we installed the v3 build, though that could just be co-incidence. Also all normal incoming calls are fine, it's just when it tries to send it to VM.

    I can PM you the pcap if you want? It's only 160k

     

    Well in that trace we see that the Asterisk drops the connection.

     

    When the PBX picks the call up, Asterisk tries to re-negotiate the codecs (obviously because it wants to change the IP address of the RTP) and then sends a BYE (no idea why). Maybe you have to upgrade to the latest 1.4 version. Maybe you have to put something like canreinvite=false or something like that into the configuration files, so that it does not attempt to make the PBX talk directly to the Vegastream.

  16. Is there any way to allow the extensions that are ringing via a huntgroup to still call fork to a cell phone?

     

    There was another post recently.

     

    Bottom line. There is (static registrations). However, be prepared for a lot of problems with offline cell phones that will pickup immediately.

×
×
  • Create New...