cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1855
Views
10
Helpful
2
Replies

PROBLEM WITH FORWARDING ALL - SIP TRUNK

alicia.vega
Level 1
Level 1

Hello,

I'm experiencing the following problem:

I have this scenario: PSTN - SIP GW - CUCM6.1 - SIP TRUNK - CUM8.6

Phone A (extension 33476761834) is registered on CUCM8.6, with external forwarding to the PSTN.

If someone from CUCM8.6 calls - it works.

If someone from CUCM6.1 or from PSTN calls - fast busy. Error in CUCM traces:

19:20:47.056 |//SIP/SIPTcp/wait_SdlSPISignal: Outgoing SIP TCP message to 145.245.235.201 on port 36615 index 3295

[1925279,NET]

SIP/2.0 500 Internal Server Error

Via: SIP/2.0/TCP 145.245.235.201:5100;branch=z9hG4bK3744a3159aed8f

From: <sip:1767@145.245.235.201>;tag=e1d37fe6-cb7b-46e7-a868-6fe81d6bb391-40319184

To: <sip:1834@145.245.116.26>;tag=907605~2b367b5a-23ed-4193-a18b-e8c2f777615e-62999964

Date: Thu, 26 Sep 2013 17:20:46 GMT

Call-ID: f9a33080-24416cee-339879-c9ebf591@145.245.235.201

CSeq: 101 INVITE

Allow-Events: presence

Reason: Q.850;cause=100

Content-Length: 0

|2,100,63,1.580442^145.245.235.232^*

Any idea? Thanks a lot!

(Attaching the complete trace).

2 Replies 2

Ayodeji Okanlawon
VIP Alumni
VIP Alumni

Alicia,

I have looked at your traces and here are my observations..

1. It looks as if you have enabled EO on the CUCM8.6 sip trunk, hence cucm tryies to allocate a MTP device for EO. Here we can see that MTP_4 was allocated

18:59:16.564 |MediaResourceManager::waiting_MrmAllocateMtpResourceRes - CI=62999932 deviceName=MTP_4 deviceCap=57 count=1|3,100,63,1.95460^145.245.235.201^*

18:59:16.564 |MRM::updateMtpCounter devName=MTP_4, countChange=1|3,100,63,1.95460^145.245.235.201^*

18:59:16.564 |MRM::updateXcodeCounter devName=MTP_4, countChange=1|3,100,63,1.95460^145.245.235.201^

2. While cucm was computitng the SDP needed to send EO, something goes wrong. It is not clear what went wrong but we can see CUCM de-allocating the selected MTP device..

18:59:16.753 |SIG-MediaManager-(17782) - eoCleanup - Deallocated MTP - resourceCI(62999932), MRM(3,1)|2,100,63,1.580390^145.245.235.232^*

3. CUCM then says that an invalid disconnect cause happened. It didnt tell us exactly what happened

18:59:16.755 |//SIP/SIPCdpc(3,74,20955)/ci=62999928/ccbId=907589/scbId=0/appendReasonHdr: appendReasonHdr - Invalid Disconnect Cause(cause=100), No Reason Header Appended|2,100,63,1.580390^145.245.235.232^*

18:59:16.755 |//SIP/SIPCdpc(3,74,20955)/ci=62999928/ccbId=907589/scbId=0/addTransparencyInfo: Transparency info is NULL.  Not attaching anything.|2,100,63,1.580390^145.245.235.232^*

18:59:16.755 |//SIP/SIPCdpc(3,74,20955)/ci=62999928/ccbId=907589/scbId=0/appendRPIDHdrForOriginalCalledParty: SIP device does not Support Orig Dialled Phone nego: 0|2,100,63,1.580390^145.245.235.232^*

Its a little difficult to tell whats going on here but here are my thoughts

1. It is possible CUCM is unable to do DO-EO over two sip trunks from different CUCM clusters

2. There may be a problem with the selected MTP device..

Suggestions...

1. Try and enable EO on the sip trunk on CUCM6.1 or

2. Try to disable EO on CUCM8.6 or

3. Remove MTP_4 from your MRG and see if another MTP device will work for DO-EO

Let m know if any of the suggestions work

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

Please rate all useful posts

Hi,

Making some tests regarding the problem we saw this:

Oct  1 23:02:22: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

INVITE sip:0034638139199@145.245.242.121:5060 SIP/2.0

Date: Tue, 01 Oct 2013 23:02:22 GMT

Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, PUBLISH

From: <sip:00034661616350@145.245.235.201>;tag=e1d37fe6-cb7b-46e7-a868-6fe81d6bb391-40468009

Allow-Events: presence

Supported: timer,replaces

Min-SE:  1800

Diversion: " Elodie" " <sip:33476768900@145.245.108.29>;reason=unconditional;privacy=off;screen=yes

Remote-Party-ID: <sip:00034661616350@145.245.235.201>;party=calling;screen=yes;privacy=off

Content-Length: 0

User-Agent: Cisco-CUCM6.1

To: <sip:0034638139199@145.245.242.121>

Contact: <00034661616350>

Expires: 180

Call-ID: 86455880-24b1547e-33edda-c9ebf591@145.245.235.201

Via: SIP/2.0/TCP 145.245.235.201:5060;branch=z9hG4bK3863af2fe80489

CSeq: 101 INVITE

Session-Expires:  1800

Max-Forwards: 67



Oct  1 23:02:22: //350172/5D95E6C38917/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 400 Bad Request - 'Malformed CC-Diversion/Diversion/CC-Redirect Header'

Via: SIP/2.0/TCP 145.245.235.201:5060;branch=z9hG4bK3863af2fe80489

From: <sip:00034661616350@145.245.235.201>;tag=e1d37fe6-cb7b-46e7-a868-6fe81d6bb391-40468009

To: <sip:0034638139199@145.245.242.121>;tag=DA70FE78-21AE

Call-ID: 86455880-24b1547e-33edda-c9ebf591@145.245.235.201

CSeq: 101 INVITE

Reason: Q.850;cause=100

Content-Length: 0

The problem is because in the redirect header, the comma "," is not a valid parameter so in the alerting name I removed the comma after the surname (i.e. "Elodie, Mary" to "Elodie Mary" and now is working.

We will change the alerting name by the moment and I will also investigate if there is a parameter to just not divert this name because is not needed this info in forwarded calls.


Anyway the problem is solved