cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Announcement“Cisco Design Thinking Workshop”. Cisco Small Business is excited to invite its Silicon Valley customers to an exclusive interactive one-day session between customers and product Managers.  If you are interested in this exclusive workshop, please fill out the Registration Form. For more information, please check out our FAQ


Get the latest new and information the November issue of the Cisco Small Business Monthly Newsletter

862
Views
0
Helpful
4
Replies
Highlighted

problem with inbound sip limitation with blast groups

I am setting up inbound calling on my SIP trunk. I have run into a problem with inbound sip limitation with blast groups. If I have a certain number of users (more than 8), the initial blast group just rings and goes nowhere. I have confirmed this with Cisco support, but I am guessing that there is a workaround or trick to do what I need to. Thanks for your help.

Everyone's tags (4)
1 ACCEPTED SOLUTION

Accepted Solutions
Enthusiast

problem with inbound sip limitation with blast groups

This is a CLI fix for this problem, but I've seen this resolve this issue when a "generic SIP trunk provider" is programmed in CCA.  Put this in your incoming dial-peers for the SIP trunk:

dial-peer voice XXXX voip
   voice-class sip rel1xx disable

Adam Compton

View solution in original post

4 REPLIES 4
Enthusiast

problem with inbound sip limitation with blast groups

I have a similar setup but I have 10 phones and they all work as expected.  Is this similar to what you have setup?

problem with inbound sip limitation with blast groups

Similar yes, but not exactly. I have blast groups with 15-18 phones. Is your phone system working on a SIP trunk? Do you know of any hard limitations with blast groups on a SIP trunk? If so, can you find a way to work around it?

Enthusiast

problem with inbound sip limitation with blast groups

Yes, I am using SIP for all incoming calls.   There are no hard limits based on blast or hunt groups.  Have you tried to point that SIP DID to a single extension as a test to troubleshoot?

Enthusiast

problem with inbound sip limitation with blast groups

This is a CLI fix for this problem, but I've seen this resolve this issue when a "generic SIP trunk provider" is programmed in CCA.  Put this in your incoming dial-peers for the SIP trunk:

dial-peer voice XXXX voip
   voice-class sip rel1xx disable

Adam Compton

View solution in original post