Hi all ...
My name is Majdi Al-Qatatsheh from BTC Jordan, Avaya Golden Partner.
I have Configured a SIP Trunk between Avaya IP Offcce 500v2 Rls 8.1 and on the Royal Wings to the Cisco Call Manager Rls.7 on Royal Jordanian.
I have an issue on call completion and hope to find the solution on this fourm.
first, Here is the information about setup:
IP Office IP Address: 10.10.89.10
Cisco Call Manager IP Address:10.10.240.1
IP Office Extension Range: 33xx
Cisco Call Manager Extension Range: 2xxx
IP Office ARS: 2N"@10.10.240.1"
We follow the following document in the configuration:
After completion, the SIP Trunk is up, and the Cisco Users can call the IP Office Users, but in vise versa, when calling from Avaya Phone, it's displays "incompatible" Message.
the following is the trace I capture it from Moniter when I call extension number 2888 on the cisco call manager:
72430mS SIP Tx: TCP 10.1.68.10:5060 -> 10.10.240.1:5060
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/TCP 10.1.68.10:5060;rport;branch=z9hG4bK74b94ee30671bb a6942063bffcc56c0c
From: "Alaa Sammamah" <sip:[email protected]>;tag=fee68729789c201c
To: <sip:[email protected]>
Call-ID: 41e907b1e3423a20dfa5accb231c2fe4
CSeq: 630221668 INVITE
Contact: "Alaa Sammamah" <sip:[email protected]:5060;transport=tcp>
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
Content-Type: application/sdp
Supported: timer
User-Agent: IP Office 8.1 (43)
Content-Length: 271
v=0
o=UserA 3612928582 3500921764 IN IP4 10.1.68.10
s=Session SDP
c=IN IP4 10.1.68.10
t=0 0
m=audio 49154 RTP/AVP 8 0 18 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
72431mS CD: CALL: 252.1005.0 BState=Idle Cut=0 Music=0.0 Aend="Alaa Sammamah(3330)" (0.0) Bend="Line 17" [Line 17] (0.0) CalledNum=2888 () CallingNum=3330 (Alaa Sammamah) Internal=0 Time=809 AState=Dialling
72446mS SIP Rx: TCP 10.10.240.1:5060 -> 10.1.68.10:5060
SIP/2.0 100 Trying
Date: Sun, 29 Sep 2013 11:53:50 GMT
From: "Alaa Sammamah" <sip:[email protected]>;tag=fee68729789c201c
Allow-Events: presence
Content-Length: 0
To: <sip:[email protected]>
Call-ID: 41e907b1e3423a20dfa5accb231c2fe4
Via: SIP/2.0/TCP 10.1.68.10:5060;rport;branch=z9hG4bK74b94ee30671bb a6942063bffcc56c0c
CSeq: 630221668 INVITE
72449mS CMLineRx: v=0
CMProceeding
Line: type=SIPLine 17 Call: lid=17 id=1007 in=0
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:0 N:100 R:4) number=2888
IE CMIEDeviceDetail (231) LOCALE=ara HW=15 VER=8 class=CMDeviceSIPTrunk type=0 number=17 channel=1 rx_gain=32 tx_gain=32 ep_callid=1007 ipaddr=10.1.68.10 apps=0
72449mS CMCallEvt: 0.1006.0 2 TargetingEP: RequestEnd 17.1007.0 2 SIPTrunk Endpoint
72449mS CMTARGET: 252.1005.0 2 Alaa Sammamah.0: CancelTimer CMTCNoAnswerTimeout
72449mS CMCallEvt: 0.1006.0 -1 BaseEP: DELETE CMEndpoint f4e5c3b0 TOTAL NOW=2 CALL_LIST=1
72449mS CMCallEvt: 17.1007.0 2 SIPTrunk Endpoint: StateChange: END=B CMCSOffering->CMCSAccept
72450mS CMCallEvt: 252.1005.0 2 Alaa Sammamah.0: StateChange: END=A CMCSDialling->CMCSDialled
72450mS CMExtnEvt: v=1 State, new=Proceeding old=Dialling,0,0,Alaa Sammamah
72451mS CMExtnTx: v=3330, p1=0
CMFacility
Line: type=IPLine 250 Call: lid=252 id=1005 in=0
IE CMIEFastStartInfoData (6) 2 item(s)
Timed: 29/09/13 14:51
72452mS CMExtnTx: v=3330, p1=8001
CMFacility
Line: type=IPLine 250 Call: lid=252 id=1 in=1
IE CMIEFastStartInfoData (6) 2 item(s)
72452mS CMExtnTx: v=3330, p1=0
CMProceeding
Line: type=IPLine 250 Call: lid=252 id=1005 in=0
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:0 N:100 R:4) number=2888
IE CMIEDeviceDetail (231) LOCALE=ara HW=15 VER=8 class=CMDeviceSIPTrunk type=0 number=17 channel=1 rx_gain=32 tx_gain=32 ep_callid=1007 ipaddr=10.1.68.10 apps=0
Timed: 29/09/13 14:51
72454mS CD: CALL: 252.1005.0 BState=Ringing Cut=3 Music=0.0 Aend="Alaa Sammamah(3330)" (0.0) Bend="Line 17" [Line 17] (0.0) [email protected] () CallingNum=3330 (Alaa Sammamah) Internal=0 Time=832 AState=Dialled
72456mS SIP Rx: TCP 10.10.240.1:5060 -> 10.1.68.10:5060
SIP/2.0 404 Not Found
Reason: Q.850;cause=1
Date: Sun, 29 Sep 2013 11:53:50 GMT
From: "Alaa Sammamah" <sip:[email protected]>;tag=fee68729789c201c
Allow-Events: presence
Content-Length: 0
To: <sip:[email protected]>;tag=ed8670f9-bccc-48ab-a850-c066054d2648-51165869
Call-ID: 41e907b1e3423a20dfa5accb231c2fe4
Via: SIP/2.0/TCP 10.1.68.10:5060;rport;branch=z9hG4bK74b94ee30671bb a6942063bffcc56c0c
CSeq: 630221668 INVITE
72460mS SIP Tx: TCP 10.1.68.10:5060 -> 10.10.240.1:5060
ACK sip:[email protected] SIP/2.0
Via: SIP/2.0/TCP 10.1.68.10:5060;rport;branch=z9hG4bK74b94ee30671bb a6942063bffcc56c0c
From: "Alaa Sammamah" <sip:[email protected]>;tag=fee68729789c201c
To: <sip:[email protected]>;tag=ed8670f9-bccc-48ab-a850-c066054d2648-51165869
Call-ID: 41e907b1e3423a20dfa5accb231c2fe4
CSeq: 630221668 ACK
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
User-Agent: IP Office 8.1 (43)
Content-Length: 0
********** Warning: Logging to Screen Stopped **********
I think this is the problem:
Cause=1, Unallocated (unassigned) number
The number 2888 is not configured in the Cisco call Manager correctly.
That is why I received a 404 Not found.
Is this analysis true, if this mean i need to configure some kind of URI on the Cisco side.
Can I found a suggestion on How to do this on the cisco call manager ?
Regards,
Eng Majdi Al-Qatatsheh
Senior Support Engineer
My name is Majdi Al-Qatatsheh from BTC Jordan, Avaya Golden Partner.
I have Configured a SIP Trunk between Avaya IP Offcce 500v2 Rls 8.1 and on the Royal Wings to the Cisco Call Manager Rls.7 on Royal Jordanian.
I have an issue on call completion and hope to find the solution on this fourm.
first, Here is the information about setup:
IP Office IP Address: 10.10.89.10
Cisco Call Manager IP Address:10.10.240.1
IP Office Extension Range: 33xx
Cisco Call Manager Extension Range: 2xxx
IP Office ARS: 2N"@10.10.240.1"
We follow the following document in the configuration:
After completion, the SIP Trunk is up, and the Cisco Users can call the IP Office Users, but in vise versa, when calling from Avaya Phone, it's displays "incompatible" Message.
the following is the trace I capture it from Moniter when I call extension number 2888 on the cisco call manager:
72430mS SIP Tx: TCP 10.1.68.10:5060 -> 10.10.240.1:5060
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/TCP 10.1.68.10:5060;rport;branch=z9hG4bK74b94ee30671bb a6942063bffcc56c0c
From: "Alaa Sammamah" <sip:[email protected]>;tag=fee68729789c201c
To: <sip:[email protected]>
Call-ID: 41e907b1e3423a20dfa5accb231c2fe4
CSeq: 630221668 INVITE
Contact: "Alaa Sammamah" <sip:[email protected]:5060;transport=tcp>
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
Content-Type: application/sdp
Supported: timer
User-Agent: IP Office 8.1 (43)
Content-Length: 271
v=0
o=UserA 3612928582 3500921764 IN IP4 10.1.68.10
s=Session SDP
c=IN IP4 10.1.68.10
t=0 0
m=audio 49154 RTP/AVP 8 0 18 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
72431mS CD: CALL: 252.1005.0 BState=Idle Cut=0 Music=0.0 Aend="Alaa Sammamah(3330)" (0.0) Bend="Line 17" [Line 17] (0.0) CalledNum=2888 () CallingNum=3330 (Alaa Sammamah) Internal=0 Time=809 AState=Dialling
72446mS SIP Rx: TCP 10.10.240.1:5060 -> 10.1.68.10:5060
SIP/2.0 100 Trying
Date: Sun, 29 Sep 2013 11:53:50 GMT
From: "Alaa Sammamah" <sip:[email protected]>;tag=fee68729789c201c
Allow-Events: presence
Content-Length: 0
To: <sip:[email protected]>
Call-ID: 41e907b1e3423a20dfa5accb231c2fe4
Via: SIP/2.0/TCP 10.1.68.10:5060;rport;branch=z9hG4bK74b94ee30671bb a6942063bffcc56c0c
CSeq: 630221668 INVITE
72449mS CMLineRx: v=0
CMProceeding
Line: type=SIPLine 17 Call: lid=17 id=1007 in=0
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:0 N:100 R:4) number=2888
IE CMIEDeviceDetail (231) LOCALE=ara HW=15 VER=8 class=CMDeviceSIPTrunk type=0 number=17 channel=1 rx_gain=32 tx_gain=32 ep_callid=1007 ipaddr=10.1.68.10 apps=0
72449mS CMCallEvt: 0.1006.0 2 TargetingEP: RequestEnd 17.1007.0 2 SIPTrunk Endpoint
72449mS CMTARGET: 252.1005.0 2 Alaa Sammamah.0: CancelTimer CMTCNoAnswerTimeout
72449mS CMCallEvt: 0.1006.0 -1 BaseEP: DELETE CMEndpoint f4e5c3b0 TOTAL NOW=2 CALL_LIST=1
72449mS CMCallEvt: 17.1007.0 2 SIPTrunk Endpoint: StateChange: END=B CMCSOffering->CMCSAccept
72450mS CMCallEvt: 252.1005.0 2 Alaa Sammamah.0: StateChange: END=A CMCSDialling->CMCSDialled
72450mS CMExtnEvt: v=1 State, new=Proceeding old=Dialling,0,0,Alaa Sammamah
72451mS CMExtnTx: v=3330, p1=0
CMFacility
Line: type=IPLine 250 Call: lid=252 id=1005 in=0
IE CMIEFastStartInfoData (6) 2 item(s)
Timed: 29/09/13 14:51
72452mS CMExtnTx: v=3330, p1=8001
CMFacility
Line: type=IPLine 250 Call: lid=252 id=1 in=1
IE CMIEFastStartInfoData (6) 2 item(s)
72452mS CMExtnTx: v=3330, p1=0
CMProceeding
Line: type=IPLine 250 Call: lid=252 id=1005 in=0
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:0 N:100 R:4) number=2888
IE CMIEDeviceDetail (231) LOCALE=ara HW=15 VER=8 class=CMDeviceSIPTrunk type=0 number=17 channel=1 rx_gain=32 tx_gain=32 ep_callid=1007 ipaddr=10.1.68.10 apps=0
Timed: 29/09/13 14:51
72454mS CD: CALL: 252.1005.0 BState=Ringing Cut=3 Music=0.0 Aend="Alaa Sammamah(3330)" (0.0) Bend="Line 17" [Line 17] (0.0) [email protected] () CallingNum=3330 (Alaa Sammamah) Internal=0 Time=832 AState=Dialled
72456mS SIP Rx: TCP 10.10.240.1:5060 -> 10.1.68.10:5060
SIP/2.0 404 Not Found
Reason: Q.850;cause=1
Date: Sun, 29 Sep 2013 11:53:50 GMT
From: "Alaa Sammamah" <sip:[email protected]>;tag=fee68729789c201c
Allow-Events: presence
Content-Length: 0
To: <sip:[email protected]>;tag=ed8670f9-bccc-48ab-a850-c066054d2648-51165869
Call-ID: 41e907b1e3423a20dfa5accb231c2fe4
Via: SIP/2.0/TCP 10.1.68.10:5060;rport;branch=z9hG4bK74b94ee30671bb a6942063bffcc56c0c
CSeq: 630221668 INVITE
72460mS SIP Tx: TCP 10.1.68.10:5060 -> 10.10.240.1:5060
ACK sip:[email protected] SIP/2.0
Via: SIP/2.0/TCP 10.1.68.10:5060;rport;branch=z9hG4bK74b94ee30671bb a6942063bffcc56c0c
From: "Alaa Sammamah" <sip:[email protected]>;tag=fee68729789c201c
To: <sip:[email protected]>;tag=ed8670f9-bccc-48ab-a850-c066054d2648-51165869
Call-ID: 41e907b1e3423a20dfa5accb231c2fe4
CSeq: 630221668 ACK
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
User-Agent: IP Office 8.1 (43)
Content-Length: 0
********** Warning: Logging to Screen Stopped **********
I think this is the problem:
Cause=1, Unallocated (unassigned) number
The number 2888 is not configured in the Cisco call Manager correctly.
That is why I received a 404 Not found.
Is this analysis true, if this mean i need to configure some kind of URI on the Cisco side.
Can I found a suggestion on How to do this on the cisco call manager ?
Regards,
Eng Majdi Al-Qatatsheh
Senior Support Engineer
