Snom phones can't call out (Network failure)

[JohnM]

Hi all,

I'm having some problems with the rollout of a new system. 3cx is cloud hosted, and clients/phones are at a few different locations.

The 3cx mac/windows/iOS clients are working perfectly. However for Snom phones, although they can receive calls (and in that situation audio passes correctly in both directions), they can't dial out. It's not even that the call connects and then there is no audio, it just times out and fails with "Network failure"

Even more strangely, Gigaset N300 based handsets manually configured work perfectly. Snom phones either manually configured, or provisioned by 3cx (following a factory reset) all fail, so it seems to be a configuration issue specific to the Snoms.

In the logs for the Snoms, we see the following;

--
Jan 12 14:53:14.012 [WARN ] SIP: transaction_timeout udp: 1001252 (32000)

Jan 12 14:53:14.013 [ERROR ] SIP: transport error: 1001252 -> Udp:[3CX-IP]:5060

Jan 12 14:53:14.013 [NOTICE] SIP: Add dirty host: Udp:[3CX-IP]:5060 (0 sec)

Jan 12 14:53:14.013 [ERROR ] SIP: request 1001252 destination invalid Udp:[3CX-IP]:5060 3135313537363531363133383934-x6g13tk75lov

Jan 12 14:53:14.013 [NOTICE] SIP: final transport error: 1001252 -> Udp:[3CX-IP]:5060

Jan 12 14:53:14.023 [NOTICE] CSTA: csta_cid = 2 phone_cid2 csta_cid = 3 phone_cid3 csta_cid = 4 phone_cid4 csta_cid = 5 phone_cid5 csta_cid = 6 phone_cid6 csta_cid = 7 phone_cid7 csta_cid = -2 phone_cid-2 csta_cid = 8 phone_cid8 csta_cid = -3 phone_cid-3 csta_cid = 9 phone_cid9 csta_cid = -4 phone_cid-4 csta_cid = -5 phone_cid-5 csta_cid = -6 phone_cid-6 csta_cid = 10 phone_cid10 csta_cid = 11 phone_cid11 csta_cid = -7 phone_cid-7 csta_cid = -8 phone_cid-8 csta_cid = -9 phone_cid-9 csta_cid = 12 phone_cid12 csta_cid = 13 phone_cid13 csta_cid = 14 phone_cid14 csta_cid = 15 phone_cid15 csta_cid = 16 phone_cid16 csta_cid = 17 phone_cid17 csta_cid = 18 phone_cid18 csta_cid = 19 phone_cid19 csta_cid = 20 phone_cid20 csta_cid = 21 phone_cid21 csta_cid = 22 phone_cid22 csta_cid = 23 phone_cid23 csta_cid = 24 phone_cid24 csta_cid = 25 phone_cid25 csta_cid = 26 phone_cid26 csta_cid = 27 phone_cid27 csta_cid = 28 phone_cid28 csta_cid = 29 phone_cid29 csta_cid = 30 phone_cid30 csta_cid = 31 phone_cid31 csta_cid = 32 phone_cid32 csta_cid = 33 phone_cid33 csta_cid = 34 phone_cid34 csta_cid = 35 phone_cid35 csta_cid = 36 phone_cid36 csta_cid = 37 phone_cid37 csta_cid = -13 phone_cid-13 csta_cid = -14 phone_cid-14 csta_cid = -15 phone_cid-15 csta_cid = -16 phone_cid-16 csta_cid = -17 phone_cid-17 csta_cid = 38 phone_cid38 csta_cid = 39 phone_cid39 csta_cid = 40 phone_cid40 csta_cid = 41 phone_cid41 csta_cid = 42 phone_cid42 csta_cid = 43 phone_cid43 csta_cid = 44 phone_cid44 csta_cid = 45 phone_cid45 csta_cid = 46 phone_cid46

Jan 12 14:53:14.094 [ERROR ] SIP: transport error 1001252: generating fake 599

Jan 12 14:53:14.151 [NOTICE] MEDIA: MediaIpc::rtpClose: RP63

Jan 12 14:53:14.151 [NOTICE] MEDIA: MediaIpc::rtpClose: RC63

Jan 12 14:53:14.152 [ERROR ] MEDIA: Stream setup: invalid ssrc 104789790, state off

Jan 12 14:53:14.185 [NOTICE] MEDIA: onRtpClose: RP63

Jan 12 14:53:14.224 [NOTICE] MEDIA: onRtpClose: RC63
--

The only possibly hint I found from searching for the above error messages is related to IP Fragmentation.
ip_frag_enable is set to on, but it has made no difference.

There are no SBCs in play. Phones have the 3cx recommended software version running.

Any hints gratefully received!

 

[leejor]

Looking at the 3CX Activity log, do you see a call attempt by the Snom sets? If so, then an error message may provide a clue as to what is going on. That fact that even a manually configured set won't work, does suggest a Snom option, that is not correct. Is that an internal dialplan that requires configuration?