Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

SIP Route List doesn't use second sip trunk

Hi all,

we are using two sip trunks in one CM-cluster (4.1(3)sr3), let's say trunk-A and trunk-B.

Both trunks are member of the same route group, the route group is member of one route list. The route pattern is assigned to this route list.

Trunk-B is our SIP-IVR-backup-server, so we stopped the IVR on server-A (with trunk-A) and expected Callmanager to reroute the call to server-B (with trunk-B), but nothing happens.

We took a look at detailed CM traces, CM tries just to reach server-A.

Any ideas?

Thanks in advance,

Axel

3 REPLIES
Green

Re: SIP Route List doesn't use second sip trunk

Hi Axel,

BAsically CCM will attempt to allocate first an MTP for the SIP trunk then send an INVITE.

For the first TRUNK found in the RG.

Under CCM Service Parameters check:

Retry Count for SIP Invite*

You may play with it.

The IVR is sending back a message like any 4XX Error message in SIP? Or no Message response?

You may check also

Stop Routing on Out of Bandwidth Flag*

Stop Routing on Unallocated Number Flag* (404 Not found)

Stop Routing on User Busy Flag*

Now that you have the traces, please upload them, make sure:

*Enable SIP Call Processing Trace

*Enable SIP Stack Trace

Are checked.

HTH

New Member

Re: SIP Route List doesn't use second sip trunk

Hi HTH,

thank you for your answer.

We stoped the service on server-A, so there is no response on port 5060/UDP.

I attach the CCM-Traces:

starts at 10/04/2006 15:56:33.001

Server-A = 134.17.1.1

Server-B = 130.11.1.1

SEP0011924BCB1A, IP = 140.11.194.230, DN 2672

Kind regards

Axel

Green

Re: SIP Route List doesn't use second sip trunk

Hi Axel,

Try to change (reduce) the Retry Count for SIP Invite* under Service Parameters, per SDL trace is set to 6 and SIP Trying Timer which is the maximum time that Cisco CallManager will wait to receive a 100 response to an INVITE request, this one also reduce it.

001479579| 06/10/04 15:56:33.782| 002| SdlSig | SIPTimer | wait | SIPHandler(2,100,110,1) | SdlTimerService(2,100,3,1) | (2,100,119,1).762836-(MTP_V4170232:144.17.120.232)| [NP - PQ: 0]TimerType=SIP_TIMER_TRYING value=500 numRetries=6 ccb=0x06003A88

*********************************************

001479658| 06/10/04 15:57:36.938| 002| SdlSig | SIPTimer | wait | SIPHandler(2,100,110,1) | SdlTimerService(2,100,3,1) | (2,100,119,1).762836-(MTP_V4170232:144.17.120.232)| [NP - PQ: 0]TimerType=SIP_TIMER_TRYING value=32000 numRetries=0 ccb=0x06003A88

*********************************************

001479677| 06/10/04 15:57:36.938| 002| SdlSig | DStopConf | routeListExhausted_shutting_down| RouteListCdrc(2,100,104,17) | RouteListControl(2,100,105,3) | (2,100,119,1).762836-(MTP_V4170232:144.17.120.232)| [R:NP - HP: 0, NP: 4, LP: 0, VLP: 0, LZP: 0 DBP: 0]varChannelStatus=0

It seems that CCM is rejecting to place the call with Reorder tone due to RouteListExhausted.

Please verify the service parameter "Stop Routing on User Busy Flag", and if this is True, please try 'False'.

Let me know

Thanks

656
Views
0
Helpful
3
Replies