Jump to content
Vodia PBX forum
pbx support

Epsilon Geminids

Recommended Posts

Hello,

 

The latest 4.5 snomONE version(Epsilon Geminids) has been released. This version is built on top of the Delta Aurigids.

The release notes and the download links can be found here - Epsilon Geminids

 

Note: This is snom ONE release (i.e., not applicable to pbxnsip customers).

 

Also, after this version, 4.5 will become a bugfix only branch. The new features will be added to the version 5.

 

Thank you for the continued support.

The snomONE team!

Share this post


Link to post
Share on other sites

Does this release announcement mean that the 4.5 snomONE version(Epsilon Geminids) is ready for Production Use?

 

We currently are at 2011-4.2.0.3981 (Linux) and there seems to be a disconnect between what is listed as Production Ready (4.3) and what is delivered when you click on the 4.3 Download for Centos-64 (2011-4.2.0.3981). reference: http://wiki.snomone.com/index.php?title=Upgrades_(Release_4.3)

 

There is also no indication what the state of the snonONE 4.5 is on the Download pages, beyond several Alpha/Beta/etc releases and what they have added/fixed. reference: http://wiki.snomone.com/index.php?title=Upgrades_(Release_4.5)

 

A statement of Production Readiness would be very helpful for the real world community.

 

Jim

Share this post


Link to post
Share on other sites

The versions that we release to the wiki are generally production ready, i.e, ran on the internal lab & production networks and some beta customers etc. Note that this may not exercise every test case out in the real world, but covers most cases.

 

The upgrades, to most part, are smooth. But couple of upgrades have caused some heartburn. One such case is switching from 'pbxnsip' versions to 'snomONE' versions. The other case could be the trunk upgrades that we introduced on 4.5.

Share this post


Link to post
Share on other sites

The versions that we release to the wiki are generally production ready, i.e, ran on the internal lab & production networks and some beta customers etc. Note that this may not exercise every test case out in the real world, but covers most cases.

 

The upgrades, to most part, are smooth. But couple of upgrades have caused some heartburn. One such case is switching from 'pbxnsip' versions to 'snomONE' versions. The other case could be the trunk upgrades that we introduced on 4.5.

 

Great work thanks!

 

1- I have reg_system.htm that contain WAN PORT and SERVER DNS 1 and 2 + NTP server. Can you please point me to the documentation in that regards.

 

2- I have note that dom_accounts.htm display several information that are unchecked, it seams to be looking at something since the download is rolling... and finally the display become clean... Is this a normal behavior?

 

3- dom_accounts.htm administrator are displayed with "#" instead of " * "

 

4- reg_appear.htm ... Logo Link: do not seems to be working... path is html/img/Background2.jpg that use to work on previous version and not on this one, but the file is present on the directory.

Share this post


Link to post
Share on other sites

1- I have reg_system.htm that contain WAN PORT and SERVER DNS 1 and 2 + NTP server.  Can you please point me to the documentation in that regards.

Did not understand the question here.

 

2- I have note that dom_accounts.htm display several information that are unchecked, it seams to be looking at something since the download is rolling...  and finally the display become clean...  Is this a normal behavior?

That is normal if you have a lot of accounts or slow connection to the server from wherever you are accessing from. Basically, the server sends everything to the browser and the javascript will display or hide based on what is selected.

 

3- dom_accounts.htm administrator are displayed with "#" instead of  " [size="5"]*[/size] "

Yes, now you can have both system and domain administrator options.

 

4- reg_appear.htm ...  [font=Verdana, Helv, sans-serif][size=2]Logo Link: do not seems to be working...  path is html/img/Background2.jpg that use to work on previous version and not on this one, but the file is present on the directory.[/size][/font]

Please take a look at http://wiki.snomone.com/index.php?title=OEM

Share this post


Link to post
Share on other sites

1- I have reg_system.htm that contain WAN PORT and SERVER DNS 1 and 2 + NTP server.  Can you please point me to the documentation in that regards.

Did not understand the question here.

 

When you log as admin, you can access "reg_system.htm" setting page. This page contain settings that I cannot find documentation about

 

 

WAN PORT

