Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations MikeeOK on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

no trunk license available for call

Status
Not open for further replies.

hallocje

Technical User
Jan 30, 2014
4
US
I have an IPO 500 v2, VCM32 card with PRI daughter card. I have 4 8 channel PRI E1R2 licenses. The system is in Mexico (thus the E1R2). We only use the E1 for incoming calls. All outbound calls use SIP trunks. We have no problems with outgoing calls on the SIP trunks, and don't seem to have any issues with calls coming in (at least I haven't heard any complaints), however, in the System Status app, we get messages that say "no trunk license available for call" for the PRI line. I've gotten about 40 of them in the last 3 days since we plugged it in. I've searched online and I cannot find any reference to this error. Any ideas? Do I need another license for the PRI card besides the channel licenses?
 
What version? I don't trust SSA, use monitor and enable "Licenses" on the system filter.
 
Is it a single or a dual E1 card?
If dual then you must set the amount of channels per E1 to the correct amount.


BAZINGA!

I'm not insane, my mother had me tested!

 
Indeed, also make sure you haven't left the line/channels in the line group you use for outbound, it may be trying that failing and going out SIP which counts up the alarms every time :)

 
IP Office version 8.0.44. The card is a single PRI 700417439. I've set the Monitor to show only licensing, so I'll wait until the next time the error appears and see what it catches. Thanks.

amriddle01 said:
Indeed, also make sure you haven't left the line/channels in the line group you use for outbound, it may be trying that failing and going out SIP which counts up the alarms every time smile
I don't see anything that would suggest that is configured incorrectly, but I may not be looking in the right place.
 
SSA on 8.0 is bad, ignore the errors if everything else works. I bet there will be no error in sysmonitor.
 
I have been looking at the logs, and around the time the error showed up this morning there is nothing in the logs. So I'll ignore the errors for now, unless someone complains about it.
Thanks for the help.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top