Comed Posted December 3, 2013 Report Share Posted December 3, 2013 Hi Guys I have a problem with our new snomone appliance. We use version 5.1.2 of Snomone with SPA941 and Snom 320 phones. External calls show the right caller ID, but if we transfer the call, the caller id of the internal number is on the display. is it possible, that the external caller id shows after transfering? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted December 3, 2013 Report Share Posted December 3, 2013 On which device do you have the problem? If the problem is on the SPA, it might be a challenge because SIP has no real standard way of updating the caller-ID. Quote Link to comment Share on other sites More sharing options...
Comed Posted December 4, 2013 Author Report Share Posted December 4, 2013 i have it on all of the phones, external -> snom -> snom or external -> snom -> spa or external -> spa -> spa the main use case would be external -> snom -> spa Quote Link to comment Share on other sites More sharing options...
Vodia support Posted December 4, 2013 Report Share Posted December 4, 2013 We will test this item for you, It might just be a some setting on the trunk header. Can you also tell us which version of software the snom units are running Quote Link to comment Share on other sites More sharing options...
Comed Posted December 5, 2013 Author Report Share Posted December 5, 2013 Thx. Snom 320 with firmware 8.7.3.19 Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted December 5, 2013 Report Share Posted December 5, 2013 We are now running 8.7.3.25 which seems to fix a lot of problems (the long-promised snom firmware). Quote Link to comment Share on other sites More sharing options...
Comed Posted December 10, 2013 Author Report Share Posted December 10, 2013 i updated the snom phones, but no change. can i do something in the clip settings of the trunk? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted December 10, 2013 Report Share Posted December 10, 2013 You probably also have to upgrade the PBX. This is something that we have changed for 5.1.3. Quote Link to comment Share on other sites More sharing options...
Comed Posted December 13, 2013 Author Report Share Posted December 13, 2013 So i updated the PBX too, and the result is bad. No change at all. I understand, that the spa phones are really bad and not from snom. but whats with the snom phones? they should work with the snomone pbx i think. i tried external -> snom -> snom Quote Link to comment Share on other sites More sharing options...
Comed Posted December 18, 2013 Author Report Share Posted December 18, 2013 whats the solution if one only uses snom phones? i understand, that there is no "standard", but the snom phones and the pbx will have a standard way, or not? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted December 21, 2013 Report Share Posted December 21, 2013 If your phone has still the old call logs, it could be that it matches the old SIP URI and then overrides the display-name provided by the PBX. If you can reproduce the problem, try to factory reset one of the phones that has the problem and see if that clears the history and solves the problem. Quote Link to comment Share on other sites More sharing options...
Comed Posted December 30, 2013 Author Report Share Posted December 30, 2013 i tried this, but it did not work. am i the only one with this problem? what clip-settings do you reccomend? Quote Link to comment Share on other sites More sharing options...
Comed Posted January 20, 2014 Author Report Share Posted January 20, 2014 i have no solution for this problem. is there no one with the same issue? what settings should i change to test? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 20, 2014 Report Share Posted January 20, 2014 The Caller-ID topic is unsatisfactory in SIP. Originally the idea was that the phone shows the From-Header. However because it is not allowed to change that header during a conversation (at least not in the beginning), the companies started to do workarounds with Remote-Party-ID, P-Asserted-Identiy and INFO messages with sipfrag attachments. Unfortunately if you got it working with one phone type, it does not work with the next type. We have it on our to-do list to try another approach like now; however honestly this will not guarantee satisfaction. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.