SERVER DNS 1

SERVER DNS 2

NTP server

 

I am looking for documentation that explain what it used for. This is not new but I cannot find manual on this...

Share this post


Link to post
Share on other sites

You should be seeing this page through any of the navigation links on a default installation. That's why there is no documentation on that.

 

You would probably see this only if you directly type reg_system.htm on the address bar or have modified the HTML page templates. We have/had that page for the CS410 appliance only.

Share this post


Link to post
Share on other sites

Hi,

 

I upgraded from 4.5.1075 to this version 4.5.1090, since then my outgoing calls work, but no incoming call work!

I'm using 2 different trunk from outgoing and incoming.

 

Downgraded back to 4.5.1075 and everything is working again.

 

What is the problem? I cannot find anything wrong!

 

My provider for incoming calls give me those logs:

Our call capture shows that we are getting a 404 no-route-at-dest error

message coming from your PBX system

 

Hope this help to resolve my problem...

 

Thanks,

Joel

Share this post


Link to post
Share on other sites

Please provide us with the screen shots of trunk and SIP log of a failed call. Generally 4.5.0.1075 to 4.5.0.1090 should be a smooth upgrade. Only thing that pops out from the release notes is - "P-Charging vector: this will be set only if the older version had something set for that field."

Share this post


Link to post
Share on other sites

Please provide us with the screen shots of trunk and SIP log of a failed call. Generally 4.5.0.1075 to 4.5.0.1090 should be a smooth upgrade. Only thing that pops out from the release notes is - "P-Charging vector: this will be set only if the older version had something set for that field."

 

To provide the SIP logs, I will have to return back to 4.5.0.1090 to redo the test, because now I'm back to 4.5.0.1075 so we can use the system.

 

But meanwhile I can get you the screenshots of the truck configuration as 4.5.0.1075. Do you need those for 4.5.0.1090?

 

How can I check the P-Charging vector? Because I running this system and upgraded few times in the run...

Share this post


Link to post
Share on other sites

You can provide us with the SIP logs from .1075 and the screen shots from the same.

 

Under the Trunk->Remote Party/Privacy Indication: Custom Headers: P-Charging-Vector:.

 

In .1090, we are forcing it to "Don't user header" if it was not explicitly set on the previous versions.

In .1075, we always send it even if it was not explicitly set on the previous versions.

Share this post


Link to post
Share on other sites

You can provide us with the SIP logs from .1075 and the screen shots from the same.

 

Under the Trunk->Remote Party/Privacy Indication: Custom Headers: P-Charging-Vector:.

 

In .1090, we are forcing it to "Don't user header" if it was not explicitly set on the previous versions.

In .1075, we always send it even if it was not explicitly set on the previous versions.

Here is my trunk configuration, "Remote Party/Privacy Indication" is set to "RFC3325 (P-Asserted-Identity)" and not "Custom Headers", Should I change it to "Customs Headers" and change my "P-Charging-vector" which is "Use ICID value" to "Don't use header"?

 

Under "Customs headers" here are all the settings I have:

 

Header Value

Request-URI Let the system decide (default)

From: Base on incoming call

To: Let the system decide (default)

P-Asserted-Identity: Base on trunk account info

P-Preferred-Identity: Don't use header

Remote-Party-ID: Don't use header

P-Charging-Vector: Use ICID value

Privacy Indication: RFC3325

 

Should I change anything under "Custom headers"?

 

OR should I not use "Custom headers" and change "Remote Party/Privacy Indication" from "RFC3325 (P-Asserted-Identity)" to something else beside "Custom Headers"?

Other choices I got are: "RFC3325 (P-Preferred-Identity)", "No Indication", "Remote-Party-ID" or "RFC3325, but don't hide".

 

Thank you for all the help...

Share this post


Link to post
Share on other sites

Based on the explanation, PBX is sending P-Charging vector under .1075 version and the trunk provider seems to like it. But in .1090, as I mentioned earlier, we do not send that header, unless you explicitly set it.

 

So, before switching to .1090, please make a call and capture the SIP trace (basically, the INVITE that is going out to the trunk provider from snomONE). This will help you (and us) to see what is really going out to the provider.

