Jump to content
Vodia PBX forum

Dale

Members
  • Content Count

    23
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Dale

  • Rank
    Member
  1. Look here for Asterisk for Beagle Bone: http://www.beaglebone-asterisk.org/
  2. I'm using a Snom One Mini running version 4.5.1.1107 Zeta Perseids (snom ONE mini) In the log I see sequences of errors that look like this: [5] 2013/08/01 08:35:23: HTTP 192.168.90.229:3280: Alert(2, 0) [5] 2013/08/01 08:40:40: HTTP 192.168.90.228:4765: Alert(2, 0) [5] 2013/08/01 08:40:41: HTTP 192.168.90.228:4942: Alert(2, 0) [5] 2013/08/01 08:40:42: HTTP 192.168.90.228:4511: Alert(2, 0) They appear in bursts of 6 or more within a few seconds. What do the errors mean?
  3. I did not think to look at this earlier, but I can see from the Service Providers logs and web site that registration is not really being lost. When I looked at this in detail and when I tried calls while the PBX was reporting being in the 408 state, I found the service provider did not think that the registration had been dropped and incoming calls still completed. So you are right, the problem is not as serious as it originally seemed to be. The system will be going into operation soon and the service provider does send an email whenever a call is attempted that fails because the PBX is not registered, so soon I will see how real the problem is. My fall back plan if calls really are dropped is to try to configure the system without registration, where the service provider sends the calls to my static, public IP. Regarding the 100 Trying message, from watching the logs I notice that I only get the 408 email when the 100 Trying message comes immediately (within the same second or two) after the 200 OK. That is, the 100 Trying has gotten out of sequence. It seems that this event confuses this version of the Snom One code (4.5.1.1107).
  4. Thanks for your suggestion regarding DNS. However, even when I enter the IP address I get the same problem. I really think that this is a bug in the SNOM ONE code. Here is why. Even when the web page for the trunk status says "408 Request timeout..." the registration continues to be valid on the VOIP provider and I can successfully complete incoming calls to the trunk. I think the SNOM ONE code is getting confused by the out of sequence "100 Trying" message and declaring the timeout when, in fact, no timeout has occurred from the VIOP provider's perspective.
  5. Thanks. I was able to make it work by setting up DID names on the accounts and leaving the "route to extension" blank in the trunk configuration.
  6. I changed the timeout to 40 seconds. It actually seemed slightly worse with that value rather than the default 30 seconds. I get, on average, about one timeout per trunk per hour. With two trunks that is 48 emails per day....not very practical to leave the email status change warnings turned on. I'm thinking that perhaps I could get around the problem by configuring my VOIP provider to send INVITES to my public IP and not use registration. To do that I need to get the routing for the different numbers working in the PBX.
  7. Thanks. I'll let it run with a keep-alive time of 40 seconds and see how it goes.
  8. Unfortunately, I'm not using 5.1. I'm using a SNOM ONE MINI running 4.5.1.1107. How do I do it with this release?
  9. I think I understand what you are saying, but, being new to SNOM ONE, I don't know how to implement what you suggest. How, in the SNOM ONE gui, do I create the rules in the PBX that will route to different extensions based on the Request-URI or To-header?
  10. I observe that the REGISTER message sent by the PBX seems to occur every keep alive time. When you say to try "putting 40 there" are you suggesting 40 be tried for the proposed registration duration or the keep alive time? When I change the keep alive time to be 40, I see the REGISTER messages every 40 seconds. But my original observation was that the problem occurs only when the "Trying" message gets out of sequence due to a route change affecting the UDP packets. How would the timeout affect out of sequence packet processing?
  11. Is call recording on the Snom One Mini running version 4.5.1.1107 supposed to work? I seem to get no recordings, but no errors either.
  12. It does matter which trunk is selected because one trunk is for the main number that goes to the receptionist and the other is for the back office that goes to a different station. I can change the account names at Vitelity, but, sorry, I'm still a bit fuzzy regarding exactly what you mean by "giving accounts in the domain additional names that match the numbers being called." As you can see the incoming invite and To: show the number that was called, but how do I get the PBX to select the right trunk? What, exactly, would you recommend I put in which field of the trunk configuration to get the PBX to match the right trunk? That is, what rule can I configure to make this work? If you could give a specific example based on the INVITE message above that would be very helpful. Thanks.
  13. I really cannot afford the upgrade price just to fix a bug. My registration duration is set to one hour, but the keep alive time is set to blank which seems to default to 30 seconds. Which of these do you suggest I change to a longer value? What value do you suggest? Is there a way I can get this fixed for my version? This is really killing my customer.
  14. I have a Vitelity Trunk that I use successfully for inbound and outbound traffic. I set both the proxy and the domain to sip29.vitelity.net in the trunk configuration. My problem is that I actually have two separate inbound trunks form Vitelity that I want to route differently in the PBX...that is not working and I've created a separate topic for that.
  15. I've personally found that one way audio on the trunks can be caused by a router that does not properly handle the layer 7 SIP translations if you are behind a firewall. If you can disable the routers attempt to translate the SIP headers you can configure the Snom One Mini to create and process the headers correctly on the Admin Settings Ports page using the "IP Routing List" configuration line.
×
×
  • Create New...