UM integration with 3CX issue. Ringing and no answer

Status
Not open for further replies.

fceledon

Joined
Apr 19, 2010
Messages
6
Reaction score
0
I trying to intergrate the 3cx Ip-PBX with Exchange Server UM. The connection between both systems looks ok, in fact,

Kindly remember to use code and /code tags when posting server logs, this time it has been done for you - MFM


On the 3CX side the sequence is:
Code:
SDP:Request: INVITE sip:[email protected]:5060 SIP/2.0; SDP:SessionName=3cxVCE Audio Call, Version=0, MediaDescription=audio 40016 RTP/AVP 0 8 3 101
SIP:Response: SIP/2.0 100 Trying
SDP:Request: INVITE sip:[email protected]:5060;transport=TCP SIP/2.0; SDP:SessionName=3cxPS Audio call, Version=0, MediaDescription=audio 7086 RTP/AVP 0 8 3 13 18 110 99 101
SIP:Response: SIP/2.0 100 Trying
SIP:Response: SIP/2.0 302 Moved Temporarily
SIP:Request: ACK sip:[email protected]:5060;transport=TCP SIP/2.0
SDP:Request: INVITE sip:[email protected]:5065;transport=TCP SIP/2.0; SDP:SessionName=3cxPS Audio call, Version=0, MediaDescription=audio 7086 RTP/AVP 0 8 3 13 18 110 99 101
SIP:Response: SIP/2.0 100 Trying
SIP:Response: SIP/2.0 180 Ringing
SIP:Response: SIP/2.0 180 Ringing
SIP:Request: CANCEL sip:[email protected]:5065;transport=TCP SIP/2.0
SIP:Response: SIP/2.0 487 Request Terminated
SIP:Response: SIP/2.0 200 OK
.....

On the UM side the sequence is:
Code:
SDP:Request: INVITE sip:[email protected]:5060;transport=TCP SIP/2.0; SDP:SessionName=3cxPS Audio call, Version=0, MediaDescription=audio 7086 RTP/AVP 0 8 3 13 18 110 99 101
SIP:Response: SIP/2.0 100 Trying
SIP:Response: SIP/2.0 302 Moved Temporarily
SDP:Request: INVITE sip:[email protected]:5065;transport=TCP SIP/2.0; SDP:SessionName=3cxPS Audio call, Version=0, MediaDescription=audio 7086 RTP/AVP 0 8 3 13 18 110 99 101
SIP:Response: SIP/2.0 100 Trying
SIP:Response: SIP/2.0 180 Ringing
SIP:Request: CANCEL sip:[email protected]:5065;transport=TCP SIP/2.0
SIP:Response: SIP/2.0 487 Request Terminated
SIP:Response: SIP/2.0 200 OK
SIP:Request: ACK sip:[email protected]:5065;transport=TCP SIP/2.0

Look to me that two consecutives "Ringing" tells the 3cx that nobody is picking up the call and then hangup. Then, why UM is not picking up?

I have 9999 as the Subscriber Access.

Same situation when calling 8000 (The auto attendant extension).

Help is appreciated.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,880
Messages
589,533
Members
164,735
Latest member
998742