chrispopp

Hi, Is it possible to use the "Destination for incoming calls:" feature in order to send a specific caller to a different part of the pbx? For example: If the caller ID of the person calling is 555-555-5555 I want it to go to extension 200. All other calls to the auto attendant.

Correct. Would like to have 5 minutes in between calls. To be honest 1 minute is somewhat pointless... It is very unlikely to pickup a minute later, if the first call goes unanswered.

The drop menu works fine, but it seems that it's the initial delay after the message is left. For example. Drop menu to 5 mins. Message left. [waits 5 minutes] call 1 [wait 1 min] call2 [wait 1 min] call3...

When using the call cell phone when new message arrives, is there a way to increase the delay from 1 minute to something longer? Reason is that you barely have the time to pick up before it rings again.

We tired two different curl calls. First we tired rest curl ( url = /rest/system/session, method=PUT, data={name=’auth’, value=’’} ) and generate user level session token, and redirect to the usr_portal.html page with custom header with include session token which we got From rest call. This process didn’t worked. Second we tired to make curl ( url=/welcome.htm, method=GET) with basic authorization in header and didn’t worked. Any other ideas?

But is there a way to generate a link or script that would login the user automatically? I want to be able to send their login link directly, without them needing to enter/know the credentials.

Is there a way to create a link to log a user directly into their user portal? What I'm trying to do, is create a link in my billing portal to log the user directly into their user portal and take advantage of the webrtc phone.

Found out what the problem is.... The login only works on port 443. I was using port 8843 for https, since my port 443 was taken up by a different device. I temporarily changed it to 443 and the log-in works correctly.

It is a valid certificate... So I am assuming that user cannot log-in unless they use the whole domain such as 333@domain.xyz.com... which is a pity.

I think the problem is due to the redirect. Instead of logging in, it simply refreshes the page. Am I really the only one having this issue?

Further further testing, i am able to log-in correctly using the full username: 9999@sub.domain.com and the password. I think the problem is withing the welcome.js which I cannot modify: // Redirect to secure login? if (session.secure && window.location.protocol !== 'https:') { var l = 'https://' + window.location.hostname + ":" + session.secure + window.location.pathname + window.location.hash; window.location = l; return; }

So further testing shows that i can log-in using the admin accounts, but domain admin and user portal don't work.

Bump

Were you able to replicate the issue?

Testing with version 56.0 Thank you.

Yes the green lock is on. And working without any errors. The page is displayed correctly, but when i enter the user without the domain or anything, and the password, the page simply refreshes and comes back with the empty fields. Note, that on http, it works fine to log in.

I go to https://subdomain.maindomain.com...and not the IP. I simply want to log as a regular user, not admin. Don't see why there would be a redirect...

It's for a simple subdomain. Not for the whole server. The certificate works fine, and the page seems fine. Just that I cannot login via THAT subdomain.

Used LetsEncrypt to generate a certificate. We are using port 9443 for https. If I go to my subdomain portal, it works fine, and the connection is established and secure (see pic). But cannot login. Using the same credentials via http/port 80, works fine, and can log in without any problems. I can even change the http to https and port 9443, once loged in, and the session works via https... Why can't I log in using https?

Hey guys, Would love a kick in the right direction for this...

I'm having a bit of a hard time reading this, specifically for the buttons. {if_button button value}: and {fi_button}: This tag is used to help renderung buttons. The output is suspended or resumed when the button profile for the current user and the provided button is not present or it set to the provided value. This way the system can skip generating buttons when the user has not set them. Resuming the output does not require any arguments. {ifn_button button value}: and {fin_button}: These tags work like if_button and fi_button, however with inverted logic. and then: {button button}: Insert a button for the current user that has the button number button. This format was used to provision snom phones and should not be used any more. {button-label button}: Insert the label of the button number button. {button-param button}: Insert the paramter of the button number button. Do I need to use both of these, or can i do something along the lines of {button-param 1} {button-param 2} {button-param 3}

Or is there a way to retrieve these buttons using the customize template? ie: how we can get the domain by using {domain}...

I recently started playing with a new phone. This phone has several Memory keys. I want to when a button is pressed, it calls out the representing button of the extension. For example. Extension 2005 has buttons set as 1 Speed Dial 17035556666 2 Speed Dial 17035556667 3 Speed Dial 17035556668 Would like to make button 1 on the phone to call out the button on Vodia and make the call to the speed dial. Any ideas how this can be achieved? It's a no name phone.

Great. Let me test with it. Thank you

I believe that if the admin account leaks, it would be just as easy to log-on and take everything anyways. If we would overwrite it, that means that we would need to support another CMS. Otherwise we can specifically, use the MAC address field, and retrieve the credentials based on that. Only problem is that we currently cannot retrieve the SIP password. There should be a way to retrieve it. I would say that close to 80% of clients are asking for smartphone applications, and it's really hard to be copetitve without one.