Leonardo srl Posted April 12, 2012 Report Share Posted April 12, 2012 we have been testing SnomOne for 2 weeks now, and we were almost thinking about buying the blue one for a company we work for; but in the last days there were some unexpected things which raised up a few doubts; hoping they will disappear soon, as the product is very fine from the administration point of view; the biggest problem we have came out today; for 2 weeks the registration of a sip-trunk worked perfectly; today it is always giving "408 request timeout"; the situation is the following: > the server is Windows 2008 English 64bit > the snomone software is the actual one at 64bit > we did not change anything on the configuration of SnomOne, but unexpectedly it started giving problems today > if we configure the same sip-account on a snom phone 821 it works great (so it is not a sip-provider problem) > if we configure the same sip-account on a softphone on the same server it works great (so it is not a firewall, port or any other problem regarding the server itself) > another sip-trunk on the snom-one is still working fine (it's another provider) and says 200 OK registered activating the log on the most detailled way, it says just the following of course: - [server-ip] contains the real ip of the server - [trunk-account] contains the real account user of the sip-provider  2012/04/12 21:31:26: SIP Tr udp:184.108.40.206:5060: REGISTER sip:voip.eutelia.it SIP/2.0 Via: SIP/2.0/UDP [server-ip]:5060;branch=z9hG4bK-e59675b24c1a72b65270c196bc7a5362;rport From: "[trunk-account]" <sip:[trunk-account]@voip.eutelia.it>;tag=17644 To: "[trunk-account]" <sip:[trunk-account]@voip.eutelia.it> Call-ID: fq87utbb@pbx CSeq: 27476 REGISTER Max-Forwards: 70 Contact: <sip:[trunk-account]@[server-ip]:5060;transport=udp;line=9bf31c7f>;+sip.instance="<urn:uuid:cb028e47-5cf1-4e18-a931-4420d3e4e724>" User-Agent: snom-PBX/220.127.116.1158 Supported: outbound Expires: 3600 Content-Length: 0  2012/04/12 21:31:26: Registration on trunk 15 (test) failed. Retry in 60 seconds anyone has any idea what we could check? service was already restarted ... trunk was deleted and reinserted ... nothing helps thanks! Giovanni Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.