Jump to content

almoondsllc

Members
  • Posts

    53
  • Joined

  • Last visited

Posts posted by almoondsllc

  1. Is there a way to change the chipers Vodia offers?  I'm trying with pipedream, things are going better...

    [9] 20:08:47.488 Initialize TLS connectionⓘ
    [9] 20:08:47.489 Last message repeated 2 timesⓘ
    [9] 20:08:47.489 HTTP 18.235.89.39: Send Client Hello(03035F97..00020017)ⓘ
    [9] 20:08:47.574 HTTP 18.235.89.39: Receive Server Hello(03035153..03000102)ⓘ
    [9] 20:08:47.575 HTTP 18.235.89.39: Receive Certificate(0012D700..5DF4038C)ⓘ
    [9] 20:08:47.575 HTTP 18.235.89.39: Received chain with 4 certificatesⓘ
    [8] 20:08:47.585 HTTP 18.235.89.39: Certificate name *.m.pipedream.net matchesⓘ
    [9] 20:08:47.585 HTTP 18.235.89.39: Receive Server Key Exchange(03001741..C2BBB7BC)ⓘ
    [9] 20:08:47.610 HTTP 18.235.89.39: Pre Master Secret(8CCC9BC7..CD3D4A66)ⓘ
    [9] 20:08:47.610 HTTP 18.235.89.39: Client Random(5F971EBF..272B7BAE)ⓘ
    [9] 20:08:47.610 HTTP 18.235.89.39: Server Random(5153BF0F..90BE3932)ⓘ
    [9] 20:08:47.610 HTTP 18.235.89.39: Master Secret(0FA8E970..01FF2C34)ⓘ
    [9] 20:08:47.610 HTTP 18.235.89.39: Receive Server Hello Done()ⓘ
    [9] 20:08:47.610 HTTP 18.235.89.39: Send Client Key Exchange(41047A93..D64234EE)ⓘ
    [9] 20:08:47.610 HTTP 18.235.89.39: Send Change Cipher Spec(01)ⓘ
    [9] 20:08:47.610 HTTP 18.235.89.39: Perform Change Cipher Spec(c027)ⓘ
    [9] 20:08:47.610 HTTP 18.235.89.39: Key Block(69BE62E3..0B3CD2EE)ⓘ
    [9] 20:08:47.610 HTTP 18.235.89.39: Client Write MAC Secret(69BE62E3..CCC9915B)ⓘ
    [9] 20:08:47.610 HTTP 18.235.89.39: Server Write MAC Secret(80E3C9AB..C0BE85EE)ⓘ
    [9] 20:08:47.610 HTTP 18.235.89.39: Client Write Key(D028C2B0..CA784F3C)ⓘ
    [9] 20:08:47.610 HTTP 18.235.89.39: Server Write Key(25CE52D0..22FD34C6)ⓘ
    [9] 20:08:47.611 HTTP 18.235.89.39: Send Finished(9427E587..309049E1)ⓘ
    [9] 20:08:47.696 HTTP 18.235.89.39: Receive Change Cipher Spec(01)ⓘ
    [9] 20:08:47.696 HTTP 18.235.89.39: Receive Process Finished(31BFE9E2..F3C2587E)ⓘ
    [9] 20:08:47.833 Received 435 bytesⓘ
    HTTP/1.1 200 OK
    Date: Mon, 26 Oct 2020 19:08:47 GMT
    Content-Type: text/html; charset=UTF-8
    Content-Length: 179
    Connection: keep-alive
    X-Powered-By: Express
    Access-Control-Allow-Origin: *
    x-pd-status: sent to coordinator
    ETag: W/"b3-174a20b59d8"

     

  2. Handshake Failure...

    [9] 19:57:25.204 Initialize TLS connectionⓘ
    [9] 19:57:25.204 Last message repeated 2 timesⓘ
    [9] 19:57:25.204 HTTP 149.154.167.220: Send Client Hello(03035F97..00020017)ⓘ
    [5] 19:57:25.209 HTTP 149.154.167.220: Alert Fatal (2): Handshake failure (40)ⓘ
    [7] 19:57:25.209 https:api.telegram.org:443: TCP disconnectⓘ
    [7] 19:57:25.209 https:api.telegram.org:443: Return code 500ⓘ

     

  3. Hello, I'm trying to receive Telegram message on my bot when a new call comes into the system

    I'm using HTTPS POST JSON according to telegram 

    https://core.telegram.org/bots/api#making-requests

    So in Vodia -> Advanced ->Action URL I put:

    ** When a new call comes in **

    Authentication metod: None

    Method: POST

    URL: https://api.telegram.org/bot<mytoken>/sendMessage

    Encoding for the message body: JSON

    Message Body: {"chat_id": "mychatid", "text": "This is a test from curl", "disable_notification": true}

     

    But it doesn't work, some help? Thanks.

     

    Alessandro

     

  4. I think Vodia should say clearly if Zoho CRM/Phonebridge is supported or not. I got the enterprise version for the Zoho CRM integration, according the link https://doc.vodia.com/zoho_crm it should work but in fact it doesn't.

    I spent hours trying to get all this working and then Zoho support (I'm a Zoho one customer) told me this:

    Sorry to disappoint you. Please note that as of now you can only use the supported providers of Zoho. Please log-on to crm.zoho.com--> Click Setup--> Select Telephony under Channels and check the list if supported providers--> you can integrate any one of listed supported providers.
    You can find the supported telephony partners from this list: https://www.zoho.com/telephony/provider-lists.html
    Unfortunately, it is not possible to use any of the unlisted providers with Zoho. Since you are using the telephony integration with Zoho using API it is not supported and we are unable to assist for the error facing with it.  If you want to register your provider as a supported partner for Zoho, please access the below link and register the details of the telephony system you are using.
    https://www.zoho.com/phonebridge/

    In fact in one of the log I found this:

    https:www.zohoapis.eu:443: Return content (90 bytes)ⓘ
    {"message":"PBX_NOT_INTEGRATED","status":"error","code":"PBX_NOT_INTEGRATED","details":{}}

    I opened a ticket on support.vodia.com support and they are just saying like "did you check the docs? did you check this and that?".

    I'm using the last version and build 65.0.10, I'm on Google Cloud with all the ports opened, https working, the check on the right of the "GET AUTH CODE" on the CRM setting of the extension is GREEN.

    Just to avoid other waste of time, I ask to Vodia engineers to officially say if Zoho CRM/Phonebrige is working or not, thanks a lot.

    Alessandro Marzini

  5. In fact I disabled the TLS on the phone and SRTP, the problem is that I still have 20 snom phones at this customer that now they are working with TLS, but I don't know for how long more it will be ok. How I can check the reason of the SRTP key negotation fails? If the solution is upgrading to a recent version of PBX, is the problem related to some Certificate expiration? If yes, how check when is the expiration? Just to be sure that nothing will happen until that date, thanks.

  6. I started to play with the option in Hunt Group, From-Header and I realized that also with the just "Calling party name (CMC)" I got what I need:

    First line: <calling number> or <calling name - called number> if present in addressbook 

    Second line: <called number> or <called name - called number> if present in addressbook 

    This mean the call is delivered to the phone in different way if just like a simple extension or like hunt group. Anyway I solved my problem and I really thank you for your support. Any problem or need or request discussed in this forum increase the level of knowledge of Vodia 😎

    Regards,

    Alessandro

  7. It works! :)

    The interesting thing is this:

    Before the change, on the display of the snom I got this:

    First line of LCD: <caller id number>

    Second line of LCD: blank

     

    After the change you suggested:

    First line of LCD: icon of the phone ringing <caller id number> (<called number>)   <<<---- according the new setup

    Second Line of LCD: icon of contact <name of the called number> <number of the called number> <<---snom automatically added

     

    So it's like then snom add a second line displaying the called number-contact when he see a "to:" header

    image.png.715298822273205455d61b7f1a343c85.png

    So the final question, if I want to show on the first line only the calling number (370129...) and in the secon line the concact-number (I'M BURGHER 0586193...), what to change in the config you posted? Thank you

     

    Regards,

    Alessandro

     

  8. The 50 DIDs on the system are working in this way:

    I have a sip trunk (ip auth) configured with the provider who assigned to me a GNR like +3905861234xx meaning all inbound calls from +390586123400 to +3905861234099 are routed in my pbx, so the pbx see coming call for +390586123400->99, at this point I should be able to intercept the DNID and display on the extension (snom d712) what's the +3905861234xx called (dnid) and who is calling (caller-id).

    I can of course assign the trunk sip receiving the 100 dnid to only one Hunt Group and then in the Hunt Group rules add a custom-headers to display dnid + caller-i in the "from-header" in behavior settings, I think is a good starting.

  9. My problems is showing on the Snom not only the callerid of the person calling but also the DID called (or the trunk name). So I don't know on which part of the setting of the trunk make changes: Number/Call Identification? Routing/Redirection?

    Shortly:

    caller +39370123456 calls the did +39058612345. I want to see on the snom (Snom 710) this:

    "+39370123456 (+39058612345)"

    or better, if I've mapped +39058612345. to "Google" in the addressbook: 

    "+39370123456 (Google)"

     

  10. I did some progress...

    If I put in DTMF List this ->   !1!-!

    And in the List of Actions -> http://192.168.178.123:8181

    Then on the server I receive this:

    POST / HTTP/1.1
    Host: 192.168.178.123:8181
    SOAPAction: IvrInput
    Content-Type: text/xml
    Content-Length: 408

    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sns="http://soap.com/pbx"><env:Body><sns:IVRInput><CallID>313538383236343131323436363937-c6qipkp2gide</CallID><Output></Output><From>&quot;Alessandro Marzini&quot; &lt;sip:40@localhost&gt;</From><To>&quot;IVR Zero&quot; &lt;sip:4000@localhost&gt;</To><IpAdr>tls:192.168.178.136:35913</IpAdr></sns:IVRInput></env:Body></env:Envelope>
     

    So it seems working now. What I don't understand is why I've to put the single dash (-) when docs are saying:

    "If the destination field contains a single dash (-) and the pattern matches, the PBX will disconnect the call."

  11. 12 minutes ago, Support said:

    Have you gone through the doc we gave earlier? It has example about how you can setup the DTMF list in it.

    Please check that and let us know.

    Yes I did, I tried a lot of combination but I never received anything on the server side.

    That's why I'm asking a very basic example of what to put in the DTMF List, what in "List of actions".

    By the way, what the "Remote application control" is used for?

    The "Mute when user presses a key" seems not working, I still hear the "beep" when I digit dtmf while I'm connected to the IVR.

    I can received events like :

    Method: POST
    Headers: {'Remote-Addr': '192.168.178.122', 'Host': '192.168.178.123:8090', 'Content-Type': 'application/json', 'Content-Length': '99'}
    Args (url path): ()
    Keyword Args (url parameters): {}
    Body: b'\\{"id":17,"from":\\"Alessandro Marzini\\" <sip:40@localhost>,"to":\\"IVR Zero\\" <sip:4000@localhost>\\}'

    just because I setup correctly the Advanced->Action URL setting as in the pic attached.

     

    Istantanea_2020-04-30_18-01-08.png

  12. Hello,

    I'm trying to setup an IVR node where the dtmf digits the user input are passed to the an external server. I'm actually using a simple "netcat -l -p 8080" to check if something arrives on the server but nothing...

    It's not clear, at least for me, how to fill correctly  "DTMF Match List" "From/To-based routing match list", List of Actions" "Remote Application contro Yes/No" in IVR Node. Can you provide a simple example like the user call ivr node 4000, digit 9 numbers and these 9 digits are redirected via HTTP to external server on port 8080 ip 192.168.1.x

    Thank you very much for the help.

     

    Regards,

    Alessandro Marzini

  13. For example, with Pushbullet API I can use my phone to send sms with this:

    curl --header 'Access-Token: xxxxxxxxxxxxxxxxxxxxxxx' --header 'Content-Type: application/json' --data-binary '{"push":{"conversation_iden":"+39xxxxxxxxx","message":"Hello from Almoonds PushBullet","package_name":"com.pushbullet.android","source_user_iden": "yyyyyyyy","target_device_iden":"zzzzzzzzzz", "type": "messaging_extension_reply"},"type":"push"}' --request POST https://api.pushbullet.com/v2/ephemerals

    As you can see is a simple HTTP post with a body and some headers that let the customer using any android phone + pushbullet app sending sms from the phone

    Can you add a "Generic HTTP SMS Provider" in the list? 

     

  14. Hello,

    I'm checking the SMS setting and I saw only few provider are supported. So why don't you plan to implement a "custom SMS provider support" where the user just need to specify like HTTP POST, the body, headers, etc, something like a general HTTP post setup. It would be simple in this case for integrators like me implementing some "gateway server" vodia <---http_post---->gateway<---anysms provider>. Thank you for your attention.

     

    Regards,

    Alessandro Marzini

  15. Hello,

    I want to setup an automatic service flag for summer holidays so that with this service flag I can control the IVR messages in autoattendant and have multiple service flag for multiple type of holiday and so different IVR messages.

    So I created an automatic service flag with the logic "Specify times when flag is active (calls are redirected)" where I filled only "Holidays hours" and "List of holidays".

    In "Holiday hours" I put "00:00-24:00" to specify the whole day and in "List of holidays"  I put for example "08/01/2019-08/31/2019":  the flag is activated for every day between 1st and 31st August and it's ok, BUT if I use the format "08/01-08/31" in "List of holidays", the flag is not activated like the range format is not recognized. Is that a bug or I'm doing wrong somewhere?

    Btw this mechanism to specify a service flag only for holidays is a bit tricky because the "List of Holidays" logic that is (according to the manual) "To specify the days on which you do not want the schedule to be activated, such as a holiday or any other day, use the holiday field", but at least it works :)

    Thank you for your help,

    Alessandro

×
×
  • Create New...