Jump to content
Vodia PBX forum

Carlos Montemayor

Members
  • Content count

    168
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Carlos Montemayor

  • Rank
    Advanced Member
  • Birthday 11/25/1958

Contact Methods

  • MSN
    cmont2000
  • Skype
    carlos.g.montemayor

Profile Information

  • Gender
    Male
  • Location
    Monterrey, Mexico
  1. LDAP on GXP1630

    Hi, I have not been able to make work LDAP on a GXP1630. The PBX is a hosted version running 57.0 (Debian64) and the phone has its latest firmware which is Version 1.0.4.67. The phone did plug and play and all the section regarding LDAP looks like it got populated ok, nevertheless, the phone does not find entries in the LDAP directory. What could it be?
  2. star code for "the current time"

    I do not think so. Let me try to explain. In my country, there are no 10 digit numbers that could be dialed to get the current time. The incumbent carrier does have the service for their customers and such customers get it by dialing the following three digits: 030 Since we are not the incumbent carrier, dialing those three digits would not work. To follow that route, I would need to suscribe a couple of trunk lines with the incumbent carrier and then use them as global trunks in the pbx using an FXO gateway. The PBX already has a text to speech service built in. I mean, by dialing *61 the pbx announces the current balance of an account. It also knows the current time thanks to the ntp server that it also handles. So, the elements are already there, it would only be a matter of assigning a star code to have the service of saying the current time, no? perhaps *60 ?
  3. star code for "the current time"

    Hi, I know that this request may be seen as coming from the previous century, but well, although hard to believe, we have some users asking for this. Could you guys add the feature of announcing the current time? I know that we have *62 for wake up call, but this is a bit different. The feature would be of just saying the current time and that would be it. A more 21st century idea would be to trigger a look up to also announce the current temperature (based on user location). At the moment, the current time (that the pbx already knows) would be good. I know that most IP phones have a display that shows the current time but there are users with no display or are using an ATA or Gateway to enable analog phones. Well, for now, just giving the current time would do. Could it be something included on the next release? Cheers!
  4. GXP1630 loosing registration when ending a previously transferred call

    It was not exactly that, but we fixed it anyway. It had to do with some changes that we had done to the buttons template. We were trying to make the BLF button assignment through plug and play and we messed it up somehow. We put the latest firmware on the phone and on the pbx and used the clean templates (not the ones we had been modifying) and the problem was fixed Thanks!
  5. GXP1630 loosing registration when ending a previously transferred call

    Thanks for answering. Yes indeed. It is an attended transfer the one that is giving the problem. I have not tried a blind transfer. The user is an executive and receives his calls from a receptionist and attended transfer is the recurring scenario there. I will give 57.0 a try tomorrow morning (today is not a working day in the country) Cheers!
  6. Hi, We just encountered a weird behavior. The scenario is as follows: The IP PBX is Vodia hosted version 56.0 over debian The phones are GXP1630 with firmware 1.0.4.50 The phones were provisioned using plug and play The failure presents when the user tries to end a call that was previously been received by a transfer. The symptom is that when the "end call" button is pressed, the audio is lost but the call remains "active" and the phone looses registration with the pbx and the only way ro restore the phone to working condition is to reboot it. We have already tried using different transport methods (udp and tcp) and different ports (5060 and a different one) and we even upgraded the switch,from fast ethernet to gigabit, but nothing seems to fix the problem What could it be?
  7. Hi, I just enabled a Beaglebone Black Rev C to run the pbx software and I notice that after installing the operating system, the pbx software and the audio files for the language,there is still room in the eMMC memory flash, but not too much. So, It would make a lot of sense to use the Beaglebone Black facility of having a microSD Card device to use it to save CDRs, Recordings, PCAP Files and in general anything that is not the core application software. To make a test, I am using an 8 GB microSD Card and by using the df -k command under a terminal I was able to see where it is in the beaglebone black. The line that clearly shows the microSD Card that I placed is the following one: Filesystem 1K-blocks Used Available Use% Mounted on /dev/mmcblk0p1 7726080 4 7726076 1% /media/BBB_STORAGE I recognize the size of it (about 8 GB), that I have not yet used (only 1% is used) and the label that I placed in the microSD card at the time when I formated it (BBB_STORAGE) So far so good, however, I just do not know how to tell the pbx that it should use the mircoSD Card to write all those those files that could be eating the small room left in the eMMC flash memory. As always, help is greatly appreciated!
  8. Phantom calls on Yealink Phones

    Hi, Updating the firmware had already decreased the problem to about 50% Disallowing IP Calls seems to have reduced the problem to zero. (Although it may be too soon to evaluate) I found the Yealink Configuration Tool and also the option account.1.sip_trust_ctr. However, the options are only "disable" and "enable" and therefore cannot set it to "1" (no such option) Now that I understand that I had a couple of sites under attack, I increased the level of security of the firewall on the sites routers. Thanks for the good advice. Besides the risk, receiving about a hundred phantom calls is a big nuisance. One of the phones (the T20) was in a demo with a potential customer, I figure that I would not be able to close the sale with that behavior Can you elaborate on the option account.1.sip_trust_ctrl ? That was the only piece of advice that I could not implant. Regards and thanks again
  9. Phantom calls on Yealink Phones

    Hi, I know this is going to sound weird, but well, it is happening to us. A few days a go, a couple of Yealink phones started to behave strangely. They started to ring, as if there was an incoming call from another extension, and since such extensions do not exist in the domain, they should not happen at all. The calls are not recorded in the call log and they do not show up in the active calls window. If you answer them, there is no audio whatsoever. It is really a problem because during a single working they , there can be from 50 to 100 phantom calls during a single working day. I believe this has nothing to do with the pbx, although the caller ID of the calls appear to be the same as existing extensions in other domains (could be just a coincidence). One of the phones, a T20, stop this weird behavior by stepping it down a couple of firmware versions. The other, a T22, I have yet to find a cure. Has this happen to somebody else? Regards
  10. SPA301 PnP

    Yes. I have tried some 303 with no problem, but this 301 did not play. Do we need a special text file?
  11. SPA301 PnP

    Hi, Is it possible to do PnP with a Cisco SPA301 ? Has anyone already done it? Thanks in advance.
  12. Coma as an invalid character

    Well. My particular error came with the name of a customer. As an example, imagine that my customer was SIEMENS AG, and that by mistake I entered: Siemens, AG (with a coma between the name and the business type (the Aktiengesellschaft, but abbreviated). The name, which was meant to be only one field, became two (one for Siemens and another one for the AG). Once this happened to me, I believe that I will never use a coma as part of a name, but I figured it could be helpful it were not allowed.
  13. Coma as an invalid character

    Hi, I just experienced a problem because I inadvertently used a coma within the name of a user. This provoked a major error during a billing process while reading a CSV. Since by definition a CSV uses a coma to separate fields, a coma should not be used within anything that can come up in a field of a file that can be obtained as an CSV, otherwise, one more field than expected is going to appear (the one created by the coma within a name). So, the improvement would be that the pbx would not allow the use of a coma in any parameter that can be a field of a file that can be obtained as an CSV fie. "invalid character" or something like that should kick back while attempting to save something that has a coma in such a box. Regards
  14. Conference Initiation by an Assistant

    Got it. Thanks!
  15. Conference Initiation by an Assistant

    I would like to try that. Which is that star code? Should the calls to be merged be put in separate park orbits and then the star code would merge them into a conference. That would do the trick.
×