Toggle sidebar Toggle sidebar

Help Trunk Between 3CX and Cisco UCM

Status
Not open for further replies.

mikegillespie

Silver Partner
Basic Certified
Joined
Feb 15, 2012
Messages
30
Reaction score
1
HI,
The goal is to trunk the 3CX (v14) and UCM together for extension dialing and UCM access to PSTN trunks attached to 3CX.
1. The Cisco devices associated with the UCM must allowed to dial to extensions and trunks on the 3CX (v14)
2. The SIP devices registered to the 3CX must be allowed to dial extensions of Cisco Devices registered to the UCM

We have established a generic trunk (no authentication) between the 3CX and UCM.
3CX SIP endpoints can call devices registered to the UCM.
Devices registered to the UCM cannot dial extensions on 3CX or use PSTN trunks.

If I created a DID for a 3CX extension on the 3CX Trunk inbound from the UCM, the caller from the UCM device can reach the phone on the 3CX. The problem with this is that it doesn't make sense to create a DID for each extension on the 3CX and they will not be able to dial out to the PSTN this way.

Any help with this is much appreciated.

Thanks

Mike
 
  • Like
Reactions: Daniel Sobrinho
Using trunks of 3CX is not possible from other PBX extensions when you interconnect PBXs via generic SIP trunk, mostly for security reasons.
You have to use a bridge on 3CX to accomplish this, but may experience problems with caller's IDs.
If you are using generic SIP trunk, you need DDI table (inbound rules) in order to call extensions in 3CX.
 
  • Like
Reactions: datamerge
I have tried the bridge, however, i am told the CUCM is not capable of registering to a SIP server on it's own. Is there any other way?
 
mikegillespie said:
i am told the CUCM is not capable of registering to a SIP server on it's own. Is there any other way?
Click to expand...

How does it normally interface to a provider? Are there various methods (types of Interface cards) available?

From you original post, it would seem that you have established a VoIP connection between the two. Do you have 3CX registering to the CUCM as if it were a Provider? If that is the case, then I'd be surprise if the CUCM can't register to a VoIP provider. The Bridge trunk settings will allow 3CX to appear as that.
 
Last edited:
leejor said:
How does it normally interface to a provider? Are there various methods (types of Interface cards) available?

From you original post, it would seem that you have established a VoIP connection between the two. Do you have 3CX registering to the CUCM as if it were a Provider? If that is the case, then I'd be surprise if the CUCM can't register to a VoIP provider. The Bridge trunk settings will allow 3CX to appear as that.
Click to expand...
Hi, I had set up a generic provider with no authenticaton and they registered. The issue is, endpoint registered to the CUCM would not me able to dial any extensions on the 3cx with there being a DID and endpoint restrered to the CUCM would not be able to use the trunk on the 3CX to make external calls.
Did i miss something? its quite possible.

Thanks
Mike
 
mikegillespie said:
Hi, I had set up a generic provider with no authentication and they registered.
Click to expand...
So you had 3CX registered to the CUCM? In that case, any calls in the direction of 3CX would be routed as a whole trunk group, all incoming calls to one destination, or as DIDs (If the CUCM was capable of that). If you set-up a Bridge trunk, you can send digits, routing calls to specific extensions, or outbound rules. Bridge trunks can be set-up as a master or slave. So... 3Cx can register to a provider, or in this case , the CUCM, or it can act as a provider allowing registration from the CUCM. If you are attempting to allow extensions on the CUCM to access outbound trunks on the 3CX PBX, then a bridge trunk would be the best way of achieving that.
 
Hi,
I have them setup as a bridge and here is what I see when a call is attempted from an endpoint on the CUCM into the 3CX.

