Karl Stallknecht Posted October 17, 2017 Report Share Posted October 17, 2017 We have a few accounts with offices in different timezones and I thought it would be helpful to show the timezone on the voicemail email if they forward the email between offices and are trying to figure out what the actual time when the voicemail was received was. I used the dropdown and added user.timezone but it just doesn't show anything when I left a test voicemail. My full string is: {{date_called.local|date:"l, F j, Y @ g:i A"}} {{user.timezone}} Which when I tested it just now it shows: Monday, October 16, 2017 @ 8:17 PM (simply missing the timezone at the end) Am I doing something wrong or is this a bug? Link to comment Share on other sites More sharing options...
2600Hz Employees JR^ Posted October 17, 2017 2600Hz Employees Report Share Posted October 17, 2017 This sounds like a bug to me. Can you file a ticket against the back-end for that one? Link to comment Share on other sites More sharing options...
2600Hz Employees mc_ Posted October 17, 2017 2600Hz Employees Report Share Posted October 17, 2017 Have you looked at using the 'date' filter instead? Perhaps try adding 'e' to the date_called args? Link to comment Share on other sites More sharing options...
2600Hz Employees mc_ Posted October 17, 2017 2600Hz Employees Report Share Posted October 17, 2017 Also, is the voicemail box owned by a user? And does the user have a timezone set on the user doc? Link to comment Share on other sites More sharing options...
Karl Stallknecht Posted October 18, 2017 Author Report Share Posted October 18, 2017 4 hours ago, mc_ said: Have you looked at using the 'date' filter instead? Perhaps try adding 'e' to the date_called args? I tried that and it didn't work either. 4 hours ago, mc_ said: Also, is the voicemail box owned by a user? And does the user have a timezone set on the user doc? Yes, and yes. Link to comment Share on other sites More sharing options...
Karl Stallknecht Posted October 18, 2017 Author Report Share Posted October 18, 2017 9 hours ago, JR^ said: This sounds like a bug to me. Can you file a ticket against the back-end for that one? KAZOO-5726 Link to comment Share on other sites More sharing options...
Guest hesaam Posted October 18, 2017 Report Share Posted October 18, 2017 What is the Kazoo version? For Kazoo 4.0 and older there is no "user" macro set for template. You can use "account.timezone" instead. For Kazoo v4.1+ the user macro is set properly. Link to comment Share on other sites More sharing options...
Karl Stallknecht Posted October 18, 2017 Author Report Share Posted October 18, 2017 8 minutes ago, hesaam said: What is the Kazoo version? For Kazoo 4.0 and older there is no "user" macro set for template. You can use "account.timezone" instead. For Kazoo v4.1+ the user macro is set properly. I'm on 4.1 We can't use account.timezone because the account has phones in different timezones, so we need to use the timezone of the user in question. Link to comment Share on other sites More sharing options...
Guest hesaam Posted October 18, 2017 Report Share Posted October 18, 2017 6 minutes ago, Karl Stallknecht said: I'm on 4.1 We can't use account.timezone because the account has phones in different timezones, so we need to use the timezone of the user in question. Can you give a sample log from teletype application? Link to comment Share on other sites More sharing options...
Karl Stallknecht Posted October 18, 2017 Author Report Share Posted October 18, 2017 15 minutes ago, hesaam said: Can you give a sample log from teletype application? Unfortunately I don't have access to that Link to comment Share on other sites More sharing options...
Guest hesaam Posted October 18, 2017 Report Share Posted October 18, 2017 Oh I forgot if you're on 4.1, timezone is also set on "date_called" like "{{date_called.timezone}}". This is the same local timezone which is used to convert the call date timestamp for "{{date_called.local}}". Link to comment Share on other sites More sharing options...
Karl Stallknecht Posted October 18, 2017 Author Report Share Posted October 18, 2017 52 minutes ago, hesaam said: Oh I forgot if you're on 4.1, timezone is also set on "date_called" like "{{date_called.timezone}}". This is the same local timezone which is used to convert the call date timestamp for "{{date_called.local}}". That worked, thanks! Link to comment Share on other sites More sharing options...
Karl Stallknecht Posted October 18, 2017 Author Report Share Posted October 18, 2017 Actually another question: that now says "America/New_York" - is there any way to say EST/EDT instead? Link to comment Share on other sites More sharing options...
Guest hesaam Posted October 18, 2017 Report Share Posted October 18, 2017 Timezone value is coming from Voicemail box, if not found from the owner (user) and if not found again then account and then system. Can you check that you have set the correct time zone for voicemail box or the user? By the way, do the "{{user.first_name}}" or "{{user.last_name}}" are present? Link to comment Share on other sites More sharing options...
Recommended Posts