<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article Vitelity Error Codes in Vitelity Portal</title>
    <link>https://community.sinch.com/t5/Vitelity-Portal/Vitelity-Error-Codes/ta-p/17163</link>
    <description>&lt;DIV class="lia-message-template-content-zone"&gt;
&lt;H2&gt;Look up call failure codes&lt;/H2&gt;
&lt;DIV data-pm-slice="1 1 []"&gt;
&lt;DIV class="hs-table-align-center" data-hs-responsive-table="true"&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD&gt;BUSY&lt;/TD&gt;
&lt;TD&gt;
&lt;P&gt;This error means we received a busy signal from your server or device&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;DIV class="hs-table-align-center" data-hs-responsive-table="true"&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;CALL_REJECTED&lt;/P&gt;
&lt;/TD&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;This error usually means your server or device rejected our call.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;DIV class="hs-table-align-center" data-hs-responsive-table="true"&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;CANCEL&lt;/P&gt;
&lt;/TD&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;Call is cancelled. The dial command reached its number, but the caller hung up before the caller picked up.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;DIV class="hs-table-align-center" data-hs-responsive-table="true"&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;CHANUNAVAIL&lt;/P&gt;
&lt;/TD&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;This error usually means your server or device is not currently registered to our servers.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;
&lt;P&gt;Recommended Solution:&lt;/P&gt;
&lt;/TD&gt;
&lt;TD&gt;
&lt;P&gt;Please make sure you are registered to the correct inbound server for your account as per the configuration samples found on the support page within the user portal and that you have selected the correct routing method for your DID(s) on the DIDs page. If you are aware of this error and are purposely having calls fail to utilize our failover feature, please disregard this message&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;DIV class="hs-table-align-center" data-hs-responsive-table="true"&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;CONGESTION&lt;/P&gt;
&lt;/TD&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;This error usually means your server or device does not recognize the number being dialed.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;
&lt;P&gt;Recommended Solution:&lt;/P&gt;
&lt;/TD&gt;
&lt;TD&gt;
&lt;P&gt;If using asterisk, make sure you have the correct inbound context specified on your inbound trunk and that you have correctly added an inbound route/extension logic for this DID&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;DIV class="hs-table-align-center" data-hs-responsive-table="true"&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;NO_ANSWER&lt;/P&gt;
&lt;/TD&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;This error means we attempted to route the call to your server, but received no answer&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;DIV class="hs-table-align-center" data-hs-responsive-table="true"&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;NO_USER_RESPONSE&lt;/P&gt;
&lt;/TD&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;This error means we attempted to route the call to your server, but received no answer&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;DIV class="hs-table-align-center" data-hs-responsive-table="true"&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;NORMAL_CIRCUIT_CONGESTION&lt;/P&gt;
&lt;/TD&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;This error usually means your server or device does not recognize the number being dialed.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;
&lt;P&gt;Recommended Solution:&lt;/P&gt;
&lt;/TD&gt;
&lt;TD&gt;
&lt;P&gt;If using asterisk, make sure you have the correct inbound context specified on your inbound trunk and that you have correctly added an inbound route/extension logic for this DID&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;DIV class="hs-table-align-center" data-hs-responsive-table="true"&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;ORIGINATOR_CANCEL&lt;/P&gt;
&lt;/TD&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;Call is cancelled. The dial command reached its number, but the caller hung up before the caller picked up&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;DIV class="hs-table-align-center" data-hs-responsive-table="true"&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;Over the channel Limit&lt;/P&gt;
&lt;/TD&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;This call failure could have been the result of various issues. The failure cause could be Post Dialed Delay, Ring back, and or channel limitations.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;
&lt;P&gt;Recommended Solution:&lt;/P&gt;
&lt;/TD&gt;
&lt;TD&gt;
&lt;P&gt;Please contact Voyant if you have further concerns regarding this failed call. If this DID is assigned to a Virtual PRI you may order more channels within the Order section of the customer user portal. Otherwise please contact our customer support department to have this limit raised.&lt;/P&gt;
&lt;P&gt;Please Note: DID numbers with the Unlimited Local DID rate plan may only receive 4 simultaneous inbound calls; Unfortunately, this limit cannot be increased. However, per request we can convert the number to the PPM (Pay Per Minute) rate plan which does not have this channel restriction. If you no longer wish to receive these emails, you may disable this feature within the My Account section of the customer user portal.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;DIV class="hs-table-align-center" data-hs-responsive-table="true"&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;REQUESTED_CHAN_UNAVAIL&lt;/P&gt;
&lt;/TD&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;This error usually means your server or device is not currently registered to our servers.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;
&lt;P&gt;Recommended Solution:&lt;/P&gt;
&lt;/TD&gt;
&lt;TD&gt;
&lt;P&gt;Please make sure you are registered to the correct inbound server for your account as per the configuration samples found on the support page within the user portal and that you have selected the correct routing method for your DID(s) on the DIDs page. If you are aware of this error and are purposely having calls fail to utilize our failover feature, please disregard this message&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;DIV class="hs-table-align-center" data-hs-responsive-table="true"&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;UNKNOWN&lt;/P&gt;
&lt;/TD&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;An unknown error has occurred&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;
&lt;P&gt;Recommended Solution:&lt;/P&gt;
&lt;/TD&gt;
&lt;TD&gt;
&lt;P&gt;Please open a trouble ticket within the user portal for further assistance&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;DIV class="hs-table-align-center" data-hs-responsive-table="true"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
    <pubDate>Tue, 12 Nov 2024 22:18:03 GMT</pubDate>
    <dc:creator>Bill_Balvanz</dc:creator>
    <dc:date>2024-11-12T22:18:03Z</dc:date>
    <item>
      <title>Vitelity Error Codes</title>
      <link>https://community.sinch.com/t5/Vitelity-Portal/Vitelity-Error-Codes/ta-p/17163</link>
      <description>&lt;DIV class="lia-message-template-content-zone"&gt;
