In the script I am basically forwarding the caller to a persons cell phone (and other numbers) based on difffent logic.
The issue is it only rings twice then fails. Registers as Call.RequeryStatus=3 (Ring no Answer).
How can I extend that ring time in ICM?
I have it doing to a dialed number that is a dummy number on a dummy phone that forwards teh call out from CM. When I call the dummy number from a phone in that CM Cluster - it works fine - no isses - rings till VM answers. SO the issue lies with the call coming out of ICM.
I have tried it both as a "dynamic label" and "configured label" (not that it would matter but just for kicks) and the results are the same.
It DOES call the number - but only allows for 2 rings and ends. I can (and did) enable the requery on the label node but all that gives me is the system making muliple back to back 2 ring calls.
I feel like there should be a RNA setting in ICM somewhere but there isn't. Not for an outboud call off a label. There is a setting for internal calls on the agent desk settings but that has no effect on this.
Can you send the call offnet then to that phone? Also, disable the requery on the label. Ultimately, ICM needs to see a label and just sends the call off without keeping track of it.
If I disable the requery then the call will just ring twice then disconnect.
It's not just sending the call off - it's "keeping tabs" of it for some reason.
If i do it as a dynamic label and don't enable the requery - it will ring out twice then play an error message.
If I do it as a configured label - it will ring twice then disconnect.
I have a feeling the issue is going to be on the ingress gateway. If I remember correctly, there might be a timer somewhere in there that might be dropping the call. What happens when you send the call offnet (through PSTN)?
I'm not 100% sure what you mean by "offnet".
I can tell you - when I call the label from a phone that is on that UCM Cluster - it works just fine and rings more than twice.
As a matter of fact - i tested that with a few different numbers - and got the same results each time. It only fails if the call originates from ICM.
Time to bring in your IPT guys and find out what is disconnecting the call, is it UCM or the ingress gateway.
That should work. You return a label to CVP (like 8885551234) and CVP consults the SIP proxy (or gatekeeper) and you have static routes to all your subscribers. Then CUCM will see that as a standard pattern and prefix "91" and place the call. You are hairpinning of course - using an inbound channel and an outbound channel on possibly two different gateways for the life of the call. Worked for me, but I am trying to remember if I had to do something on the ingress dial peers.
Alternatively, let the proxy send back to the ingress gateway, catch it on a dial peer and send it out the POTS dial peer.