Code: 
07-Feb-2017 09:35:05.388   Leg L:776.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505723~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453595] is terminated: Cause: BYE from PBX
07-Feb-2017 09:35:05.338   Leg L:776.2[Extn:200] is terminated: Cause: 488 Not Acceptable Here/INVITE from 10.0.7.127:5063
07-Feb-2017 09:35:05.338   L:776.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505723~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453595] failed to reach Extn:200, reason Not Acceptable HereReason Unknown
07-Feb-2017 09:35:05.338   Call to T:Extn:200@[Dev:sip:[email protected]:5063] from L:776.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505723~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453595] failed, cause: Cause: 488 Not Acceptable Here/INVITE from 10.0.7.127:5063
07-Feb-2017 09:35:05.338   [CM503003]: Call(C:776): Call to <sip:[email protected]:5060> has failed; Cause: 488 Not Acceptable Here/INVITE from 10.0.7.127:5063
07-Feb-2017 09:35:05.277   [CM503025]: Call(C:776): Calling T:Extn:200@[Dev:sip:[email protected]:5063] for L:776.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505723~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453595]
07-Feb-2017 09:35:05.270   [CM503027]: Call(C:776): From: DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505723~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453595 ("SX10 x5506" <sip:[email protected]:5060>)  to  T:Extn:200@[Dev:sip:[email protected]:5063]
07-Feb-2017 09:35:05.270   [CM503004]: Call(C:776): Route 1: from L:776.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505723~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453595] to T:Extn:200@[Dev:sip:[email protected]:5063]
07-Feb-2017 09:35:05.270   [CM503001]: Call(C:776): Incoming call from DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505723~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453595 to <sip:[email protected]:5060>
07-Feb-2017 09:35:05.270   NAT/ALG check:L:776.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505723~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453595] REQUEST 'INVITE' - some of SIP/SDP headers may contain inconsistent information or modified by intermediate hop
   SIP contact header is not equal to the SIP packet source(IP:port):
      Contact address:10.0.4.62:5060
      Received from :10.0.4.62:34267
07-Feb-2017 09:35:05.106   Leg L:775.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505721~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453593] is terminated: Cause: BYE from PBX
07-Feb-2017 09:35:05.096   Leg L:775.2[Extn:200] is terminated: Cause: 488 Not Acceptable Here/INVITE from 10.0.7.127:5063
07-Feb-2017 09:35:05.096   L:775.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505721~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453593] failed to reach Extn:200, reason Not Acceptable HereReason Unknown
07-Feb-2017 09:35:05.096   Call to T:Extn:200@[Dev:sip:[email protected]:5063] from L:775.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505721~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453593] failed, cause: Cause: 488 Not Acceptable Here/INVITE from 10.0.7.127:5063
07-Feb-2017 09:35:05.096   [CM503003]: Call(C:775): Call to <sip:[email protected]:5060> has failed; Cause: 488 Not Acceptable Here/INVITE from 10.0.7.127:5063
07-Feb-2017 09:35:05.000   [CM503025]: Call(C:775): Calling T:Extn:200@[Dev:sip:[email protected]:5063] for L:775.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505721~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453593]
07-Feb-2017 09:35:04.976   [CM503027]: Call(C:775): From: DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505721~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453593 ("SX10 x5506" <sip:[email protected]:5060>)  to  T:Extn:200@[Dev:sip:[email protected]:5063]
07-Feb-2017 09:35:04.976   [CM503004]: Call(C:775): Route 1: from L:775.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505721~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453593] to T:Extn:200@[Dev:sip:[email protected]:5063]
07-Feb-2017 09:35:04.976   [CM503001]: Call(C:775): Incoming call from DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505721~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453593 to <sip:[email protected]:5060>
07-Feb-2017 09:35:04.976   NAT/ALG check:L:775.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505721~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453593] REQUEST 'INVITE' - some of SIP/SDP headers may contain inconsistent information or modified by intermediate hop
   SIP contact header is not equal to the SIP packet source(IP:port):
      Contact address:10.0.4.62:5060
      Received from :10.0.4.62:34267
