Upgrade on Mac

[eyeless]

Hi,

 

Maybe there is some information on this, but cannot find it. On the downloads page it says the latest SnomOne DMG file is only for new installations, but what if one wants to upgrade? I find the current version we use to be quite unstable 4.2.0.3958 -- had to restart the server three times before it started to operate normally today.

 

I notice that the Installation from the DMG makes things easy, but places files in totally different places from before on the Mac -- so the question is two-fold -- is the new version more stable and can one replace or move certain files around in order to upgrade?

 

Thanks, Jerry

[pbx support]

The MAC upgrade instructions are here - http://wiki.snomone.com/index.php?title=Upgrades#Mac_Software_Upgrade

[eyeless]

Ah, was not looking carefully ... . Will see if the new version may be more stable ... .

Thanks, Jerry

[eyeless]

I see that this is a different download page than the one where I found the DMG file. Can I use the files on the DMG mount as well and would I need to chmod those files too? I also see that you have included a 'snom ONE Admin' application for some reason .... what is the idea with that? Supposedly one is only supposed to put the SnomOne folder into the applications folder (and I guess that files elsewhere are installed upon launching, which is why this is only to be used for new installations, I guess ...). Just wondering and maybe someone else will ... . /Jerry

[eyeless]

Upgrade went fine, but now they can only have voice one way on their Snom m3 telephone despite rebooting.

 

Logs from the SnomOne: (outbound call - both inbound and outbound works the same way, the person on the Snom m3 hears nothing, but the person on a phone not on this system hears everything):

 

[8] 2011/06/15 14:47:10: Could not find a trunk (7 trunks)

[7] 2011/06/15 14:47:10: Set packet length to 20

[6] 2011/06/15 14:47:10: Sending RTP for GL6VyB8alxudabhc7FP7wMMq@[server] to [client]:5008, codec not set yet

[8] 2011/06/15 14:47:10: Call from an user 40

[8] 2011/06/15 14:47:10: To is <sip:0317018939@[server]>, user 0, domain 1

[8] 2011/06/15 14:47:10: From user 40

[8] 2011/06/15 14:47:10: Set the To domain based on From user 40@[server]

[8] 2011/06/15 14:47:10: Call state for call object 54: idle

[5] 2011/06/15 14:47:10: Dialplan "Company": Match 0317018939@[server] to <sip:0317018939@sip.voicetech.se;user=phone> on trunk Voicetech-031109428

[5] 2011/06/15 14:47:10: Charge user 40 for redirecting calls

[8] 2011/06/15 14:47:10: Play audio_moh/noise.wav

[7] 2011/06/15 14:47:10: set_codecs: for GL6VyB8alxudabhc7FP7wMMq@[server] codecs "", codec_preference count 7

[1] 2011/06/15 14:47:10: UDP: TOS could not be set

[1] 2011/06/15 14:47:10: Last message repeated 2 times

[7] 2011/06/15 14:47:10: set_codecs: for 7adcf6b2@pbx codecs "", codec_preference count 7

[7] 2011/06/15 14:47:10: Set packet length to 20

[6] 2011/06/15 14:47:10: Codec pcmu/8000 is chosen for call id GL6VyB8alxudabhc7FP7wMMq@[server]

[8] 2011/06/15 14:47:10: DNS: Add NAPTR sip.voicetech.se (ttl=60)

[8] 2011/06/15 14:47:10: DNS: Add SRV _sips._tcp.sip.voicetech.se (ttl=60)

[8] 2011/06/15 14:47:10: DNS: Add SRV _sip._tcp.sip.voicetech.se (ttl=60)

[8] 2011/06/15 14:47:10: DNS: Add SRV _sip._udp.sip.voicetech.se (ttl=60)

[8] 2011/06/15 14:47:10: DNS: Add AAAA sip.voicetech.se (ttl=60)

[8] 2011/06/15 14:47:10: Answer challenge with username 031109428

[8] 2011/06/15 14:47:10: Packet authenticated by transport layer

