Jump to content
Калькуляторы

CCM 8 Transfer SIP Calls

Всем привет.

Есть Cisco Call Manager 8 версии и Cisco 28ХХ.

Когда с CCM звоню через SIP, через Cisco SIP to SIP на SIP провайдера, и когда хочу перевести звонок на внутреннего абонента хочу кнопкой трансфер с телефона SCCP.

Жамкую просто кнопку transfer не набирая ни чего, вижу уже SIP пакеты на Cisco

 

voice-router#
Nov 22 10:15:30.999: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:87051231212@10.10.20.253:5060 SIP/2.0
Via: SIP/2.0/UDP 10.10.20.252:5060;branch=z9hG4bK713897b1e6240
From: <sip:77212922222@10.10.20.252>;tag=c834a7d7-9a2a-44e6-a9c7-bdc36f2f6d58-25537838
To: <sip:87051231212@10.10.20.253>;tag=235C68-1A0B
Date: Fri, 22 Nov 2013 10:10:38 GMT
Call-ID: 4157d880-28f12d7e-43b1-fc140a0a@10.10.20.252
Supported: timer,resource-priority,replaces
Min-SE:  1800
User-Agent: Cisco-CUCM8.0
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 102 INVITE
Max-Forwards: 70
Contact: <sip:77212922222@10.10.20.252:5060>
Expires: 180
Allow-Events: presence, kpml
Supported: X-cisco-srtp-fallback
Supported: Geolocation
P-Asserted-Identity: <sip:77212922222@10.10.20.252>
Content-Type: application/sdp
Content-Length: 219

v=0
o=CiscoSystemsCCM-SIP 2000 3 IN IP4 10.10.20.252
s=SIP Call
c=IN IP4 0.0.0.0
t=0 0
m=audio 32696 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=ptime:20
a=inactive
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

Nov 22 10:15:31.003: //344/4157D8800000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.10.20.252:5060;branch=z9hG4bK713897b1e6240
From: <sip:77212922222@10.10.20.252>;tag=c834a7d7-9a2a-44e6-a9c7-bdc36f2f6d58-25537838
To: <sip:87051231212@10.10.20.253>;tag=235C68-1A0B
Date: Fri, 22 Nov 2013 10:15:30 GMT
Call-ID: 4157d880-28f12d7e-43b1-fc140a0a@10.10.20.252
CSeq: 102 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0


Nov 22 10:15:31.003: //345/4157D8800000/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:87051231212@8.9.136.2:5060 SIP/2.0
Via: SIP/2.0/UDP 8.9.137.194:5060;branch=z9hG4bK11072C
From: <sip:77212922222@8.9.137.194>;tag=2347E0-839
To: <sip:87051231212@8.9.136.250>;tag=6F1151BC-14A9
Date: Fri, 22 Nov 2013 10:15:31 GMT
Call-ID: C6E0458B-529511E3-81DF8A3D-55AA6B37@8.9.137.194
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 1096276096-0000065536-0000017329-4229171722
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 102 INVITE
Max-Forwards: 70
Timestamp: 1385115331
Contact: <sip:77212922222@8.9.137.194:5060>
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 255

v=0
o=CiscoSystemsSIP-GW-UserAgent 6529 8223 IN IP4 8.9.137.194
s=SIP Call
c=IN IP4 8.9.137.194
t=0 0
m=audio 21846 RTP/AVP 8 100
c=IN IP4 8.9.137.194
a=inactive
a=rtpmap:8 PCMA/8000
a=rtpmap:100 X-NSE/8000
a=fmtp:100 192-194
a=ptime:20

Nov 22 10:15:31.007: //345/4157D8800000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 8.9.137.194:5060;branch=z9hG4bK11072C
From: <sip:77212922222@8.9.137.194>;tag=2347E0-839
To: <sip:87051231212@8.9.136.250>;tag=6F1151BC-14A9
Date: Fri, 22 Nov 2013 10:15:00 GMT
Call-ID: C6E0458B-529511E3-81DF8A3D-55AA6B37@8.9.137.194
Timestamp: 1385115299
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 102 INVITE
Allow-Events: telephone-event
Content-Length: 0