07-Feb-2017 09:35:04.790   Leg L:774.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505719~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453591] is terminated: Cause: BYE from PBX
07-Feb-2017 09:35:04.740   Leg L:774.2[Extn:200] is terminated: Cause: 488 Not Acceptable Here/INVITE from 10.0.7.127:5063
07-Feb-2017 09:35:04.740   L:774.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505719~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453591] failed to reach Extn:200, reason Not Acceptable HereReason Unknown
07-Feb-2017 09:35:04.740   Call to T:Extn:200@[Dev:sip:[email protected]:5063] from L:774.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505719~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453591] failed, cause: Cause: 488 Not Acceptable Here/INVITE from 10.0.7.127:5063
07-Feb-2017 09:35:04.740   [CM503003]: Call(C:774): Call to <sip:[email protected]:5060> has failed; Cause: 488 Not Acceptable Here/INVITE from 10.0.7.127:5063
07-Feb-2017 09:35:04.692   [CM503025]: Call(C:774): Calling T:Extn:200@[Dev:sip:[email protected]:5063] for L:774.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505719~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453591]
07-Feb-2017 09:35:04.647   [CM503027]: Call(C:774): From: DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505719~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453591 ("SX10 x5506" <sip:[email protected]:5060>)  to  T:Extn:200@[Dev:sip:[email protected]:5063]
07-Feb-2017 09:35:04.647   [CM503004]: Call(C:774): Route 1: from L:774.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505719~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453591] to T:Extn:200@[Dev:sip:[email protected]:5063]
07-Feb-2017 09:35:04.646   [CM503001]: Call(C:774): Incoming call from DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505719~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453591 to <sip:[email protected]:5060>
07-Feb-2017 09:35:04.646   NAT/ALG check:L:774.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505719~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453591] REQUEST 'INVITE' - some of SIP/SDP headers may contain inconsistent information or modified by intermediate hop
   SIP contact header is not equal to the SIP packet source(IP:port):
      Contact address:10.0.4.62:5060
      Received from :10.0.4.62:34267
07-Feb-2017 09:35:04.433   Leg L:773.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505717~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453589] is terminated: Cause: BYE from PBX
07-Feb-2017 09:35:04.382   Leg L:773.2[Extn:200] is terminated: Cause: 488 Not Acceptable Here/INVITE from 10.0.7.127:5063
07-Feb-2017 09:35:04.382   L:773.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505717~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453589] failed to reach Extn:200, reason Not Acceptable HereReason Unknown
07-Feb-2017 09:35:04.382   Call to T:Extn:200@[Dev:sip:[email protected]:5063] from L:773.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505717~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453589] failed, cause: Cause: 488 Not Acceptable Here/INVITE from 10.0.7.127:5063
07-Feb-2017 09:35:04.382   [CM503003]: Call(C:773): Call to <sip:[email protected]:5060> has failed; Cause: 488 Not Acceptable Here/INVITE from 10.0.7.127:5063
07-Feb-2017 09:35:04.295   [CM503025]: Call(C:773): Calling T:Extn:200@[Dev:sip:[email protected]:5063] for L:773.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505717~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453589]
07-Feb-2017 09:35:04.249   [CM503027]: Call(C:773): From: DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505717~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453589 ("SX10 x5506" <sip:[email protected]:5060>)  to  T:Extn:200@[Dev:sip:[email protected]:5063]
07-Feb-2017 09:35:04.249   [CM503004]: Call(C:773): Route 1: from L:773.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505717~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453589] to T:Extn:200@[Dev:sip:[email protected]:5063]
07-Feb-2017 09:35:04.249   [CM503001]: Call(C:773): Incoming call from DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505717~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453589 to <sip:[email protected]:5060>
07-Feb-2017 09:35:04.248   NAT/ALG check:L:773.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505717~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453589] REQUEST 'INVITE' - some of SIP/SDP headers may contain inconsistent information or modified by intermediate hop
   SIP contact header is not equal to the SIP packet source(IP:port):
      Contact address:10.0.4.62:5060
      Received from :10.0.4.62:34267
 
You probably need to adjust/normalize some SIP profile configuration settings?:confused:

