StarTrinity.com

VoIP software

StarTrinity Softswitch - frequently asked questions (FAQ)


Outgoing calls from the StarTrinity VoIP softswitch don't work. Why?
There can be various reasons of the problem:
  • Call is failed with "408 request timeout" error. Possible reason: invalid configuration of IP routing. Examples: softswitch tries to make call via wrong network adapter with wrong IP address; destination GSM gateway IP address is in a different subnet. Possible solution: move IP addresses of softswitch and target into same subnet, remove unneeded IP addresses on softswitch machine
  • Call is failed with "488 not acceptable here" error. Possible reason: invalid configuration of codecs in the softswitch and in the target. Possible solution: set fixed codec: G.711 or G.729
  • Invalid called number (CLD) or CLI format
  • Issue specific to destination number (e.g. blacklist). Try to call a different number in the same area (with same prefix)
  • No call is performed. Possible reasons: syntax error in CallXML script; CPU is overloaded (too many concurrent calls or too many calls per seconds)
For more information about the problem please look into CDR, SIP trace and system log in the softswitch web interface. Remember that behaviour of your terminator (provider) may change during day and with different destination number.

Why am I unable to make more than one parallel call in the softswitch? Second call is rejected with 403.
  • Please check "mac channel" settings for originator and terminator
  • Make sure that your provider allows more than one channel for your account

Incoming calls to the StarTrinity VoIP softswitch are rejected. Why?
There can be various reasons of the problem:
  • Call is failed with "488 not acceptable here" error. Possible reason: invalid configuration of codecs in the softswitch and in the target. Possible solution: set fixed codec: G.711 or G.729
  • Call is failed with "401 authorization required" or "403 forbidden" error. Possible reason: bad username/password or source IP address
  • Call is failed with "408 request timeout" error. Possible reason: VoIP call is blocked by firewall. Open UDP ports 5000...30000 on server where StarTrinity softswitch is installed
  • Syntax error in CallXML script
  • Overload of CPU (too many concurrent calls or too many calls per seconds)
For more information about the problem please look into CDR, SIP trace and system log in the softswitch web interface

Why do I have one-way audio when using the VoIP softswitch in RTP media proxy mode?
There can be various reasons of the problem:
  • Presence of SIP ALG or invalid operation of NAT on router under VoIP traffic. Try to set settings "SymmetricSIP"="1" and "SymmetricRTP"="1" in the StarTrinity softswitch
  • Invalid implementation of codec negotiation procedure in another softswitch or SIP phone. Try to set fixed codec: G.711 or G.729
For more information about the problem please look into CDR, SIP trace and system log of the softswitch

Do you have any plans on making the softswitch compatible with Linux/Unix?
No, it works under Windows only, because a big part of code is written in C# and uses .NET framework

Why is the softswitch free?
It is free because we want to have our softswitch being used by a significant part of VoIP origination, wholesale and termination businesses. We also want to reduce softswitch operation costs for the VoIP businesses. We are going to make profit from interconnections, like speedflow.com. Currently we have enough founds for development and technical support of the VoIP softswitch.

How do I add more prefix to one originator?
  • Add the prefix into origination-side tariff
  • If the new prefix should go to a new terminator: add the prefix in terminator's destination set, add new item in routing group which links the new terminator and destination set
  • If the new prefix should go to same terminator: add the prefix into current terminator's destination set

Why do I get an error with PayPal API when I run softswitch on Windows XP or Windows Server 2003?
Paypal requires TLS 1.2 which is not supported by .NET Framework on the old operating systems. You need to upgrade to Windows Vista or Windows Server 2008.

Copyright 2011-2017 StarTrinity.com | Blog | Contact lead developer via LinkedIn | Get support via TeamViewer