SIP URI is set to use a different incoming call group other than default 0. That's my bet. Love these guess the solution riddles without the problem. sip trace please...
I just setup a SIP trunk to a Vocera and have set them up with SNET to a Primary Server.
Not shooting from the hip, offering possible fixes. Without an incoming call route setup correctly it won't work.
SIP traces may help but it's quicker to add the ICR and test.
When you configure the SIP trunk you build the URI table. You assign it an incoming line group and and outgoing line group.
You also assign have many SIP channels you require.
Thats in the SIP line programming.
The Incoming Call Route is not in the SIP line but under its own header.
Configure new ICR,
1. Assign the line group you build in the SIP URI.
2. Incoming number will be *
3. Destination will be . (period)
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.