Code: 
   Leg L:776.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505723~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453595] is terminated: Cause: BYE from PBX
   Leg L:776.2[Extn:200] is terminated: Cause: 488 Not Acceptable Here/INVITE from 10.0.7.127:5063
   L:776.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505723~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453595] failed to reach Extn:200, reason Not Acceptable HereReason Unknown
   Call to T:Extn:200@[Dev:sip:[email protected]:5063] from L:776.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505723~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453595] failed, cause: Cause: 488 Not Acceptable Here/INVITE from 10.0.7.127:5063
   [CM503003]: Call(C:776): Call to <sip:[email protected]:5060> has failed; Cause: 488 Not Acceptable Here/INVITE from 10.0.7.127:5063
   [CM503025]: Call(C:776): Calling T:Extn:200@[Dev:sip:[email protected]:5063] for L:776.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505723~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453595]
   [CM503027]: Call(C:776): From: DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505723~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453595 ("SX10 x5506" <sip:[email protected]:5060>)  to  T:Extn:200@[Dev:sip:[email protected]:5063]
   [CM503004]: Call(C:776): Route 1: from L:776.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505723~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453595] to T:Extn:200@[Dev:sip:[email protected]:5063]
   [CM503001]: Call(C:776): Incoming call from DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505723~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453595 to <sip:[email protected]:5060>
   NAT/ALG check:L:776.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505723~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453595] REQUEST 'INVITE' - some of SIP/SDP headers may contain inconsistent information or modified by intermediate hop
   SIP contact header is not equal to the SIP packet source(IP:port):
      Contact address:10.0.4.62:5060
      Received from :10.0.4.62:34267
   Leg L:775.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505721~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453593] is terminated: Cause: BYE from PBX
   Leg L:775.2[Extn:200] is terminated: Cause: 488 Not Acceptable Here/INVITE from 10.0.7.127:5063
   L:775.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505721~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453593] failed to reach Extn:200, reason Not Acceptable HereReason Unknown
   Call to T:Extn:200@[Dev:sip:[email protected]:5063] from L:775.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505721~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453593] failed, cause: Cause: 488 Not Acceptable Here/INVITE from 10.0.7.127:5063
   [CM503003]: Call(C:775): Call to <sip:[email protected]:5060> has failed; Cause: 488 Not Acceptable Here/INVITE from 10.0.7.127:5063
   [CM503025]: Call(C:775): Calling T:Extn:200@[Dev:sip:[email protected]:5063] for L:775.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505721~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453593]
   [CM503027]: Call(C:775): From: DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505721~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453593 ("SX10 x5506" <sip:[email protected]:5060>)  to  T:Extn:200@[Dev:sip:[email protected]:5063]
   [CM503004]: Call(C:775): Route 1: from L:775.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505721~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453593] to T:Extn:200@[Dev:sip:[email protected]:5063]
   [CM503001]: Call(C:775): Incoming call from DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505721~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453593 to <sip:[email protected]:5060>
   NAT/ALG check:L:775.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505721~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453593] REQUEST 'INVITE' - some of SIP/SDP headers may contain inconsistent information or modified by intermediate hop
   SIP contact header is not equal to the SIP packet source(IP:port):
      Contact address:10.0.4.62:5060
      Received from :10.0.4.62:34267
   Leg L:774.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505719~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453591] is terminated: Cause: BYE from PBX
   Leg L:774.2[Extn:200] is terminated: Cause: 488 Not Acceptable Here/INVITE from 10.0.7.127:5063
   L:774.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505719~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453591] failed to reach Extn:200, reason Not Acceptable HereReason Unknown
   Call to T:Extn:200@[Dev:sip:[email protected]:5063] from L:774.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505719~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453591] failed, cause: Cause: 488 Not Acceptable Here/INVITE from 10.0.7.127:5063
   [CM503003]: Call(C:774): Call to <sip:[email protected]:5060> has failed; Cause: 488 Not Acceptable Here/INVITE from 10.0.7.127:5063
   [CM503025]: Call(C:774): Calling T:Extn:200@[Dev:sip:[email protected]:5063] for L:774.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505719~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453591]
   [CM503027]: Call(C:774): From: DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505719~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453591 ("SX10 x5506" <sip:[email protected]:5060>)  to  T:Extn:200@[Dev:sip:[email protected]:5063]
   [CM503004]: Call(C:774): Route 1: from L:774.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505719~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453591] to T:Extn:200@[Dev:sip:[email protected]:5063]
   [CM503001]: Call(C:774): Incoming call from DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505719~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453591 to <sip:[email protected]:5060>
   NAT/ALG check:L:774.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505719~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453591] REQUEST 'INVITE' - some of SIP/SDP headers may contain inconsistent information or modified by intermediate hop
   SIP contact header is not equal to the SIP packet source(IP:port):
      Contact address:10.0.4.62:5060
      Received from :10.0.4.62:34267
   Leg L:773.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505717~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453589] is terminated: Cause: BYE from PBX
   Leg L:773.2[Extn:200] is terminated: Cause: 488 Not Acceptable Here/INVITE from 10.0.7.127:5063
   L:773.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505717~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453589] failed to reach Extn:200, reason Not Acceptable HereReason Unknown
   Call to T:Extn:200@[Dev:sip:[email protected]:5063] from L:773.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505717~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453589] failed, cause: Cause: 488 Not Acceptable Here/INVITE from 10.0.7.127:5063
   [CM503003]: Call(C:773): Call to <sip:[email protected]:5060> has failed; Cause: 488 Not Acceptable Here/INVITE from 10.0.7.127:5063
   [CM503025]: Call(C:773): Calling T:Extn:200@[Dev:sip:[email protected]:5063] for L:773.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505717~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453589]
   [CM503027]: Call(C:773): From: DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505717~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453589 ("SX10 x5506" <sip:[email protected]:5060>)  to  T:Extn:200@[Dev:sip:[email protected]:5063]
   [CM503004]: Call(C:773): Route 1: from L:773.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505717~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453589] to T:Extn:200@[Dev:sip:[email protected]:5063]
   [CM503001]: Call(C:773): Incoming call from DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505717~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453589 to <sip:[email protected]:5060>
   NAT/ALG check:L:773.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505717~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453589] REQUEST 'INVITE' - some of SIP/SDP headers may contain inconsistent information or modified by intermediate hop
   SIP contact header is not equal to the SIP packet source(IP:port):
      Contact address:10.0.4.62:5060
      Received from :10.0.4.62:34267
 