[6] 2011/06/15 14:47:11: Sending RTP for 7adcf6b2@pbx to 213.50.91.3:40444, codec not set yet

[6] 2011/06/15 14:47:11: Codec pcmu/8000 is chosen for call id 7adcf6b2@pbx

[8] 2011/06/15 14:47:11: Call state for call object 54: alerting

[7] 2011/06/15 14:47:11: GL6VyB8alxudabhc7FP7wMMq@[server]: RTP pass-through mode

[7] 2011/06/15 14:47:11: 7adcf6b2@pbx: RTP pass-through mode

[8] 2011/06/15 14:47:12: Packet authenticated by transport layer

[8] 2011/06/15 14:47:18: Last message repeated 3 times

[7] 2011/06/15 14:47:18: Call 7adcf6b2@pbx: Clear last INVITE

[7] 2011/06/15 14:47:18: Determine pass-through mode after receiving response

[8] 2011/06/15 14:47:18: Call state for call object 54: connected

[8] 2011/06/15 14:47:20: Packet authenticated by transport layer

[8] 2011/06/15 14:47:38: Last message repeated 4 times

[7] 2011/06/15 14:47:38: 7adcf6b2@pbx: Media-aware pass-through mode

[8] 2011/06/15 14:47:38: Hangup: Call 139 not found

[8] 2011/06/15 14:47:38: Last message repeated 2 times

[7] 2011/06/15 14:47:38: Call 7adcf6b2@pbx: Clear last request

[5] 2011/06/15 14:47:38: BYE Response: Terminate 7adcf6b2@pbx

 

On the phone log:

 

0101000242 [N](09):Outgoing Call from UA #0 (CallId #3)

0101000242 [N](09):Outgoing Call 3 answered

0101000242 [N](07):RTP Opened. Ch: 0, Len: 160, RxPort: 5008, TxPort: 57972

0101000242 [N](07):Codec routed to RTP Ch: 0, PCM Ch: 0, Codec Type: 0

0101000310 [N](ff):RTP Closed. Ch: 0

 

(I think this was from a similarly failed incoming call:

 

0101000000 [N](09):Registration of user 40 at UA #0 succeeded

0101000031 [N](09):Incoming call to UA #0 - given call id #1

0101000034 [N](07):RTP Opened. Ch: 0, Len: 160, RxPort: 5004, TxPort: 61382

0101000034 [N](07):Codec routed to RTP Ch: 0, PCM Ch: 0, Codec Type: 0

0101000041 [N](ff):RTP Closed. Ch: 0)

[pbx support]

Do you have any other phones, i.e., non-m3 phones? Most of the time the 1-way audio issue are because of codec issue or RTP ports are being blocked by the firewalls. Codec seemed fine based on the log. So check if the RTP ports(the range is in Admin->Settings->Ports page) are open on your firewall(s).

[eyeless]

Yes, we have Snom 320 phones there too on different connections and one on the same connection as the m3. When the m3 did not work they started to use the Snom 320 instead and it works perfectly in the same network and with the "same" setup.

[Guest madigan]

eyeless, can you provide a SIP trace taken from the M3 base station (webinterface -> Status -> SIP Trace)

I presume the RTP Port value is on default? (-> Setup -> Advanced -> SIP/RTP Settings: RTP port: 5004)

[eyeless]

I think the problem was simply that they had pushed the speaker phone button on the side, which had muted all incoming sound ... why and how it can do so I do not know, but apparently this is how it works here ... . However, now that incoming voice can be heard on the handset, it can no longer receive incoming calls ... (Will try and restart the SnomOne server, because that is about the only thing I have not tried.) Managing to register a handset (either m3 & m9) always involves magic and rites ... but usually works after some hours ... .

[eyeless]

The m3 registers incoming calls, but does not ring or show that someone is trying to call it ... maybe that what one has to live with in order to get incoming voice ... hmm.

[eyeless]

Well, somehow it had unregistered itself from the call group in that setting on the phone. Still I have to press the speaker phone on each call in order to receive any incoming voice - can't find a solution to that, but maybe the internal speaker has died or something ... .

[eyeless]

Should also note that the e-mail messaging now magically started to work again after applying the latest upgrade to the SnomOne.

[Guest madigan]

Well, somehow it had unregistered itself from the call group in that setting on the phone.

You mean the "Telephony Settings"? That would be strange. Are the M3s being provisioned?

 

Still I have to press the speaker phone on each call in order to receive any incoming voice - can't find a solution to that, but maybe the internal speaker has died or something ... .

OK, that means incoming calls are being indicated on the display and through the ring tone but when you answer the call there is no audio on the internal speaker? If you receive audio in speaker mode it's definitely the internal one which is defective. (So outgoing calls should have the same problem)

[eyeless]

You mean the "Telephony Settings"? That would be strange. Are the M3s being provisioned?

 

 

OK, that means incoming calls are being indicated on the display and through the ring tone but when you answer the call there is no audio on the internal speaker? If you receive audio in speaker mode it's definitely the internal one which is defective. (So outgoing calls should have the same problem)

 

I think it was provisoned ... (said something about it in the log - sorry for not being better on this, but only deals with these phones now and then). I am not 100% sure I was not inadvertently changing something when I played around with the settings both on the phone, on the web interface and then maybe something happened when resetting the base station and re-registering etc.) - anyway found that setting. I suspect the problem really came down to a damaged internal speaker, since I have to press the speaker button for every phone call now in order to hear anything, but given that I put on the external speaker, the phone now works otherwise well.

 

They still have problem with calls that are cut on some phones, calls that are not forwarded and instead directed to the Voice mail, bad quality of voice, bad operating distance for the esp. the m9 phones, calls where one side stops hearing, etc. Many of these problems could likely be handled if the phones were in the hands of computer savvy people, but they are not and thus complaints are common and difficult to get a good solution for. The stationary phones (Snom 320 works much more reliably). There might have been some new network problems recently as I also experienced a strange "locking" when remote controlling the server, but could see it ping an external server quite normally while my session was "held up" - will need to know first if the SnomOne update helped or not. For some reason things always works better when I am present ... ;-).

[eyeless]

You mean the "Telephony Settings"? That would be strange. Are the M3s being provisioned?

 

OK, that means incoming calls are being indicated on the display and through the ring tone but when you answer the call there is no audio on the internal speaker? If you receive audio in speaker mode it's definitely the internal one which is defective. (So outgoing calls should have the same problem)

 

Think I did not give a good answer. First, I actually am totally clueless about what Provisioning is and how it works and if I use it or not. I think it pertains to how devices can get some some settings from somewhere else, but do not understand how this is supposed to work and do not know where to activate or deactivate it in case that should be relevant. Maybe this could explain why I have some problems at times with registering the mobile devices, but not sure. Maybe it could also change settings in inconsistent ways, but that seems unlikely as has not happened before. (Only account info and server address and phone specific settings are made on the Snom 320 and base stations, all general settings are made on the server. Only ringtones settings have been made directly on the mobile devices. Sometimes language settings has to be made at various places.)

 

The m3 was somewhat easy to set up and get registered in the first place and has worked fine for ca. 2 months and before that for two years at another customer with firmware 1.0 (it was not possible to upgrade and I cannot figure out how to do it - the manual surely does not help anyway).

 

Before I changed the group setting on the phone, the call was registered in the log on the base station, but was not visible on the phone itself. I can find no place to on either the server or the base station to set this setting ... (the base station for the m3 almost have no settings at all anyway (unlike for the m9)).

 

Well, the outgoing voice is heard on the other side whether or not the speaker phone mode is activated, but in order to hear something on my side I have to press the speaker phone button. And, yes, to hear the other side when making an outgoing call one also has to press the speaker button. It is just strange that this happened precisely after I upgraded the server ... .