Soporte & Consultoria

Soporte Remoto y Consultoria skype : ambiorixg12.
Nota no se brinda ningun tipo de consulta o soporte fuera del blog de forma gratuita

viernes, 15 de septiembre de 2017

Difference Between 180 Ringing and 183 Session Progress

Difference Between 180 Ringing and 183 Session Progress

In general, ringing is controlled via two Informational Responses in SIP: the 180 Ringing and the 183 Session Progress.
The main difference between them, is the 180 Ringing message instructs the UA to create the dial-tone locally, whereas the 183 Session Progress contains an SDP, which allows for regional ring-back and carrier announcements as well.
Typically 183 contains SDP and is used to play media before the call is connected
-----------------------------------------------------

a) 180 Ringing
   The UA receiving the INVITE is trying to alert the user. This
   response MAY be used to initiate local ringback.
b) 183 Session Progress
   The 183 (Session Progress) response is used to convey information
   about the progress of the call that is not otherwise classified.

https://supportforums.cisco.com/t5/ip-telephony/difference-between-180-ringing-and-183-session-progress/td-p/2413632

martes, 15 de agosto de 2017

freepbx extensions_override_freepbx.conf example

[from-internal]
exten=>h,1,Noop(${VM_MESSAGEFILE}   )
same=>n,System(php /var/www/html/voicemail/insert.php ${VM_MESSAGEFILE} )
same=>n,Set(CDR(accountcode)=00000)
same=>n,Set(CDR(userfield)=222)
same=>n,hangup()


[macro-dialout-trunk]
include => macro-dialout-trunk-custom
exten => s,1,Set(DIAL_TRUNK=${ARG1})
exten=>s,n,Set(CDR(userfield)=${MIXMONITOR_FILENAME});; code  ambiorix for rec ${EPOCH},,%Y%m%d-%H%M%S)}


jueves, 27 de julio de 2017

asterisk call id

https://wiki.asterisk.org/wiki/display/AST/Unique+Call-ID+Logging+in+Asterisk+12+and+beyond

martes, 18 de julio de 2017

sábado, 15 de julio de 2017

FreePBX custom extension




[from-internal-custom]
exten=>_100,1,Answer()
same=>n,Playback(hello-world)

sábado, 8 de julio de 2017

Google Speech API

https://cloud.google.com/speech/docs/languages
https://cloud.google.com/speech/docs/basics
https://github.com/GoogleCloudPlatform/php-docs-samples/blob/master/speech/quickstart/quickstart.php
https://cloud.google.com/speech/docs/getting-started
https://cloud.google.com/speech/docs/basics
https://cloud.google.com/speech/docs/reference/libraries#client-libraries-usage-php
https://cloud.google.com/speech/docs/
Interactive guide

https://codelabs.developers.google.com/codelabs/cloud-speech-intro/index.html?index=..%2F..%2Findex#0


quick

https://cloud.google.com/speech/docs/reference/libraries



translation

https://cloud.google.com/php/docs/reference/


default credentials
https://github.com/google/google-auth-library-php
https://developers.google.com/identity/protocols/application-default-credentials


lunes, 5 de junio de 2017

freepx asterisk service


Saltar al final de los metadatos
Ir al inicio de los metadatos
As most distributions have moved to systemd, here's an example startup script that you may customize for your installation.
This has been tested to work on CentOS 7.
Contents of /etc/systemd/system/freepbx.service
[Unit]
Description=FreePBX VoIP Server
After=mariadb.service
 
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/sbin/fwconsole start -q
ExecStop=/usr/sbin/fwconsole stop -q
 
[Install]
WantedBy=multi-user.target
  
From there you can enable it so it starts automatically
Note that on Debian 8.1, you need to use After=mysql.service, not After=mariadb.service. 
[root@firewall ~]# systemctl enable freepbx.service
ln -s '/etc/systemd/system/freepbx.service' '/etc/systemd/system/multi-user.target.wants/freepbx.service'
[root@firewall ~]#
And then start it yourself if you haven't already
[root@firewall ~]# systemctl start freepbx
[root@firewall ~]#
You can check the output of the startup with the 'systemctl status' command
[root@firewall ~]# systemctl status -l freepbx.service
freepbx.service - FreePBX VoIP Server
   Loaded: loaded (/etc/systemd/system/freepbx.service; enabled)
   Active: active (exited) since Mon 2015-08-17 09:20:09 AEST; 52s ago
  Process: 5020 ExecStart=/usr/sbin/fwconsole start (code=exited, status=0/SUCCESS)
 Main PID: 5020 (code=exited, status=0/SUCCESS)
Aug 17 09:20:06 firewall.xrobau.com fwconsole[5020]: Running Sysadmin Hooks
Aug 17 09:20:06 firewall.xrobau.com fwconsole[5020]: Starting Asterisk...
Aug 17 09:20:06 firewall.xrobau.com fwconsole[5020]: 0/100 [>---------------------------]   0%
Aug 17 09:20:07 firewall.xrobau.com fwconsole[5020]: 33/100 [=========>------------------]  33%
Aug 17 09:20:08 firewall.xrobau.com fwconsole[5020]: 66/100 [==================>---------]  66%
Aug 17 09:20:09 firewall.xrobau.com fwconsole[5020]: 99/100 [===========================>]  99%
Aug 17 09:20:09 firewall.xrobau.com fwconsole[5020]: 100/100 [============================] 100%
Aug 17 09:20:09 firewall.xrobau.com fwconsole[5020]: Asterisk Started on  5523
Aug 17 09:20:09 firewall.xrobau.com fwconsole[5020]: Running Post-Asterisk Scripts
Aug 17 09:20:09 firewall.xrobau.com systemd[1]: Started FreePBX VoIP Server.
[root@firewall ~]#