Last edited:
mikegillespie said:
07-Feb-2017 09:35:04.382 Call to T:Extn:200@[Dev:sip:[email protected]:5063] from L:773.1[DirSip:DirectSIP<<"SX10 x5506"<sip:[email protected]>;tag=505717~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453589] failed, cause: Cause: 488 Not Acceptable Here/INVITE from 10.0.7.127:5063
Click to expand...

Are there logs at the CUCM end that might explain what is "not acceptable" when calling Ext 200?

mikegillespie said:
REQUEST 'INVITE' - some of SIP/SDP headers may contain inconsistent information or modified by intermediate hop
SIP contact header is not equal to the SIP packet source(IP:port):
Contact address:10.0.4.62:5060
Received from :10.0.4.62:34267
Click to expand...

This may not be the issue, but would seem to be of concern. Does your router do port substitution?
 
Thanks Guys, I don't believe the router is doing any port substitutions. Also, I will be getting together with the Cisco UCM tech to see what their logs say soon.
I changed the SIP domain in the 3CX to match what the UCM is set for and here are the new logs;

Code: 
; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
07-Feb-2017 20:40:00.858   [Auth] Provided response (16f2bf37b5ecaf6565516e43dbb5a5bb doesn't match calc. (f7e1d9307effff98328414f8f3141632)
07-Feb-2017 20:39:59.532   [CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:
Invite-UNK Recv Req INVITE from 10.0.4.62:44784 tid=1a96349d57ac4 [email protected]:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/TCP 10.0.4.62:5060;branch=z9hG4bK1a96349d57ac4
Max-Forwards: 69
Contact: <sip:[email protected]:5060;transport=tcp>;video;audio;+multiple-codecs-in-ans
To: <sip:[email protected]>
From: "SX10 x5506"<sip:[email protected]>;tag=512426~5dea1feb-fd7f-4c03-9dee-7de56557612c-21453665
Call-ID: [email protected]
CSeq: 101 INVITE
Expires: 180
Session-Expires: 1800
Min-SE: 1800
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=IMMERSIVE
Date: Wed, 08 Feb 2017 00:39:59 GMT
Supported: timer, resource-priority, replaces, X-cisco-srtp-fallback, X-cisco-original-called
User-Agent: Cisco-CUCM11.5
Allow-Events: presence
P-Asserted-Identity: "SX10 x5506" <sip:[email protected]>
Content-Length: 0
Remote-Party-ID: "SX10 x5506" <sip:[email protected]>;party=calling;screen=yes;privacy=off
Session-ID: 7b4a226d20e8fe93440723fcaa512425;remote=00000000000000000000000000000000
Cisco-Guid: 0492330752-0000065536-0000000481-1040449546
07-Feb-2017 20:39:31.112   [CM504001]: Endpoint Extn:202: new contact is registered. Contact(s): [sip:[email protected]:5063 / 202]
07-Feb-2017 20:39:30.611   [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from 10.0.0.65:5060 tid=56d5ce739d5d5ae8c176dbbb620d8463 Call-

[email protected]:
REGISTER sip:10.10.150.20 SIP/2.0
Via: SIP/2.0/UDP 10.0.0.65:5060;branch=z9hG4bK56d5ce739d5d5ae8c176dbbb620d8463
Max-Forwards: 70
Contact: <sip:[email protected]:5060>
To: <sip:[email protected]>
From: "Fax Server"<sip:[email protected]:5060>;tag=5f391d48
Call-ID: [email protected]
CSeq: 53698 REGISTER
Expires: 1200
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, REFER
Organization: Lindsay Construction
Proxy-Authorization: Digest

username="104",realm="3CXPhoneSystem",uri="sip:10.10.150.20",nonce="414d535c0eaaf9c200:5646da61b9cf8a4faca3b9dc9fe785b7",response="5679a32bc8a908740cb6237fe751d616",al

gorithm=MD5
Supported: timer
User-Agent: www.te-systems.de XCAPI V3.3.185.0
Content-Length: 0
X-XCAPI-UUID: BC76432F01D27A04802A23BE84E16CD6

; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
07-Feb-2017 20:39:30.611   [Auth] Provided response (5679a32bc8a908740cb6237fe751d616 doesn't match calc. (9adac5fea3d90d6cff68837552c7463c)
07-Feb-2017 20:39:30.383   [CM504001]: Endpoint Extn:201: new contact is registered. Contact(s): [sip:[email protected]:5063 / 201]
07-Feb-2017 20:39:00.543   [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from 10.0.0.65:5060 tid=06fad0643ffe739a3aab9e5ae5084711 Call-

[email protected]:
REGISTER sip:10.10.150.20 SIP/2.0
Via: SIP/2.0/UDP 10.0.0.65:5060;branch=z9hG4bK06fad0643ffe739a3aab9e5ae5084711
Max-Forwards: 70
Contact: <sip:[email protected]:5060>
To: <sip:[email protected]>
From: "Fax Server"<sip:[email protected]:5060>;tag=5f391d48
Call-ID: [email protected]
CSeq: 53696 REGISTER
Expires: 1200
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, REFER
Organization: Lindsay Construction
Proxy-Authorization: Digest

username="104",realm="3CXPhoneSystem",uri="sip:10.10.150.20",nonce="414d535c0eaaf9a471:88dbf46cf1e2df850e11e02745aa2d60",response="bc53c02058d2be650949711de3188c47",al

gorithm=MD5
Supported: timer
User-Agent: www.te-systems.de XCAPI V3.3.185.0
Content-Length: 0
X-XCAPI-UUID: BC76432F01D27A04802A23BE84E16CD6

; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
07-Feb-2017 20:39:00.543   [Auth] Provided response (bc53c02058d2be650949711de3188c47 doesn't match calc. (f9f9d09a8c7283a29377d93d6364f9a3)
07-Feb-2017 20:38:30.386   [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from 10.0.0.65:5060 tid=1bff0962ca3626b0bb41330af5968fce Call-

[email protected]:
REGISTER sip:10.10.150.20 SIP/2.0
Via: SIP/2.0/UDP 10.0.0.65:5060;branch=z9hG4bK1bff0962ca3626b0bb41330af5968fce
Max-Forwards: 70
Contact: <sip:[email protected]:5060>
To: <sip:[email protected]>
From: "Fax Server"<sip:[email protected]:5060>;tag=5f391d48
Call-ID: [email protected]
CSeq: 53694 REGISTER
Expires: 1200
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, REFER
Organization: Lindsay Construction
Proxy-Authorization: Digest

username="104",realm="3CXPhoneSystem",uri="sip:10.10.150.20",nonce="414d535c0eaaf98688:06c0f15f472acbe4a1a0ec6a8b59dad6",response="f65c43877478f2fab2415c50d02d9874",al

gorithm=MD5
Supported: timer
User-Agent: www.te-systems.de XCAPI V3.3.185.0
Content-Length: 0
X-XCAPI-UUID: BC76432F01D27A04802A23BE84E16CD6

; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
07-Feb-2017 20:38:30.386   [Auth] Provided response (f65c43877478f2fab2415c50d02d9874 doesn't match calc. (b9b8065eedf497237f67b2f90f0ae66d)
07-Feb-2017 20:38:05.059   Leg L:5.1[Extn:195] is terminated: Cause: BYE from PBX
07-Feb-2017 20:38:05.023   [CM503020]: Call(C:5): Normal call termination. Call originator: Extn:195. Reason: Terminated
07-Feb-2017 20:38:05.023   L:5.1[Extn:195] failed to reach Line:10002>>5506, reason Not Acceptable HereReason Unknown
07-Feb-2017 20:38:05.023   Leg L:5.2[Line:10002>>5506] is terminated: Cause: 401 Unauthorized/INVITE from 10.0.4.62:5060
07-Feb-2017 20:38:05.023   Call to T:Line:10002>>5506@[Dev:sip:[email protected]:5060] from L:5.1[Extn:195] failed, cause: Cause: 401 Unauthorized/INVITE from

10.0.4.62:5060
07-Feb-2017 20:38:04.867   [CM503003]: Call(C:5): Call to <sip:[email protected]:5060> has failed; Cause: 401 Unauthorized/INVITE from 10.0.4.62:5060
07-Feb-2017 20:38:04.664   [CM503025]: Call(C:5): Calling T:Line:10002>>5506@[Dev:sip:[email protected]:5060] for L:5.1[Extn:195]
07-Feb-2017 20:38:04.606   [CM503027]: Call(C:5): From: Extn:195 ("Test User" <sip:[email protected]:5060>)  to  T:Line:10002>>5506@[Dev:sip:[email protected]:5060]
07-Feb-2017 20:38:04.606   [CM503004]: Call(C:5): Route 2: from L:5.1[Extn:195] to T:Line:10002>>5506@[Dev:sip:[email protected]:5060]
07-Feb-2017 20:38:04.606   Line limit check: Current # of calls for line Lc:10002(@CUCM Trunk[<sip:[email protected]:5060>]) is 0; limit is 10
07-Feb-2017 20:38:04.606   [CM503026]: Call(C:5): Route 1 to PBXlineCUCM is not active (Busy/Not registered)
07-Feb-2017 20:38:04.606   Call(C:5): from L:5.1[Extn:195]: There are no available outbound lines on Trunk 'PBXlineCUCM' at this time. First line: 10000
07-Feb-2017 20:38:04.562   [CM303003]: There are no available outbound lines on gateway CUCM at this time. First line: Lc:10000(@CUCM[<sip:10000@:5060>])
07-Feb-2017 20:38:04.562   Line limit check: Current # of calls for line Lc:10000(@CUCM[<sip:10000@:5060>]) is 0; limit is 10
07-Feb-2017 20:38:04.562   Call(C:5): Call from Extn:195 to 5506 matches outbound rule 'Rule for CUCM'
07-Feb-2017 20:38:04.561   [CM503001]: Call(C:5): Incoming call from Extn:195 to <sip:[email protected]:5060>
07-Feb-2017 20:38:04.561   NAT/ALG check:L:5.1[Extn:195] REQUEST 'INVITE' - basic check passed. No information for extended checks
07-Feb-2017 20:38:00.284   [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from 10.0.0.65:5060 tid=5f2a21d3573fc04a21623c2a771bd582 Call-

[email protected]:
REGISTER sip:10.10.150.20 SIP/2.0
 
Status
Not open for further replies.

Latest Posts

Members Online Now

Total: 430 (members: 18, guests: 412)

Forum statistics

Threads
111,853
Messages
589,395
Members
164,692
Latest member
FuturaBerlin
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom