Jump to content
Vodia PBX forum

cwernstedt

Members
  • Content Count

    87
  • Joined

  • Last visited

Community Reputation

0 Neutral

About cwernstedt

  • Rank
    Advanced Member

Recent Profile Visitors

5,008 profile views
  1. How could that happen? Bug? Server wasn’t touched except for a reboot.
  2. After reboot, the call history shows all calls as having been made on 12/31/1969 7:00:00 PM . Version is 63.0.1 (Debian64) . Any idea of what happened here and how it can be prevented in the future? (Fortunately this time, the log isn't needed.)
  3. DNSmadeEasy provides a user name, and two keys: API Key and Secret Key . From these three, what should go into the two fields provided on the pbx (user name and password) ? [Solved on my own: Should be API Key and Secret Key for user name and password ]
  4. To clarify, this is the situation, and maybe there is a misunderstanding: Twilio utilizes, for example, the below IP-addresses and with 3.122.181.0/24 network for Media being put into use on Monday next week. Is it perhaps the case that only the signalling IP-addresses need to be configured in the Vodia trunk settings, and that media will flow regardless of if the originating Media IP-addresses match trunk settings? If so, Twilio users should be fine...If not, there's a lot of trouble coming. Signalling IPs: 35.156.191.128/30 which translates to: 35.156.191.128 35.156.191.129 35.156.191.130 35.156.191.131 Ports: 5060 (UDP/TCP), 5061 (TLS) Media IPs: 35.156.191.128/25 3.122.181.0/24 Port Range: 10,000 to 20,000 (UDP)
  5. I have this problem now with Twilio as they just added a class C network , and things will stop working next week unless I add it. (Trunk doesn't get properly identified on incoming calls without the IP-addresses specified.)
  6. Ok. Where do I configure these things in this version? Ideally I would like to prefix +423 to all numbers lacking a 00 prefix (local numbers) and replace 00 prefixes with + for international numbers. So 2371336 would turn into +423 2371336 and 0013343456666 would turn into +1 3343456666 . (Incoming calls only)
  7. Hi, Well, it's the inbound (not dialed) that I'm looking to change. In other words, the number that is presented on calees' phones and in logs etc. The trunk provider presents local numbers without the correct international prefix, which makes it difficult to process these calls correctly.
  8. One of our SIP-trunk providers isn't particularly good about how they present the CIDs on inbound calls. Is there a way to rewrite these according to some rules, for example replacing 001 with +1 , or adding a country code to local numbers. Note for clarity: I'm talking about how numbers are presented in the From field in CDRs, logs, etc.
  9. Can you take a look at the packet captures zipped and attached to the earlier message? ( )
  10. Initiate call back after hangup is "No" for the called extension in the tests and the calls are not made from a cellphone or POTS-phone, but from a registered extension.
  11. I assume it's the mailbox, since there is no agent group configured, but mailbox doesn't explicitly offer callback as an option, and "offer camp on" is disabled. The sequence of events from the point of view of the caller seems to be like this: 1) caller places a call to the extension 2) Ring tones are generated . 3) "Something" (probably voicemail) at the PBX picks up and it immediately (before even playing a greeting) for unknown reasons adds the caller to the callback list. 4) The caller hangs up. From the callee's point of view, the phone rings, but when picking up, it's the PBX offering various options. Not sure what it is. (See the file rec_115_13.wav in the attached ZIP. I'm also attaching PCAP files captured on the PBX.) When this happens there is always two calls registered in the log, starting at the same time. A big question is if the callback list option can somehow be triggered before the mailbox has kicked in . It almost appears to be the case, because the mailbox really shouldn't have come into play here. (The callee account had a live registration generated by Counterpath, and the callee picked up well before the call should have landed in voicemail.) weird call with stretto.zip
  12. Looks like I'm closer to pinning down what's going on... Seems like my test call generator, somehow, sometimes, manages to make some noise that is misinterpreted as the starcode that gets the call added to the callback list. I wonder, what are the conditions for this feature to be activated by a caller? Can it, for example, happen only when the caller reaches the mailbox, or is there some other situation when it can happen, such as when ringtones are being generated before the callee or voice mail has picked up? Can the feature be turned off?
  13. The setup is now the standard one where the client and the registration server alternate registrations, but potentially with some brief overlaps (option 0 below). Not sure this is what is causing problems since Vodia supports multiple registrations for the same account, and since most of the time, the handover appears to work fine. In any case, seems like you are suggesting that 2 would be more stable? /CW 0: Standard: Your VoIP service provider supports multiple registrations. In this mode, there may be short overlaps of registration where both the Push server and the Bria client are registered to the SIP server. 1: Single Device Emulation: Your VoIP service provider does not support multiple registrations. Bria and the Bria Push server must unregister before the other one can register. 2: Continuous: Your VoIP service provider support multiple registrations. The Bria Push server is always connected to the SIP server. Bria is only connected to the SIP server when Bria is in the foreground. When Bria is in the foreground, Bria ignores push notifications so you do not receive duplicates. 3: Single Device Takeover: Your VoIP service provider does not support multiple registrations. Bria and the Bria Push server take over registrations from each other without unregistering first.
  14. Thanks! Upgraded with no issues, and could restore PRACK after that. A remaining problem with Counterpath and its push/handover mechanism is that some calls behave very strange. Every now and then this happens: The caller lands in voice mail, but the Bria Stretto user will hear the phone ring. If picking up, the callee will hear nothing OR will hear what seems to be the Virtual Private Assistant. The PBX registers these calls as two calls in the call history. I wonder what can be done to troubleshoot this. No trunks are involved. This is just between registerred SIP-clients and the PBX.
  15. Ok. Excellent. I have hesitated to upgrade because I don't want to break anything that is working, but maybe 63 is a safe one? Rolling back seems difficult due to the password encryption.
×
×
  • Create New...