Feature #1186

Echo Test

Added by ex1st over 4 years ago. Updated over 4 years ago.

Status:FeedbackStart date:04/24/2013
Priority:HighDue date:
Assignee:lee% Done:

0%

Category:-Spent time:-
Target version:OSTel Operations
Component:

Description

Need to create an echo test for users to check that ostel.co is functioning.

History

#1 Updated by lee over 4 years ago

  • Status changed from New to In Progress

Installing Freeswitch on localhost and routing special numbers to it. This will require adding a username blacklist to the web app so users don't create an account with the same number as the echo test service or any other special service we define.

#2 Updated by lee over 4 years ago

  • Priority changed from Normal to High

#3 Updated by lee over 4 years ago

configure Kam as a SIP peer. IVR services will appear to FS as calls originating from localhost with the user registered under the ostel.co domain. Disable all local SIP users and configure the echo test service for extension 9196.

#4 Updated by lee over 4 years ago

lee wrote:

Installing Freeswitch on localhost and routing special numbers to it. This will require adding a username blacklist to the web app so users don't create an account with the same number as the echo test service or any other special service we define.

disable kamailio from listening on all interfaces, rather it should only listen on the external interface. Freeswitch should listen on localhost. This is the easiest way to run the IVR system without messing with default port numbers.

#5 Updated by lee over 4 years ago

lee wrote:

lee wrote:

Installing Freeswitch on localhost and routing special numbers to it. This will require adding a username blacklist to the web app so users don't create an account with the same number as the echo test service or any other special service we define.

disable kamailio from listening on all interfaces, rather it should only listen on the external interface. Freeswitch should listen on localhost. This is the easiest way to run the IVR system without messing with default port numbers.

There are many locations to configure the listen IP address for FS, mostly in the sip_profiles directory and vars.xml. There are some more for other modules that I'm not using. Clean up this stuff later, as well as configure IPv6 support to listen on only the local interface.

#6 Updated by lee over 4 years ago

Since Freeswitch only listens on localhost, disable ALL authentication to make this easier.

#7 Updated by lee over 4 years ago

  • Status changed from In Progress to Feedback

Echo test is working with ZRTP! I'll create a new ticket for the special services username blacklist in the webapp. I also need to create a username "whitelist" for Kam to be able to route these special services to Freeswitch. These are names matched in the [IVR] route in kamailio.cfg

#8 Updated by lee over 4 years ago

lee wrote:

lee wrote:

lee wrote:

Installing Freeswitch on localhost and routing special numbers to it. This will require adding a username blacklist to the web app so users don't create an account with the same number as the echo test service or any other special service we define.

disable kamailio from listening on all interfaces, rather it should only listen on the external interface. Freeswitch should listen on localhost. This is the easiest way to run the IVR system without messing with default port numbers.

There are many locations to configure the listen IP address for FS, mostly in the sip_profiles directory and vars.xml. There are some more for other modules that I'm not using. Clean up this stuff later, as well as configure IPv6 support to listen on only the local interface.

sofia SIP configuration reference http://wiki.freeswitch.org/wiki/Sofia_Configuration_Files#context

Also available in: Atom PDF