Jump to content

Joel

Members
  • Posts

    14
  • Joined

  • Last visited

Posts posted by Joel

  1. Hi,

     

    I'm running Snom One Free 4.5.0.1090 and before upgrading to 4.5.1.1107 I want to make sure all my features will still work on my system, like the call recording.

     

    I'm asking because this was in the release notes:

     

    "The license module now requires that the license is bound to a MAC address. This implies that the snom ONE free license does not work with version 4 and more. snom ONE can now only be evaluated on version 5."

     

    So basically what this mean? I don't what to go with version 5.0, because some features aren't free anymore and I need them.

    When I will need to use fax, I guess I will not havr choice to upgrade to v5, but for now I stick to v4.5.

     

    So I just want to make sure I won't have any trouble with features using v4.5.1.1107 over 4.5.0.1090...

     

    Thank you for all the clarifying answers...

     

    Regards,

    Joel

  2. 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?

  3. 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...

  4. 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...

  5. 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

  6. Ok I will try that, since I ping 173.194.77.109, but if I ping smtp.gmail.com it goes to 216.239.44.95, which timeout!

    Putting the IP directly instead of 173.194.77.109 it worked! Yeah!

    But when this will work again with smtp.gmail.com? I will need to enable IPv6 on all host computer (Linux/Windows) and on my router (TomatoUSB Shibby)?

     

    Look here the report http://www.mxtoolbox.com/SuperTool.aspx?action=mx%3asmtp.gmail.com

  7. What about just putting the IPv4 address there instead of the DNS name? That's a kind of workaround until IPv6 is available; maybe google wants to push for IPv6 and publishes the records on purpose...

     

    Ok I will try that, since I ping 173.194.77.109, but if I ping smtp.gmail.com it goes to 216.239.44.95, which timeout!

  8. I am having the same issue with two of my SOHO's, the common issue between them is the ASUS router with Tomato USB. The SOHO is getting the google IP but cant reach it. I think the router is having an IPv6 issue. If I manually assign the IP of smtp.gmail.com (173.194.77.109) it works, at least until the IP moves :)

     

    Is there a way to only request the IPV4 address through DNS until I can get the IT person that installed the routers out there?

     

    Thanks guys!

    I have tomato USB shibby... and my IPv6 option is Disable... Should I try to Enable it? If yes to what option?

    post-21288-0-62488400-1339498975_thumb.png

  9. Okay, just rebooted and still the same issuie. In the folder "/usr/local/snomONE/spool" I have a backlog of all email stuck in here....

     

    What should I do to fix the problem?

    I'm looking (CentOS6.2) under this folder /etc/sysconfig/network-script, and the file ifcfg-eth0 have this line:

    IPV6INIT=no

     

    Should it be set to "yes"?

  10. That is exactly what I suspected...

    I have to check, usually I don't use IPv6, but since I re-installed this server few months ago, I may have configured IPv6...

    I'm rebooting now to see if it will change, since it is now over 24hours since... Hopefully the DNS cache is expired. But before the reboot, was still not working.

     

     

    Thanks,

    Joel

     

    Okay, just rebooted and still the same issuie. In the folder "/usr/local/snomONE/spool" I have a backlog of all email stuck in here....

     

    What should I do to fix the problem?

  11. LoL, seems you are a "victim" of the IPv6 day (June 6, 2012). Did you have IPv6 connectivity on that server? Hopefully the DNS cache entry expired already, and everything goes back to good old IPv4 times...

    That is exactly what I suspected...

    I have to check, usually I don't use IPv6, but since I re-installed this server few months ago, I may have configured IPv6...

    I'm rebooting now to see if it will change, since it is now over 24hours since... Hopefully the DNS cache is expired. But before the reboot, was still not working.

     

     

    Call call limit reached message is stupid, you have zero calls. We probably should just show the message when there are more than zero calls.

    Thanks,

    Joel

  12. Hi,

     

    Since June 6th, 2012. Sending email using gmail is not working anymore! Was working before this day... So anyone had the same issue?

     

    Did gmail change something? Here is my log file:

     

    [1] 2012/06/06 19:34:52: Starting up version 4.5.0.1075 Delta Aurigids

    [1] 2012/06/06 19:34:52: Adding DNS server 192.168.1.1 to the dns server list

    [3] 2012/06/06 19:34:53: Call limit reached. Call ports 0, g729 0

    [1] 2012/06/06 19:34:53: Working Directory is /usr/local/snomONE

    [5] 2012/06/06 19:34:54: Starting threads

    [5] 2012/06/06 19:34:54: Set scheduling priority to 1

    [5] 2012/06/06 19:34:54: Set process affinity to 0

    [2] 2012/06/06 19:34:54: Trunk status 1 (2) changed to "200 OK" (Refresh interval 1800 seconds)

    [2] 2012/06/06 19:34:54: Trunk status 2 (1) changed to "200 OK" (Refresh interval 150 seconds)

    [3] 2012/06/06 19:34:55: Could not connect to [2001:4860:800a::10]:465

    [1] 2012/06/06 19:34:55: Could not send via TCP: 52 bytes to [2001:4860:800a::10], invalid socket

    [5] 2012/06/06 19:35:07: Table cdrt: Finished reading 426 rows

    [5] 2012/06/06 19:35:08: Table cdre: Finished reading 100 rows

    [5] 2012/06/06 19:35:11: Table cdri: Finished reading 432 rows

    [5] 2012/06/06 19:35:11: Table adrbook: Finished reading 1 rows

    [5] 2012/06/06 19:35:11: Table outbounds: Finished reading 0 rows

    [5] 2012/06/06 19:36:55: SMTP: Timeout

    [3] 2012/06/06 19:37:00: Could not connect to [2001:4860:800a::10]:465

    [1] 2012/06/06 19:37:00: Could not send via TCP: 52 bytes to [2001:4860:800a::10], invalid socket

     

    Also, what mean this msg: "Call limit reached..." in the beginning of the logs? Is there a config to check? I do record all communication, and my voicemail is limited to 25 voice message.

    But it looks like even if there is no voicemail on the system, when I have too much recording on the system I will tell that the voicemail is full.

    I have to manually erase the recordings and reboot the system to have it work again! Should not be linked (Voicemail and recordings)?

     

    Thanks,

    Joel

×
×
  • Create New...