Jump to content

Vodia PBX

Administrators
  • Posts

    11,069
  • Joined

  • Last visited

Posts posted by Vodia PBX

  1. I don't see how that will stop it from saying 411 for the dial by name. Won't it make that announce it as long as the 411 is entered in the "Dial By Name: Input that triggers name search:" section?

     

    Ehh... You are right.

     

    There is still one possibility. A auto attendant will immediately do to dial by name if you put "start" into the place where you currently have "411". If you use two auto attendants, then the first one can make the annoucement as described above, then redirect the call to the second attendant (which has an unspellable name like "dialbyname") and bingo - we have the perfect annoucement.

  2. Well the PSTN gateway is really a seperate subsystem. Just like you connect an external PSTN gateway. The communication runs only via SIP.

     

    If a CO-line on the PBX gets stuck, then that means that the gateway did not send a BYE. So if you do logging, make sure that you are watching the SIP traffic on the IP address 127.0.0.1.

  3. [3] 2008/03/25 21:02:47: PSTN: Channel 1 going to RING

    [5] 2008/03/25 21:02:51: PSTN: eVAPI_CALLER_ID_DETECTED_EVENT

    [5] 2008/03/25 21:02:51: PSTN: Received on 1 Caller-ID 3256900821

    [5] 2008/03/25 21:02:51: PSTN: Received on 1 Name JACKS DEBORAH

    [3] 2008/03/25 21:02:52: PSTN: Channel 1 going to NO_RING

     

    What surprises me here is that channel 1 obviously receives the caller-ID while in the "RING" state... Is that possible? I thought the caller-ID is sent in the pause between the first and the second ring?

  4. 2.1.6 supports the recording of conferences. You must use a scheduled conference for that. When you create the conference, check the recording flag. Then the conference recording is available for the moderator (the one who created the conference) from the web interface.

    Needless to say, those files can get big. The conference must be deleted manually from the web interface to delete the recording.

  5. STUN works only in < 80 % of the cases, leaving the remaining > 20 % as a support nightmare. We gave up troubleshooting all kinds of one-way audio problems and explicity removed the support for STUN-allocated identities. Our life and the life of our customers became much easier after that. And we saved a lot of money buying all these different DSL and cable routers to find out what the problem was with this and that installation.

     

    Pulver must get a session border controller. That is what practically all SIP service providers are doing.

     

    Or they should start supporting IPv6 addresses (no more NAT the way it was done in IPv4). If you don't have a routable address, don't expect that someone calls you :P . At least not in a reliable way.

  6. Anyone have a clue on this one???

     

    The setting for the dial plan in indeed missing for the IVR node. The IVR node can only call internal numbers that do not require a dial plan.

     

    Feature will be available in the next version.

  7. Would you see any reason why the phone would not find the PBXNSIP server? Maybe there are any settings that can't simply be transferred from one machine to another.

     

    Probably the outbound proxy is not correct any more. My suggestion is to use the same IP address on the new machine as the old machine, this way you can keep the phones untouched.

     

    An alternative would be having a completely automatic plug and play. Then you may have to change option 66 on the DHCP server, and that's it.

  8. We are looking for a way to forward all our technical support calls to a cell phone when needed. The calls come through our main AA and into another queue that the techs login to. We tried having a user login to the queue then forward all the calls from his ext to the cell that didn't work it only forwarded calls that came directly to his ext. It would be great if this could be done from the web page also so if a user is going to work from home he can setup the ACD Calls all to go to his cell phone.

     

    You can redirect the calls from the ACD to an external number, that should be no problem. If you redirect from a ACD also to an extension, then the cell phone redirection rules apply again and the call will fork to the cell phone as well.

  9. I tried to leave the Trunk DID blank, but the caller id when receiving a call from my voicemail came up as unknown again. So is there something I can do about this problem?

     

    Do you remember what you had in that field before? ...

  10. We got rid of these "$f $i $x $y $z" strings in the trunk. I think the new name is now "Trunk DID". Normally, it is okay to just leave it empty, the PBX then will automatically fill something useful in.

     

    It is debatable if that was a smart move. On the one hand, it caused a lot of support and problems with too much programmablility for nothing. On the other hand we have an upgrade issue, and now we need to explain everyone B) .

  11. That means that the PBX received a new media stream on the RTP port. It is allowed according to the IETF, but raises questions. A legal case could be that the other side uses an external music on hold server and sends music on hold out of the original media context.

     

    "Illegal" cases would be that there are really several audio streams running on the same RTP port. Do you have enough RTP ports open on the firewall? Or maybe there is a device that just did not stop sending audio streams?

  12. When a call redirects to my cell phone, it shows the original caller ID which is good.

     

    Congrats! You are a lucky guy. Most of the PSTN services do not allow this. What PSTN termination are you using?

     

    Is there any way to set a prefix to the caller ID, so I know the call is coming from the pbx rather than someone dialing my cell directly.

     

    No, at the moment not.....

×
×
  • Create New...