Jump to content

colink

Members
 View Profile  See their activity

  • Posts

    26

  • Joined

  • Last visited

 Content Type 

Posts posted by colink

  1. 408 error

    in Trunk Setup

    Posted

    Just upgraded a customers Snomone to the latest version as it was having issues and on restart it gets these same 408 errors.

    So that's two customers now who are having these 408 issues and trunks refusing to registers.

     

    First customer is using a BT line and a SIP account for VoipUnlimited

    Second customers is using a Spitfire Line and SIP account from Spitfire.

    both are using totally different DNS servers.

     

    this means ive got customers with out phones for days on end and is causing lots and lots of issues.

     

    All fingers are being pointed at it being a fault with the PBX software.

     

    what are we to do ?

     

    Cheers

    Colin.

  4. 408 error

    in Trunk Setup

    Posted

    Have a customer who is getting lots of 408 errors on their trunk.

    i have other customers on the same SIP provider who don't seem to have the same errors.

     

    Version: 2011-4.2.1.4025 (Linux)

    Created on: Jun 27 2011 12:40:10

    License Status: snom ONE free

    License Duration: Permanent

    Additional license information: Extensions: 5/10 Accounts: 10/30 Upgrade: 01 01 2013

    Working Directory: /usr/local/snomONE

    MAC Addresses: 001CC0E0959E

    Calls: 0/0 (CDR: 33/32/33) 0/0 Calls

    SIP packet statistics: Tx: 81 Rx: 59

    Emails: Successful sent: 0 Unsuccessful attempts: 0

    Available file system space: 92%

    Uptime: 2011/7/28 15:01:17 (uptime: 0 days 00:06:26) (8193 9847744-0) WAV cache: 0

    Number of HTTP sessions: Sessions: PAC=0, HTTP=1; Threads: SIP=0, HTTP=2

     

    the error i get is

    [2] 2011/07/28 14:55:23: Trunk status Voip Unlimited (2) changed to "408 Request Timeout" (Registration failed, retry after 60 seconds)

     

    Sometime this rights itself but today this has been going on for some hours.

     

    Any advice ?

  6. Upgrade from PBXnSIP to Snome one and hardware migration

    in MacOS related topics

    Posted

    Hi Support.

     

    we have an issue.

    When we select to back up the configuration from the PBXnSIP.

    it produces a tar file of 0kbs.

     

    on the other systems where i tried the same process the file is always 500-600kbs.

     

    so it seems we cannot take that path.

     

    is it ok to upgrade the PBXnSIP in place to SnomONE ?

    its currently running PBXnSIP 3.4.0.3201

    would we have to upgrade in stages or could we just go straight to the latest release ?

     

    Cheers

    C.

  7. Upgrade from PBXnSIP to Snome one and hardware migration

    in MacOS related topics

    Posted

    Hi All.

     

    Assisting a customer who has an old PBXnSIP server and they are looking to upgrade to SnomOne Blue.

    They already have thier Snom license and are all ready to migrate.

     

    Current server is

    Mac Mini

    OSX 10.5.8

    Intel C2D

    Running PBXnSIP 3.4.0.3201

    20 Extensions.

     

    New server is

    Mac Mini

    OSX 10.5.8

    Intel C2D (so the hardware is identical)

     

    Idealy what the customer would like us to do is...

    Keep the current server as is

    Setup the new Server and Install SnomOne.

    transfer all accounts/Voice mail/Hunt groups etc from odl to new server.

    switch off old and switch on new.

     

    keeping the old server as backup in case the migration is not smooth.

     

    are there any written instructions for migrating servers ?

    Would i have to upgrade the old server first ?

    any advice ?

     

    Cheers

    Colin.

  10. Incomming calls stop

    in Trunk Setup

    Posted

    We are looking at an issue that is caused by the buggy/slow responding DNS server. How stable is your DNS server?

     

    There is another post related to this issue.

    http://forum.snomone.com/index.php?/topic/4669-trunk-re-registration-problems/page__pid__20522#entry20522

     

    We are using the Google DNS servers

    8.8.8.8 and 8.8.4.4

     

    i can change these to the SIP providers in house DNS servers to see if that make a differance.

     

    Cheers

    C.

  13. Incomming calls stop

    in Trunk Setup

    Posted

    Happened again this morning.

    Trunk shows as registered and out going calls are fine

    Incoming calls fail until such time as i manually reset the trunk.

     

    SIP provider (as i have already posted) are pointing the finger directly at Snom and suggesting its your PBX that is the culprit.

     

    any chance of a response to my comments above ?

  15. Incomming calls stop

    in Trunk Setup

    Posted

    Hi.

     

    this happened this morning.

    incomming calls stopped and when i tried to call the system there where no INVITE requests reaching the log.

     

    when i disabled and then re-enabled the trunk it all started working and i could see

    [5] 2011/05/24 09:08:00: INVITE Response 487 Request Terminated: Terminate f7c48a14@pbx

    in the logs.

     

    However after much dispute with our sip provider they final admitted this

     

    Just realised we are in the middle of inter-op with Snom so we are not 100% on this yet, particular issues have already been logged with us confirming a Snom registration error and there should be a patch out for this.

     

    So its seem out SIP provider and SNOM PBX are not compatible.

    i wasted so much time and had so much ill will from my customers over this issue its unreal.

     

    Do you know of this patch to which they refer ?

    when are we likely to see it.

  17. 400 Bad Request (Registration failed, retry after 60 seconds)

    in Trunk Setup

    Posted

    Spoke too soon again.... now is ok and reading

     

    REGISTER sip:sip.voip-unlimited.net SIP/2.0

    Via: SIP/2.0/UDP 192.168.35.10:5060;branch=z9hG4bK-b97201c57103086690fdd46c074683e3;rport

    From: "02033273130" <sip:02033273130@sip.voip-unlimited.net>;tag=1590641134

    To: "02033273130" <sip:02033273130@sip.voip-unlimited.net>

    Call-ID: 5ibt71vq@pbx

    CSeq: 356939513 REGISTER

    Max-Forwards: 70

    Contact: <sip:02033273130@192.168.35.10:5060;transport=udp;line=c81e728d>;+sip.instance="<urn:uuid:7f44dbfa-aa69-4afd-a7ec-f227e8c8cd33>"

    User-Agent: snom-PBX/4.2.0.3950

    Supported: outbound

    Authorization: Digest realm="sip.voip-unlimited.net",nonce="4dd68bb70000310ce694f0fb2627ca7e168bfaa46a11fc44",response="014c275dce15d28c8febbdb4c7cb6b5c",username="02033273130",uri="sip:sip.voip-unlimited.net",algorithm=MD5

    Expires: 60

    Content-Length: 0

  19. 400 Bad Request (Registration failed, retry after 60 seconds)

    in Trunk Setup

    Posted

    Can anyone tell me what this error means ?

     

    Customer has had Snomone and SIP account for some while.

    But today SIP went down and he was getting error 400 Bad Request (Registration failed, retry after 60 seconds).

     

    Whilst i was looking into it SIP registration went back to normal.

     

    Just trying to figure out what the error means and where the problem might be.

     

    customer is using SnomOne 2011-4.2.0.3950 (Linux)

     

    Cheers

    Colin.

  21. Incomming calls stop

    in Trunk Setup

    Posted

    Hi.

     

    we have two customers that are both having the same issue.

    setup (in both cases)

     

    Snom 320 Handsets

    SnomOne PBX (version 2011-4.2.0.3981)

    Draytek Vigor 2820 (FW 3.3.4.1_232201)

    DSL and SIP from Voip Unlimited

     

    every so often incomming calls stop and when you dial the external number it tells you there is a fault with the number.

    checking the PBX everything seems to be ok and working.

    the trunk is shown as registered and online.

    Out going calls can still be made.

    the only way to resolve it is to disable and then re-enable the trunk.

    this resolves the issue and calls start incoming again.

     

    very keen to get this one resolved.

  22. Constant hacking

    in Security

    Posted

    1) the bind to mac address does not isolate that extension to that mac address. It is just used for PnP. The field above it IP address does do this so if extension 102 comes from a static IP address then you can enter it here and ONLY that IP address will be able to register. How they initially cracked the account is anyone's guess. If they were trying to guess the password very slowly then I don't think the access list would catch it if the number of unsuccessful attempts did not hit the threshold. Since it is happening only on one extension it sounds like they kept trying to guess that extension. So you don't have any remote phones on the system and they are all only local? Is their any PnP files in the generated directory for 102? I didn't see that answer. If they had the http password for extension 102 then they would be able to do Wan based PnP without the mac address being correct since they would be able to login.

     

    Hi.

     

    they did no use the PNP as there was no folder 102 in the generated folder.

    All of the phones are internal and static IP so i will make that change now.

     

    I will also check HTTP access to make sure them password are complex enough.

     

    Cheers

    Colin.

  24. Constant hacking

    in Security

    Posted

    Cheers for your help on this matter.

     

    im looking in the CDRE folder and have found an entry relating to one of the calls.

    I not sure how to read the file or interprate it correctly.

     

    in notepad the file reads

     

    TLVB c

    1298257126.17 cid e80568532856314b ct d d 1 e 1298257218.252 f %"Linda 102" <sip:102@pbx.company.com> i e80568532856314b o I p udp:188.161.235.136:6960 r #<sip:0038733960085@pbx.company.com> s 1298257119.298 t #<sip:0038733960085@pbx.company.com> u 3 vq ÍVQSessionReport: CallTerm

    LocalMetrics:

    Timestamps:START=2011-02-21T02:58:46Z STOP=2011-02-21T03:00:18Z

    CallID:e80568532856314b

    FromID:<sip:102@91.151.14.189>;tag=8e11e100

    ToID:<sip:0038733960085@91.151.14.189>;tag=131596bb83

    SessionDesc:PT=8 PD=pcma SR=8000 FD=20 FO=160 FPP=1 PPS=50 PLC=3

    LocalAddr:IP=192.168.10.3 PORT=57598 SSRC=0xfc0e0e8a

    RemoteAddr:IP=0.0.0.0 PORT=0 SSRC=0x

    x-UserAgent:snom-PBX/2011-4.2.0.3981

    x-SIPterm:SDC=OK SDD=214 SDR=OR

    y extcall

     

    I suppose the suspect IP in there is 188.161.235.136

    Which is from Palestinian

     

    I can black list this IP address.

    But this doesn't address the initial issue with how they where able to register the extension in the first instance.

  25. Constant hacking

    in Security

    Posted

    So what do you mean by "hacked"? Someone making unauthorized phone calls from this extension?

     

    Ideas why:

     

    • The real password leaked out. For example, if the attacket has access to the file system, all security is rendered useless.
    • If the provisioning got hacked, you would see the generated files for the extension in the file system (the "generated" directory)
    • You can see in the CDR the IP address where the call was initiated from. That might help you find the source of the problem. If neccessary, you can blacklist that address or the whole subnet.

     

     

    Yes as in someone is making calls from that extension.

    The real password leaked out

    I'm as confident as i can be that the passwords are secure.

    The OS is only assessable via VPN and has a fairly robust password of its own.

    I change the passwords each time the extension is hacked and it doesn't seem to make a vast difference.

     

    If the provisioning got hacked, you would see the generated files for the extension in the file system (the "generated" directory

    As i never set up the system i cant say with any certainty that a secure and complex password was used and/or that provisiong was used. I will set an appropriate password now.

     

    When i look in the generated folder i do see a folder named "40"

    The user of the extension 102 has a snom which end with the IP x.x.x.40

    is this a match ?

     

    is there anything i can read within that folder that would indicate if its moody or not ?

    FYI the date for file creation in that folder are all very old 08/10/2010

     

    If provisioning was hacked would that override the limit registration to MAC address of the handset ?

     

    Cheers

    Colin.

×
×
  • Create New...