Nov 22 10:15:31.059: //345/4157D8800000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 8.9.137.194:5060;branch=z9hG4bK11072C
From: <sip:77212922222@8.9.137.194>;tag=2347E0-839
To: <sip:87051231212@8.9.136.250>;tag=6F1151BC-14A9
Date: Fri, 22 Nov 2013 10:15:00 GMT
Call-ID: C6E0458B-529511E3-81DF8A3D-55AA6B37@8.9.137.194
Server: Cisco-SIPGateway/IOS-12.x
Timestamp: 1385115331
CSeq: 102 INVITE
Allow-Events: telephone-event
Contact: <sip:87051231212@8.9.136.2:5060>
Content-Type: application/sdp
Content-Length: 227

v=0
o=CiscoSystemsSIP-GW-UserAgent 3504 6999 IN IP4 8.9.136.2
s=SIP Call
c=IN IP4 8.9.136.2
t=0 0
m=audio 19250 RTP/AVP 8
c=IN IP4 8.9.136.2
a=inactive
a=rtpmap:8 PCMA/8000
a=ptime:20
a=silenceSupp:off - - - -

Nov 22 10:15:31.063: //345/4157D8800000/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:87051231212@8.9.136.2:5060 SIP/2.0
Via: SIP/2.0/UDP 8.9.137.194:5060;branch=z9hG4bK11113D1
From: <sip:77212922222@8.9.137.194>;tag=2347E0-839
To: <sip:87051231212@8.9.136.250>;tag=6F1151BC-14A9
Date: Fri, 22 Nov 2013 10:15:31 GMT
Call-ID: C6E0458B-529511E3-81DF8A3D-55AA6B37@8.9.137.194
Max-Forwards: 70
CSeq: 102 ACK
Allow-Events: telephone-event
Content-Length: 0


Nov 22 10:15:31.063: //344/4157D8800000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.10.20.252:5060;branch=z9hG4bK713897b1e6240
From: <sip:77212922222@10.10.20.252>;tag=c834a7d7-9a2a-44e6-a9c7-bdc36f2f6d58-25537838
To: <sip:87051231212@10.10.20.253>;tag=235C68-1A0B
Date: Fri, 22 Nov 2013 10:15:30 GMT
Call-ID: 4157d880-28f12d7e-43b1-fc140a0a@10.10.20.252
CSeq: 102 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: <sip:87051231212@10.10.20.253>;party=called;screen=no;privacy=off
Contact: <sip:87051231212@10.10.20.253:5060>
Supported: replaces
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-12.x
Supported: timer
Content-Type: application/sdp
Content-Length: 259

v=0
o=CiscoSystemsSIP-GW-UserAgent 7567 3227 IN IP4 10.10.20.253
s=SIP Call
c=IN IP4 10.10.20.253
t=0 0
m=audio 18880 RTP/AVP 8 101
c=IN IP4 10.10.20.253
a=inactive
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20

Nov 22 10:15:31.063: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:87051231212@10.10.20.253:5060 SIP/2.0
Via: SIP/2.0/UDP 10.10.20.252:5060;branch=z9hG4bK7138a623ff8a0
From: <sip:77212922222@10.10.20.252>;tag=c834a7d7-9a2a-44e6-a9c7-bdc36f2f6d58-25537838
To: <sip:87051231212@10.10.20.253>;tag=235C68-1A0B
Date: Fri, 22 Nov 2013 10:10:38 GMT
Call-ID: 4157d880-28f12d7e-43b1-fc140a0a@10.10.20.252
Max-Forwards: 70
CSeq: 102 ACK
Allow-Events: presence, kpml
Content-Length: 0


Nov 22 10:15:31.067: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:87051231212@10.10.20.253:5060 SIP/2.0
Via: SIP/2.0/UDP 10.10.20.252:5060;branch=z9hG4bK7138b5948261a
From: <sip:77212922222@10.10.20.252>;tag=c834a7d7-9a2a-44e6-a9c7-bdc36f2f6d58-25537838
To: <sip:87051231212@10.10.20.253>;tag=235C68-1A0B
Date: Fri, 22 Nov 2013 10:10:38 GMT
Call-ID: 4157d880-28f12d7e-43b1-fc140a0a@10.10.20.252
Supported: timer,resource-priority,replaces
Min-SE:  1800
User-Agent: Cisco-CUCM8.0
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 103 INVITE
Max-Forwards: 70
Contact: <sip:77212922222@10.10.20.252:5060>
Expires: 180
Allow-Events: presence, kpml
Supported: X-cisco-srtp-fallback
Supported: Geolocation
P-Asserted-Identity: <sip:77212922222@10.10.20.252>
Content-Length: 0


