FisherPricePhone
Technical User
Hi,
We put in server edition for a customer about 2 weeks ago with 2 x servers and 2 x IP office as H.323 gateways. The customer wanted to add a sip trunk to server A which we've done and is now operational. The customer wants the SIP trunk to operate as an overflow in ARS so calls are currently configured to go to ARS which routes the call via 60 x ISDN on IPO1. When the H.323 trunk to IPO1 reaches 60 calls, an H.323 trunk to IPO2 kicks in and routes calls to the 30 channel IPO2 instead using the overflow feature.
OK, so the clever call routing works pretty well except for the next bit...
When we overflow for a second time to a SIP trunk with 30 channels, sometimes we get the old waiting-for-line message or the call tries to complete with between 4 and 6 digits dialled. Here's the annoying bit though, sometimes the call routes just fine. We've found that by using a speed-dial, we can get the calls to go through every time. It seems like it's just something daft but given the scale and complexity of the system, I just can't see it. Also monitor output I'm reading is SIP output. With 100 calls on the go at any one point in time, some pointers on where to find out the route cause through the mire would be appreciated. Another weird one is that the SIP channel licences are reporting that they're maxing out with only some of them in use. Still, I think these issues are well served on the forum here.
Thanks,
FisherPricePhone
It's all just paper cups and bits of string!!!!!!!!!
CCNA, CCDA, ACIS - Implement IP Office, ACSS - Implement IP Office, Convergence + etc...
We put in server edition for a customer about 2 weeks ago with 2 x servers and 2 x IP office as H.323 gateways. The customer wanted to add a sip trunk to server A which we've done and is now operational. The customer wants the SIP trunk to operate as an overflow in ARS so calls are currently configured to go to ARS which routes the call via 60 x ISDN on IPO1. When the H.323 trunk to IPO1 reaches 60 calls, an H.323 trunk to IPO2 kicks in and routes calls to the 30 channel IPO2 instead using the overflow feature.
OK, so the clever call routing works pretty well except for the next bit...
When we overflow for a second time to a SIP trunk with 30 channels, sometimes we get the old waiting-for-line message or the call tries to complete with between 4 and 6 digits dialled. Here's the annoying bit though, sometimes the call routes just fine. We've found that by using a speed-dial, we can get the calls to go through every time. It seems like it's just something daft but given the scale and complexity of the system, I just can't see it. Also monitor output I'm reading is SIP output. With 100 calls on the go at any one point in time, some pointers on where to find out the route cause through the mire would be appreciated. Another weird one is that the SIP channel licences are reporting that they're maxing out with only some of them in use. Still, I think these issues are well served on the forum here.
Thanks,
FisherPricePhone
It's all just paper cups and bits of string!!!!!!!!!
CCNA, CCDA, ACIS - Implement IP Office, ACSS - Implement IP Office, Convergence + etc...