Then switch to .1090 & change the RFC3325 (P-Asserted-Identity) to Custom Headers & set P-Charging-Vector to Use ICID value & set some value under Charging Vector:.

Share this post


Link to post
Share on other sites

Based on the explanation, PBX is sending P-Charging vector under .1075 version and the trunk provider seems to like it. But in .1090, as I mentioned earlier, we do not send that header, unless you explicitly set it.

 

So, before switching to .1090, please make a call and capture the SIP trace (basically, the INVITE that is going out to the trunk provider from snomONE). This will help you (and us) to see what is really going out to the provider.

Then switch to .1090 & change the RFC3325 (P-Asserted-Identity) to Custom Headers & set P-Charging-Vector to Use ICID value & set some value under Charging Vector:.

 

On our side it is not confluent so fare. VOIP trunk are no longer working....

 

 

 

Share this post


Link to post
Share on other sites

Based on the explanation, PBX is sending P-Charging vector under .1075 version and the trunk provider seems to like it. But in .1090, as I mentioned earlier, we do not send that header, unless you explicitly set it.

 

So, before switching to .1090, please make a call and capture the SIP trace (basically, the INVITE that is going out to the trunk provider from snomONE). This will help you (and us) to see what is really going out to the provider.

Then switch to .1090 & change the RFC3325 (P-Asserted-Identity) to Custom Headers & set P-Charging-Vector to Use ICID value & set some value under Charging Vector:.

Ok the problem is when I receive call, so for this trunk I did a incoming call and I tcpdump everything on port 5060.

This is done with version .1075, where do you want the tcpdump file?

Share this post


Link to post
Share on other sites

For me, both 4.5.0.1075 and 4.5.0.1090 trunks are not working...

 

Sip Trunk are registering and working fine with version 4.3.0.5021 and giving me 200OK Status. With both version 4.5.0.1075 and 4.5.0.1090 they toggle between 200 to 408 and when at 200, giving me a busy signal on SNOM870.

 

SIP gateway (Mediatrix 1204) have not been tested so fare. SIP Registration must be working before.

Share this post


Link to post
Share on other sites

Also, after this version, 4.5 will become a bugfix only branch. The new features will be added to the version 5.

 

I read that fax-to-email support will be available in version 5.

Is there any timeframe when we can expect version 5 ?

Share this post


Link to post
Share on other sites

I read that fax-to-email support will be available in version 5.

Is there any timeframe when we can expect version 5 ?

 

 

Where did you read that at?

Share this post


Link to post
Share on other sites

As much as V5 is interesting to all of us which use SnomOne already, the new licensing policy raise the question "What's about the existing licenses?" Do they lose in value? What the user will get for their snomone yellow / snomone blue? It seems that the old licensing policy was much better for the customer as the blue included unlimited extensions, full feature set, multi tenant up to 5 companies. Although the a-la-carte seems to come without pricing-information for now, I guess that some customers are really missing the delightful "flatrate" (unlimited usage) of non-extension accounts like ACD'S, hunt groups, IVR's, Service-Flags(extremely important!) and others. It makes fun, to present the customers the advantage of an IP-PBX while they have to pay only for the extensions. Building complex scenarios doesn't result in worry about licensing issues. Especially for a hosted pbx provider the new licensing policy seems to be a drop of bitterness in a very welcome V5 with the eagerly awaited Fax integration.

Share this post


Link to post
Share on other sites

Red Alert!

 

I agree fully with Hummig KG. The current licensing model is what SnomOne stand out among all the various pbx. The Free / Yellow / Blue model makes it very attractive for the SMB market with Snom phones.

 

If Snom is going to a license model like this, 3CX will look much more attractive.

 

Please do not mess with the licensing model.

Share this post


Link to post
Share on other sites

Red Alert!

 

I agree fully with Hummig KG. The current licensing model is what SnomOne stand out among all the various pbx. The Free / Yellow / Blue model makes it very attractive for the SMB market with Snom phones.

 

If Snom is going to a license model like this, 3CX will look much more attractive.

 

Please do not mess with the licensing model.

 

I agree!

Share this post


Link to post
Share on other sites

×