&lt;H2&gt;Look up call failure codes&lt;/H2&gt;
&lt;DIV data-pm-slice="1 1 []"&gt;
&lt;DIV class="hs-table-align-center" data-hs-responsive-table="true"&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD&gt;BUSY&lt;/TD&gt;
&lt;TD&gt;
&lt;P&gt;This error means we received a busy signal from your server or device&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;DIV class="hs-table-align-center" data-hs-responsive-table="true"&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;CALL_REJECTED&lt;/P&gt;
&lt;/TD&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;This error usually means your server or device rejected our call.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;DIV class="hs-table-align-center" data-hs-responsive-table="true"&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;CANCEL&lt;/P&gt;
&lt;/TD&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;Call is cancelled. The dial command reached its number, but the caller hung up before the caller picked up.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;DIV class="hs-table-align-center" data-hs-responsive-table="true"&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;CHANUNAVAIL&lt;/P&gt;
&lt;/TD&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;This error usually means your server or device is not currently registered to our servers.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;
&lt;P&gt;Recommended Solution:&lt;/P&gt;
&lt;/TD&gt;
&lt;TD&gt;
&lt;P&gt;Please make sure you are registered to the correct inbound server for your account as per the configuration samples found on the support page within the user portal and that you have selected the correct routing method for your DID(s) on the DIDs page. If you are aware of this error and are purposely having calls fail to utilize our failover feature, please disregard this message&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;DIV class="hs-table-align-center" data-hs-responsive-table="true"&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;CONGESTION&lt;/P&gt;
&lt;/TD&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;This error usually means your server or device does not recognize the number being dialed.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;
&lt;P&gt;Recommended Solution:&lt;/P&gt;
&lt;/TD&gt;
&lt;TD&gt;
&lt;P&gt;If using asterisk, make sure you have the correct inbound context specified on your inbound trunk and that you have correctly added an inbound route/extension logic for this DID&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;DIV class="hs-table-align-center" data-hs-responsive-table="true"&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;NO_ANSWER&lt;/P&gt;
&lt;/TD&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;This error means we attempted to route the call to your server, but received no answer&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;DIV class="hs-table-align-center" data-hs-responsive-table="true"&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;NO_USER_RESPONSE&lt;/P&gt;
&lt;/TD&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;This error means we attempted to route the call to your server, but received no answer&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;DIV class="hs-table-align-center" data-hs-responsive-table="true"&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;NORMAL_CIRCUIT_CONGESTION&lt;/P&gt;
&lt;/TD&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;This error usually means your server or device does not recognize the number being dialed.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;
&lt;P&gt;Recommended Solution:&lt;/P&gt;
&lt;/TD&gt;
&lt;TD&gt;
&lt;P&gt;If using asterisk, make sure you have the correct inbound context specified on your inbound trunk and that you have correctly added an inbound route/extension logic for this DID&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;DIV class="hs-table-align-center" data-hs-responsive-table="true"&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;ORIGINATOR_CANCEL&lt;/P&gt;
&lt;/TD&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;Call is cancelled. The dial command reached its number, but the caller hung up before the caller picked up&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;DIV class="hs-table-align-center" data-hs-responsive-table="true"&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;Over the channel Limit&lt;/P&gt;
&lt;/TD&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;This call failure could have been the result of various issues. The failure cause could be Post Dialed Delay, Ring back, and or channel limitations.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;
&lt;P&gt;Recommended Solution:&lt;/P&gt;
&lt;/TD&gt;
&lt;TD&gt;
&lt;P&gt;Please contact Voyant if you have further concerns regarding this failed call. If this DID is assigned to a Virtual PRI you may order more channels within the Order section of the customer user portal. Otherwise please contact our customer support department to have this limit raised.&lt;/P&gt;
&lt;P&gt;Please Note: DID numbers with the Unlimited Local DID rate plan may only receive 4 simultaneous inbound calls; Unfortunately, this limit cannot be increased. However, per request we can convert the number to the PPM (Pay Per Minute) rate plan which does not have this channel restriction. If you no longer wish to receive these emails, you may disable this feature within the My Account section of the customer user portal.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;DIV class="hs-table-align-center" data-hs-responsive-table="true"&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;REQUESTED_CHAN_UNAVAIL&lt;/P&gt;
&lt;/TD&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;This error usually means your server or device is not currently registered to our servers.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;
&lt;P&gt;Recommended Solution:&lt;/P&gt;
&lt;/TD&gt;
&lt;TD&gt;
&lt;P&gt;Please make sure you are registered to the correct inbound server for your account as per the configuration samples found on the support page within the user portal and that you have selected the correct routing method for your DID(s) on the DIDs page. If you are aware of this error and are purposely having calls fail to utilize our failover feature, please disregard this message&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;DIV class="hs-table-align-center" data-hs-responsive-table="true"&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;UNKNOWN&lt;/P&gt;
&lt;/TD&gt;
&lt;TD data-insertable="true"&gt;
&lt;P&gt;An unknown error has occurred&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;
&lt;P&gt;Recommended Solution:&lt;/P&gt;
&lt;/TD&gt;
&lt;TD&gt;
&lt;P&gt;Please open a trouble ticket within the user portal for further assistance&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;DIV class="hs-table-align-center" data-hs-responsive-table="true"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Tue, 12 Nov 2024 22:18:03 GMT</pubDate>
      <guid>https://community.sinch.com/t5/Vitelity-Portal/Vitelity-Error-Codes/ta-p/17163</guid>
      <dc:creator>Bill_Balvanz</dc:creator>
      <dc:date>2024-11-12T22:18:03Z</dc:date>
    </item>
  </channel>
</rss>

