Jump to content
Vodia PBX forum

chrispopp

Members
  • Content count

    160
  • Joined

  • Last visited

Community Reputation

0 Neutral

Contact Methods

  • ICQ
    0
  1. Hi, I'm trying to provision a GXP2130 for multiple extensions on the same phone. I'm using the MAC address field. When opened for provisioning it only provisions the first extension, not all three. I know the Snoms and Yealink works just fine, but for Grandstream it creates two different logs files (generated folder.) But only one extension provisions. Any way to get for example 3 of them? Looking to edit the pmp file, but I just cannot figure out how to insert the second Extension and SIP password values. All other documents use a {loop-start} ...{lc} {loop-end}, but how can I do it for P values on the Grandstream. The grandstream has {user-account 2} but no values...
  2. That wouldn't work. The phone has many extensions on it... Therefore sending the *64 star code would only log-in the first identity (extension.)
  3. Provision logo on Yealink phones

    No, I meant the https... Anyways, I modified the yealink PNP file: From: wallpaper_upload.url = {http-url rest}/domain/{domain}/image/logo/480x272.jpg phone_setting.backgrounds = Config:480x272.jpg To:wallpaper_upload.url = http://www.myserver.com/images/yealinkbg.jpg phone_setting.backgrounds = Config:yealinkbg.jpg
  4. Provision logo on Yealink phones

    I was able to upload it to a webserver, and then change the path in the customized cfg file. Seems to work alright. Doesn't work over https, only over regular http.
  5. Testing with a Yealink phone T46. I uploaded a logo on the web interface but it doesn't provision as the wallpaper on the screen. Any idea?
  6. How about using a http request. Would that work? Any idea on how to do it on a Yealink?
  7. I am testing with a Yealink phone. The yealink phone has 5 extensions on it. The pbx has 5 agent groups. Is it possible that one key can be set to connect ALL extensions to ALL agent groups? For example: Extensions: 101, 102, 103, 104, 105 Agent Groups: 201, 202, 203, 204, 205 When pressing the button: 101 should login into 201, 102 into 202, 103 into 203... When pressed again log-off all extensions. Any idea?
  8. Version 58.1 Provisioning Server Redirection

    Turn ON under the Settings > General > Security > TLS RC4 We were able to test with one and it worked.
  9. Provision Yealink phones via RPS

    The yealink pnp file was misconfigured. Reverted back to default and it works now. Thanks
  10. Provision Yealink phones via RPS

    If it matters the version i'm testing with is 5.7.3
  11. When I open the provisioning to Yealink T48. it returns a 500 error. I'm thinking this has to do with the certificates, but I don't know which to add. Unless it can be something else... [5] 2017/07/24 16:34:23: Prov request: <?xml version='1.0' encoding='UTF-8'?> <methodCall> <methodName>redirect.deRegisterDevice</methodName> <params> <param> <value><string>001565EEEEEE</string></value> </param> </params> </methodCall> [5] 2017/07/24 16:34:23: Prov request: <?xml version='1.0' encoding='UTF-8'?> <methodCall> <methodName>redirect.registerDevice</methodName> <params> <param> <value><string>001565EEEEEE</string></value> </param> <param> <value><string>0ec8bb3e8fee21234567</string></value> </param> <param> <value><string>1</string></value> </param> </params> </methodCall> [6] 2017/07/24 16:34:23: 1 more requests pending to rps.yealink.com:443[7] 2017/07/24 16:34:23: https:rps.yealink.com:443: DNS A returned 184.106.101.50[7] 2017/07/24 16:34:23: https:rps.yealink.com:443: Connect to 184.106.101.50 9] 2017/07/24 16:34:23: https:rps.yealink.com:443: Send requestPOST /xmlrpc HTTP/1.1 Host: rps.yealink.com:443 Content-Length: 207 Authorization: Basic <XYZ> Content-Type: text/xml Accept-Language: en-us User-Agent: Mozilla/4.0 (compatible; PBX) <?xml version='1.0' encoding='UTF-8'?> <methodCall> <methodName>redirect.deRegisterDevice</methodName> <params> <param> <value><string>001565EEEEEE</string></value> </param> </params> </methodCall> [9] 2017/07/24 16:34:23: Initialize TLS connection [7] 2017/07/24 16:34:23: https:rps.yealink.com:443: Return code 500[5] 2017/07/24 16:34:23: Prov response: [7] 2017/07/24 16:34:23: https:rps.yealink.com:443: DNS A returned 184.106.101.50 [7] 2017/07/24 16:34:23: https:rps.yealink.com:443: Connect to 184.106.101.50 [9] 2017/07/24 16:34:23: https:rps.yealink.com:443: Send requestPOST /xmlrpc HTTP/1.1 Host: rps.yealink.com:443 Content-Length: 332 Authorization: Basic XXZZYY Content-Type: text/xml Accept-Language: en-us User-Agent: Mozilla/4.0 (compatible; PBX) <?xml version='1.0' encoding='UTF-8'?> <methodCall> <methodName>redirect.registerDevice</methodName> <params> <param> <value><string>001565EEEEEE</string></value> </param> <param> <value><string>0ec8bb3e8fee21234567</string></value> </param> <param> <value><string>1</string></value> </param> </params> </methodCall> [9] 2017/07/24 16:34:23: Initialize TLS connection[7] 2017/07/24 16:34:23: https:rps.yealink.com:443: Return code 500[5] 2017/07/24 16:34:23: Prov response: [7] 2017/07/24 16:34:23: REST: GET rest/system/session[7] 2017/07/24 16:34:23: REST: GET rest/domain/self/admin[7] 2017/07/24 16:34:23: REST: GET rest/system/session[7] 2017/07/24 16:34:23: REST: GET rest/user/23333%40mark.ssslll.com/log
  12. caller id passthrough

    Setting the indication as Remote Party ID works for us.
  13. Is this a bug or something wrong on my test machine?
  14. Trying to modify an xml file from the Customize > Webpages and every time I save an XML file it reverts back to the original. Under global admin, the saving works fine. But when I log-in into a domain, and try to customize a file, it does not save it. It shows under Currently customized templates, but when re-edit it, it always reverts back to defaults. Any idea? Tried different browsers, and refreshed the cache too... Nothing.
×