SIP trunk troubleshooting

[ReallyRotten]

I have been trying to troubleshoot a trunk group that goes from CM to Session Manager and then should be routed to the Session Border Controller. Fails every time. I have a working trunk group and duplicated the settings to a new trunk group. The new trunk group does not work. Both trunk groups are pointed at the same session manager instance. I am hoping it is something simple....so any suggestions are welcome.

LIST TRACE

time data

16:01:04 TRACE STARTED 07/08/2013 CM Release String cold-02.0.823.0-20396
16:01:33 Calling party station 5986789 cid 0xc3d
16:01:33 Calling Number & Name 5956419 BTD
16:01:33 dial 92125342345 route:HNPA|ARS
16:01:33 term trunk-group 10 cid 0xc3d
16:01:33 dial 92125342345 route:HNPA|ARS
16:01:33 route-pattern 10 preference 1 location 1/ALL cid 0xc3d
16:01:33 seize trunk-group 10 member 4 cid 0xc3d
16:01:33 Calling Number & Name NO-CPNumber NO-CPName
16:01:33 SIP>INVITE sip:2125342345@10.10.40.8 SIP/2.0
16:01:33 Call-ID: 80d6a3a3cf6e21471551a779c700
16:01:33 Setup digits 2125342345
16:01:33 Calling Number & Name 5986789 BTD
16:01:33 SIP<SIP/2.0 500 Server Internal Error: Destination Unreacha
16:01:33 SIP<ble
time data
16:01:33 Call-ID: 80d6a3a3cf6e21471551a779c700
16:01:33 SIP>ACK sip:2125342345@10.10.40.8 SIP/2.0
16:01:33 Call-ID: 80d6a3a3cf6e21471551a779c700
16:01:33 denial event 1192: Temporary failure D1=0x8a6b D2=0x229
16:01:33 idle trunk-group 10 member 4 cid 0xc3d
16:01:36 idle station 5986789 cid 0xc3d
16:02:16 Calling party station 5986789 cid 0xc47
16:02:16 Calling Number & Name 5986789 BTD
16:02:16 dial 92125342345route:HNPA|ARS
16:02:16 term trunk-group 10 cid 0xc47
16:02:16 dial 92125342345 route:HNPA|ARS
16:02:16 route-pattern 10 preference 1 location 1/ALL cid 0xc47
16:02:16 seize trunk-group 10 member 5 cid 0xc47
16:02:16 Calling Number & Name NO-CPNumber NO-CPName
16:02:16 SIP>INVITE sip:2125342345@10.10.40.8 SIP/2.0
16:02:16 Call-ID: 0b4ddbdcf6e215f1551a779c700

 

[ReallyRotten]

The 3rd line down should read 5986789.

 

[montyzummer]

Are you manipulating the digits for sta 5986789 in the public or private tables ? , as that what it looks like is happening.

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[fataldata]

Beyond the trace I would check the logs/traces in both your Session Manager and Border Controller to determine how far the call is progressing. Since this trace reveals an issue between CM and the Session Manager I would start with the SIP Trace Viewer to see what info it may provide.

Is the near end of the trunk signalling using the Procr interface?

 

[ReallyRotten]

Yes it is the procr interface. What had concerned me in the signaling group is the peer servers showed "others" when I believe it should have showed SM. My remedy was to split up the trunk groups (one for inbound and one for outbound). That was my original plan to begin with but somehow ended up only doing one 2-way trunk group. Clearly that was erroneous