Nov 22 10:15:31.071: //344/4157D8800000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.10.20.252:5060;branch=z9hG4bK7138b5948261a
From: <sip:77212922222@10.10.20.252>;tag=c834a7d7-9a2a-44e6-a9c7-bdc36f2f6d58-25537838
To: <sip:87051231212@10.10.20.253>;tag=235C68-1A0B
Date: Fri, 22 Nov 2013 10:15:31 GMT
Call-ID: 4157d880-28f12d7e-43b1-fc140a0a@10.10.20.252
CSeq: 103 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0


Nov 22 10:15:31.071: //345/4157D8800000/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:87051231212@8.9.136.2:5060 SIP/2.0
Via: SIP/2.0/UDP 8.9.137.194:5060;branch=z9hG4bK112B3
From: <sip:77212922222@8.9.137.194>;tag=2347E0-839
To: <sip:87051231212@8.9.136.250>;tag=6F1151BC-14A9
Date: Fri, 22 Nov 2013 10:15:31 GMT
Call-ID: C6E0458B-529511E3-81DF8A3D-55AA6B37@8.9.137.194
Supported: timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 1096276096-0000065536-0000017329-4229171722
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 103 INVITE
Max-Forwards: 70
Timestamp: 1385115331
Contact: <sip:77212922222@8.9.137.194:5060>
Expires: 180
Allow-Events: telephone-event
Content-Length: 0


Nov 22 10:15:31.079: //345/4157D8800000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 8.9.137.194:5060;branch=z9hG4bK112B3
From: <sip:77212922222@8.9.137.194>;tag=2347E0-839
To: <sip:87051231212@8.9.136.250>;tag=6F1151BC-14A9
Date: Fri, 22 Nov 2013 10:15:00 GMT
Call-ID: C6E0458B-529511E3-81DF8A3D-55AA6B37@8.9.137.194
Timestamp: 1385115299
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 103 INVITE
Allow-Events: telephone-event
Content-Length: 0

 

Получается Cisco пытается сообщить оператору, что будет перевод, хотя 302 message я и не вижу, да и не нужно мне такое.

 

Добавил в конфиги вот такое, но воз и ныне там

 

voice service voip

no supplementary-service sip refer

no supplementary-service sip moved-temporarily

 

И удалил

no redirect ip2ip

Share this post


Link to post
Share on other sites

"Жамкую просто кнопку transfer "

 

sip стек информирует удаленную сторону, что вызов поставлен на удержание и нет смысла отсылать данные.

Share this post


Link to post
Share on other sites

sip стек информирует удаленную сторону, что вызов поставлен на удержание и нет смысла отсылать данные.

 

Весь лог который я выложил, это реакция на нажатие кнопки трансфер, это не на набор на номер куда-то.

Я набрал 87051231212 с 77212922222, дозвонился, жамкнул на трансфер и посыпался лог в ветке.

Т.е. я так понял, Cisco-CUCM8.0 говорит циске переводи вызов, вот тебе инвайты, а циска в свою очередь пытается это отправить оператору, получается фигня полная.

Как это отключается, что бы ни кто не знал, что есть перевод вызова внутри Cisco-CUCM8.0

Share this post


Link to post
Share on other sites

В двух словах заходим в настройки шлюза, в частности SIP транка на Cisco 29XX и тыкаем на галку на против Media Termination Point (или снимаем) и чудный CUCM8.0 начинает внутри себя делать и трансфер и транскодить по ходу тоже?

Share this post


Link to post
Share on other sites

Потому что, первый раз вижу это (колманагер), и почитав немного документов по сему (MTP), понял, что я это вижу в первый раз и могу допустить любые ошибки ).

Умозаключение верное сделал в прошлом посте?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this