Design Question Sip Trunk

Hi,
I have a requirement to move from a h323 environment to a SIP environment. I am looking for best practises especially around security. I have 2 CUCM servers (8.5) located in separate cities for redundancy. I also have 2 voice gateways which at the moment are h323 to the PSTN, each located at different cities.
My requirements are:
1. Creat a sip trunk to the provider instaed of using PRI.
2. If the Wan link fails on one gateway to provider, the alternate router in the other location should be able to receive the setup messages and if a user logs on via extension mobility, should be able to answer the call.
Are there any simplified design docos about for this? I am hesitant to create a SIP trunk straight to the provider for security, so thinking of terminating the call on the voice routers with CUBE. I'm pretty sure this is run of the mill and would appreciate some input.
Cheers!
Pieter

+5 to Chris..Always use CUBE...
Here are more ideas..
1. Create two sip trunks, first one to Cube 1, second to CUBE 2
on your sip trunk set DTMF as no preference
2. Assign the trunks to CUCM group with your two servers in it
3. Configure route groups with Circular algorithm distribution (this way you have load balancing on your two cubes)
4. Configure dial-peers on your CUBE gateway to point in preferential order to your cucm servers
5. Use dtmf-relay rtp-nte on your dial-peer (ensure you have sip as the protocol on your dial-peers)
6. configure your codec selection properly on your dial-peers
7. configure your region settings properly between your sip trunk and phones.
8. Evaluate if you need xcoders, provide one if you do and ensure you set your region correctly between your xcoder and CUBE
9. Is there voicemail involved? Ensure you set your region settings between cube and voicemail correctly, otherwise calls to voicemail may invoke xcoder (from experience)
10. Provision adequate bandwidth for your calls. Once you move to sip, you loose the luxury of e1 channels. You are solely relying on Bandwidth. Ensure you have adequate bandwidth for your concurrent calls
11. Provision QoS for your calls
12. Is there fax involved? You need to think carefully on this one. What fax method do you want to use. T.38/pass through. Does your provider support T.38?
13. Have a thorough test plan. Test call transfers, call on hold, call forward etc
Just a few pointers..Careful planning and implementation is required for a successful SIP implementation

Similar Messages

SIP Trunk Question - Outbound Calls Fail

Hi Folks,
I am using a Cisco 2821 as a router that will convert a SIP trunk to an E1 PRI. Si my setup is:
SIp-Trunk > 2821 Router > E1 port on 3900> CUCM
Inbound calls are working fine, but outbound are failing. I am starting to think its due to transcoding issue on the SIP-GW maybe (there is nothing configured on it for XCODE etc).
I think my configuration is fine as I am able to recieve calls inbound. Just outbound fail.
Here are the debugs from the SIP-GW:
"Debug CCSIP calls"
*Nov 26 18:50:50 UTC: //929/F9E88693801B/SIP/Call/sipSPICallInfo:
The Call Setup Information is:
Call Control Block (CCB) : 0x4BB4F194
State of The Call : STATE_DEAD
TCP Sockets Used : NO
Calling Number : 1528xxxx
Called Number : 909
Source IP Address (Sig ): 172.29.x.xxx
Destn SIP Req Addr:Port : 10.200.7.157:5060
Destn SIP Resp Addr:Port : 10.200.7.157:5060
Destination Name : 10.200.7.157
*Nov 26 18:50:50 UTC: //929/F9E88693801B/SIP/Call/sipSPIMediaCallInfo:
Number of Media Streams: 1
Media Stream : 1
Negotiated Codec : No Codec
Negotiated Codec Bytes : 0
Nego. Codec payload : 255 (tx), 255 (rx)
Negotiated Dtmf-relay : 0
Dtmf-relay Payload : 0 (tx), 0 (rx)
Source IP Address (Media): 172.29.5.210
Source IP Port (Media): 16786
Destn IP Address (Media): -
Destn IP Port (Media): 0
Orig Destn IP Address:Port (Media): [ - ]:0
*Nov 26 18:50:50 UTC: //929/F9E88693801B/SIP/Call/sipSPICallInfo:
Disconnect Cause (CC) : 28
Disconnect Cause (SIP) : 484
Can anyone shed some light on the area that I need to focus on? This is my first attempt at SIP and I am confused :)
Thanks.

Hi
909 is what I meant to dial as that is the help desk for the telco.
I tried mobile numbers as well getting the same error codes. And international numbers.
If it's based on the called number being wrong then I guess I will have to play with the calling party ID and call type as well... Maybe this is causing it to fail??

SIP Trunks - SME

Hello,
We are in stage of configuring SIP Trunk between 2 CUCM clusters (cluster A & cluster B ) via SME.
Can any body help how to configure incoming & outgoing calls on SME using SIP ?
For Example:
For a call from user A (cluster A) to user B (cluster B)
User A from Cluster A will use Route Pattern for outgoing calls, what parameters need to be configure in SME to answer call coming from cluster A ?
Then for SME outgoing call towards cluster B, do we need to configure RP ? In cluster B what parameters need to be configure to answer call coming from SME ?
I am trying to understand the call leg step by step from one CUCM cluster to other through SME.
We have 3 Digits of extension in Cluster A & we have 4 Digits of extension in Cluster B.
Full numbers of ip phone in each cluster is 8 Digit & we want 8 digit calling pattern to call from cluster A to B & vice versa.
Thank in advance.
Regards,
Conie

Got it.
We have only one SME server at time & we are planning to use Inter-cluster trunk between clusters as backup incase if SME stop working for any malfunctioning reason.
For inter-cluster trunks we will have :
1- Inter-Cluster trunk in Cluster A point to Cluster B ?
2- Inter-Cluster trunk in Cluster B point to Cluster A ?
3- In cluster A RL, set inter-cluster trunk for cluster B as secondary ?
4- In cluster B RL, set inter-cluster trunk for cluster A as secondary ?
should i use same calling approach as we discussed above via Route Patterns only ?
As we have CUCM 8.6 in both clusters, we are planning to use H.323 Inter-Cluster (Non Gatekeeper) Trunk as backup.
And PSTN lines as backup for H.323 Inter-cluster.
Do you have any comments regarding our design ? are we on right track with this failover approach ?
Regards,
Conie
Thank you to being answering my questions appreciated your answers helped me alot.

Please confirm.. Whether Cisco CCM support SIP trunking !

Hi,
We r in the process of VoIP implementation nd during that phase came to know that Cisco doesn't support SIP trunking at gateway level.. Can anyone suggest me whether it's true or not??? Cisco says its support SIP then what is the meaning of that?? I m really confused with the twisting of words in different docs...

Thanks to all of you for your reply...When you say SIP trunking is supported then whether I can use SIP at gateway level towards making outward call.. Sorry if I am getting confused myself but when one says SIP trunking is supported what's the mean of that?? If I have a trunk line(PSTN) and a T1 line acting as a gateway, is it possible to design a network only depending upon SIP protocol using CISCO UNIFIED Components and call manager 5.0 ??
Sorry once again if my question sound something ..... but it just to clear my confusion too as I am listening so many stuff from different people when it comes to SIP overall implementation for a Enterprise network using CISCO Unified communication equipments...
With best regards,
Mani

Unable to place call on calls on hold - SIP Trunk from CUCM to CUBE and from CUBE to ISTP

Hi Cisco Community,
I have a SIP Trunk setup between the CUCM and CUBE and another SIP Dial Peers from the CUBE to the ITSP. All incoming/outgoing calls, DTMF-Relay works well except one thing which is the ability to hold the call.
On the SIP Trunk from the CUCM to the CUBE, I did not select “MTP” because when I do so, I am forced to select my preferred MTP codec which when selected G.729/G.729a, all my outgoing calls goes out using G.729r8. This codec works well for most of the calls until the ITSP replies back with G.729br8. When this condition occur, my call simply fails (this is very intermittent and only some random numbers).
That said, I have some issues with DTMF Relay when I select MTP on the SIP Trunk. DTMF Relay only works if the call is G.729r8 all the way from the CUCM to the ITSP. If the ITSP replies back with G.729br8, the call might established but will simply be “voice-only”.
The current setup is no MTP is selected and everything is working perfectly. I am happy with that until I place a call on hold, which when I do so, the call immediately terminate. Could you please help me understand why?
I have all media resources configured such as G.729r8 MTP, G.729br8 MTP, G.711u MTP, Transcoding with all codecs, etc. All MRG and MRGL are configured on all devices and SIP Trunks.
Below is an example of a call that is connected with the current setup:
Note:
IP: 10.18.81.2 (CUBE)
IP: 10.18.81.11 (CUCM SUB)
IP: 10.111.111.254 (ITSP SBC)
PM-HO-VG-01#
PM-HO-VG-01#
Nov 30 11:44:29.938: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.18.81.11:5060;branch=z9hG4bK2e72063a5aba5d
From: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
To: <sip:[email protected]>
Date: Sun, 30 Nov 2014 11:44:29 GMT
Call-ID: [email protected]
Supported: timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM9.1
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence, kpml
Supported: X-cisco-srtp-fallback,X-cisco-original-called
Call-Info: <sip:10.18.81.11:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Cisco-Guid: 1020645888-0000065536-0000124117-0189862410
Session-Expires: 1800
Contact: <sip:[email protected]:5060>
Max-Forwards: 70
Content-Length: 0
Nov 30 11:44:29.942: //64510/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.18.81.11:5060;branch=z9hG4bK2e72063a5aba5d
From: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
To: <sip:[email protected]>
Date: Sun, 30 Nov 2014 11:44:29 GMT
Call-ID: [email protected]
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.2.4.M5
Content-Length: 0
Nov 30 11:44:29.946: //64511/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3EC72218
From: "Bianca Africa" <sip:[email protected]>;tag=3C364D44-9E2
To: <sip:[email protected]>
Date: Sun, 30 Nov 2014 11:44:29 GMT
Call-ID: [email protected]
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 1020645888-0000065536-0000124117-0189862410
User-Agent: Cisco-SIPGateway/IOS-15.2.4.M5
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1417347869
Contact: <sip:[email protected]:5060>
Call-Info: <sip:10.18.81.2:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 69
Session-Expires: 1800
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 301
v=0
o=CiscoSystemsSIP-GW-UserAgent 7676 6958 IN IP4 10.18.81.2
s=SIP Call
c=I
PM-HO-VG-01#N IP4 10.18.81.2
t=0 0
m=audio 22256 RTP/AVP 18 0 8 101
c=IN IP4 10.18.81.2
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
Nov 30 11:44:29.950: //64511/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3EC72218
From: "Bianca Africa" <sip:[email protected]>;tag=3C364D44-9E2
To: <sip:[email protected]>
Call-ID: [email protected]
CSeq: 101 INVITE
Timestamp: 1417347869
Nov 30 11:44:30.658: //64511/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Session Progress
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3EC72218
From: "Bianca Africa" <sip:[email protected]>;tag=3C364D44-9E2
To: <sip:[email protected]>;tag=71913148-1417348035284
Call-ID: [email protected]
CSeq: 101 INVITE
Timestamp: 1417347869
Supported:
Contact: <sip:[email protected]:5060;transport=udp>
Session: Media
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE
X-BroadWorks-Correlation-Info: bbf94839-a234-4237-95e6-a7037322f0f4
Content-Type: application/sdp
Content-Length: 355
v=0
o=BroadWorks 316169737 1 IN IP4 10.111.111.254
s=-
c=IN IP4 10.111.111.254
t=0 0
m=audio 20074 RTP/AVP 18 101 100
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:100 X-NSE/8000
a=fmtp:100 200-202
a=X-sqn:0
a=X-cap: 1 audio RTP/AVP 100
a=X-cpar: a=rtpmap:100 X-NSE/8000
a=X-cpar: a=fmtp:100 200-202
a=X-cap: 2 image udptl t38
Nov 30 11:44:30.662: //64510/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 10.18.81.11:5060;branch=z9hG4bK2e72063a5aba5d
From: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
To: <sip:[email protected]>;tag=3C365010-1E42
Date: Sun, 30 Nov 2014 11:44:29 GMT
Call-ID: [email protected]
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <sip:[email protected]:5060>
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-15.2.4.M5
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 289
v=0
o=CiscoSystemsSIP-GW-UserAgent 7965 2747 IN IP4 10.18.81.2
s=SIP Call
c=IN IP4 10.18.81.2
t=0 0
m=audio 22350 RTP/AVP 18 101 19
c=IN IP4 10.18.81.2
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:19 CN/8000
a=ptime:20
Nov 30 11:44:31.226: //64511/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Session Progress
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3EC72218
From: "Bianca Africa" <sip:[email protected]>;tag=3C364D44-9E2
To: <sip:[email protected]>;tag=71913148-1417348035284
Call-ID: [email protected]
CSeq: 101 INVITE
Timestamp: 1417347869
Supported:
Contact: <sip:[email protected]:5060;transport=udp>
Session: Media
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE
X-BroadWorks-Correlation-Info: bbf9
PM-HO-VG-01#4839-a234-4237-95e6-a7037322f0f4
Content-Type: application/sdp
Content-Length: 355
v=0
o=BroadWorks 316169737 1 IN IP4 10.111.111.254
s=-
c=IN IP4 10.111.111.254
t=0 0
m=audio 20074 RTP/AVP 18 101 100
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:100 X-NSE/8000
a=fmtp:100 200-202
a=X-sqn:0
a=X-cap: 1 audio RTP/AVP 100
a=X-cpar: a=rtpmap:100 X-NSE/8000
a=X-cpar: a=fmtp:100 200-202
a=X-cap: 2 image udptl t38
Nov 30 11:44:31.630: //64511/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3EC72218
From: "Bianca Africa" <sip:[email protected]>;tag=3C364D44-9E2
To: <sip:[email protected]>;tag=71913148-1417348035284
Call-ID: [email protected]
CSeq: 101 INVITE
Timestamp: 1417347869
Supported:
Contact: <sip:[email protected]:5060;transport=udp>
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE
Accept: application/media_control+xml,application/sdp,application/xml
X-BroadWorks-Correlation-Info: bbf94839-a234-4237-95e6-a7037322f0f4
Content-Type: application/sdp
Content-Length: 355
v=0
o=BroadWorks 316169737 1 IN IP4 10.111.111.254
s=-
c=IN IP4 10.111.111.254
t=0 0
m=audio 20074 RTP/AVP 18 101 100
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:100 X-NSE/8000
a=fmtp:100 200-202
a=X-sqn:0
a=X-cap: 1 audio RTP/AVP 100
a=X-cpar: a=rtpmap:100 X-NSE/8000
a=X-cpar: a=fmtp:100 200-202
a=X-cap: 2 image udptl t38
Nov 30 11:44:31.630: //64511/3CD5D2000001/SIP/Call/sipSPICallInfo:
The Call Setup Information is:
Call Control Block (CCB) : 0x0x3D7B1458
State of The Call : STATE_ACTIVE
TCP Sockets Used : NO
Calling Number : 27218091323
Called Number : 0862000000
Source IP Address (Sig ): 10.18.81.2
Destn SIP Req Addr:Port : 10.111.111.254:5060
Destn SIP Resp Addr:Port : 10.111.111.254:5060
Destination Name : 10.111.111.254
Nov 30 11:44:31.630: //64511/3CD5D2000001/SIP/Call/sipSPIMediaCallInfo:
Number of Media Streams: 1
Media Stream : 1
Negotiated Codec : g729br8
Negotiated Codec Bytes : 20
Nego. Codec payload : 18 (tx), 18 (rx)
Negotiated Dtmf-relay : 6
Dtmf-relay Payload : 101 (tx), 101 (rx)
Source IP Address (Media): 10.18.81.2
Source IP Port (Media): 22256
Destn IP Address (Media): 10.111.111.254
Destn IP Port (Media): 20074
Orig Destn IP Address:Port (Media): [ - ]:0
Nov 30 11:44:31.630: //64511/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:[email protected]:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3EC81D00
From: "Bianca Africa" <sip:[email protected]>;tag=3C364D44-9E2
To: <sip:[email protected]>;tag=71913148-1417348035284
Date: Sun, 30 Nov 2014 11:44:29 GMT
Call-ID: [email protected]
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0
Nov 30 11:44:31.634: //64510/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.18.81.11:5060;branch=z9hG4bK2e72063a5aba5d
From: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
To: <sip:[email protected]>;tag=3C365010-1E42
Date: Sun, 30 Nov 2014 11:44:29 GMT
Call-ID: [email protected]
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <sip:[email protected]:5060>
Supported: replaces
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-15.2.4.M5
Supported: timer
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 289
v=0
o=CiscoSystemsSIP-GW-UserAgent 7965 2747 IN IP4 10.18.81.2
s=SIP Call
c=IN IP4 10.18.81.2
t=0 0
m=audio 22350 RTP/AVP 18 101 19
c=IN IP4 10.18.81.2
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:19 CN/8000
a=ptime:20
Nov 30 11:44:31.726: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.18.81.11:5060;branch=z9hG4bK2e72075e3a02c1
From: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
To: <sip:[email protected]>;tag=3C365010-1E42
Date: Sun, 30 Nov 2014 11:44:29 GMT
Call-ID: [email protected]
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence, kpml
Content-Type: application/sdp
Content-Length: 236
v=0
o=CiscoSystemsCCM-SIP 9082578 1 IN IP4 10.18.81.11
s=SIP Call
c=IN IP4 10.18.80.40
b=TIAS:8000
b=AS:8
t=0 0
m=audio 21928 RTP/AVP 18 101
a=rtpmap:18 G729/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
Nov 30 11:44:31.730: //64510/3CD5D2000001/SIP/Call/sipSPICallInfo:
The Call Setup Information is:
Call Control Block (CCB) : 0x0x3D816D70
State of The Call : STATE_ACTIVE
TCP Sockets Used : NO
Calling Number : 0218091323
Called Number : 0862000000
Source IP Address (Sig ): 10.18.81.2
Destn SIP Req Addr:Port : 10.18.81.11:5060
Destn SIP Resp Addr:Port : 10.18.81.11:5060
Destination Name : 10.18.81.11
Nov 30 11:44:31.730: //64510/3CD5D2000001/SIP/Call/sipSPIMediaCallInfo:
Number of Media Streams: 1
Media Stream : 1
Negotiated Codec : g729br8
Negotiated Codec Bytes : 20
Nego. Codec payload : 18 (tx), 18 (rx)
Negotiated Dtmf-relay : 6
Dtmf-relay Payload : 101 (tx), 101 (rx)
Source IP Address (Media): 10.18.81.2
Source IP Port (Media): 22350
Destn IP Address (Media): 10.18.80.40
Destn IP Port (Media): 21928
Orig Destn IP Address:Port (Media): [ - ]:0
Nov 30 11:44:31.730: //64510/3CD5D2000001/SIP/Call/sipSPICallInfo:
The Call Setup Information is:
Call Control Block (CCB) : 0x0x3D816D70
State of The Call : STATE_ACTIVE
TCP Sockets Used : NO
Calling Number : 0218091323
Called Number : 0862000000
Source IP Address (Sig ): 10.18.81.2
Destn SIP Req Addr:Port : 10.18.81.11:5060
Destn SIP Resp Addr:Port : 10.18.81.11:5060
Destination Name : 10.18.81.11
PM-HO-VG-01#
Nov 30 11:44:31.730: //64510/3CD5D2000001/SIP/Call/sipSPIMediaCallInfo:
Number of Media Streams: 1
Media Stream : 1
Negotiated Codec : g729br8
Negotiated Codec Bytes : 20
Nego. Codec payload : 18 (tx), 18 (rx)
Negotiated Dtmf-relay : 6
Dtmf-relay Payload : 101 (tx), 101 (rx)
Source IP Address (Media): 10.18.81.2
Source IP Port (Media): 22350
Destn IP Address (Media): 10.18.80.40
Destn IP Port (Media): 21928
Orig Destn IP Address:Port (Media): [ - ]:0
PM-HO-VG-01#sh sip
PM-HO-VG-01#sh sip-ua call
PM-HO-VG-01#sh sip-ua calls
Total SIP call legs:2, User Agent Client:1, User Agent Server:1
SIP UAC CALL INFO
Call 1
SIP Call ID : [email protected]
State of the call : STATE_ACTIVE (7)
Substate of the call : SUBSTATE_NONE (0)
Calling Number : 27218091323
Called Number : 0862000000
Bit Flags : 0xC04018 0x10000100 0x0
CC Call ID : 64511
Source IP Address (Sig ): 10.18.81.2
Destn SIP Req Addr:Port : [10.111.111.254]:5060
Destn SIP Resp Addr:Port: [10.111.111.254]:5060
Destination Name : 10.111.111.254
Number of Media Streams : 1
Number of Active Streams: 1
RTP Fork Object : 0x0
Media Mode : flow-through
Media Stream 1
State of the stream : STREAM_ACTIVE
Stream Call ID : 64511
Stream Type : voice+dtmf (0)
Stream Media Addr Type : 1
Negotiated Codec : g729br8 (20 bytes)
Codec Payload Type : 18
Negotiated Dtmf-relay : rtp-nte
Dtmf-relay Payload Type : 101
QoS ID : -1
Local QoS Strength : BestEffort
Negotiated QoS Strength : BestEffort
Negotiated QoS Direction : None
Local QoS Status : None
Media Source IP Addr:Port: [10.18.81.2]:22256
Media Dest IP Addr:Port : [10.111.111.254]:20074
Options-Ping ENABLED:NO ACTIVE:NO
Number of SIP User Agent Client(UAC) calls: 1
SIP UAS CALL INFO
Call 1
SIP Call ID : [email protected]
State of the call : STATE_ACTIVE (7)
Substate of the call : SUBSTATE_NONE (0)
Calling Number : 0218091323
Called Number : 0862000000
Bit Flags : 0xC0401E 0x10000100 0x80004
CC Call ID : 64510
Source IP Address (Sig ): 10.18.81.2
Destn SIP Req Addr:Port : [10.18.81.11]:5060
Destn SIP Resp Addr:Port: [10.18.81.11]:5060
Destination Name : 10.18.81.11
Number of Media Streams : 1
Number of Active Streams: 1
RTP Fork Object : 0x0
Media Mode : flow-through
Media Stream 1
State of the stream : STREAM_ACTIVE
Stream Call ID : 64510
Stream Type : voice+dtmf (1)
Stream Media Addr Type : 1
Negotiated Codec : g729br8 (20 bytes)
Codec Payload Type : 18
Negotiated Dtmf-relay : rtp-nte
Dtmf-relay Payload Type : 101
QoS ID : -1
Local QoS Strength : BestEffort
Negotiated QoS Strength : BestEffort
Negotiated QoS Direction : None
Local QoS Status : None
Media Source IP Addr:Port: [10.18.81.2]:22350
Media Dest IP Addr:Port : [10.18.80.40]:21928
Options-Ping ENABLED:NO ACTIVE:NO
Number of SIP User Agent Server(UAS) calls: 1
PM-HO-VG-01#
PM-HO-VG-01#
PM-HO-VG-01#
As you can see, the call is connected and everything is working perfectly. When I press the hold button, here is what I get:
NOTE: I have # debug ccsip messages and #debug ccsip calls (running)
PM-HO-VG-01#
PM-HO-VG-01#
Nov 30 11:44:49.210: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.18.81.11:5060;branch=z9hG4bK2e720852ab8b92
From: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
To: <sip:[email protected]>;tag=3C365010-1E42
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
Supported: timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM9.1
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 102 INVITE
Max-Forwards: 70
Expires: 180
Allow-Events: presence
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Contact: <sip:[email protected]:5060>
Content-Type: application/sdp
Content-Length: 244
v=0
o=CiscoSystemsCCM-SIP 9082578 2 IN IP4 10.18.81.11
s=SIP Call
c=IN IP4 0.0.0.0
b=TIAS:8000
b=AS:8
t=0 0
m=audio 21928 RTP/AVP 18 101
a=rtpmap:18 G729/8000
a=ptime:20
a=inactive
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
Nov 30 11:44:49.218: //64510/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.18.81.11:5060;branch=z9hG4bK2e720852ab8b92
From: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
To: <sip:[email protected]>;tag=3C365010-1E42
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
CSeq: 102 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.2.4.M5
Content-Length: 0
Nov 30 11:44:49.218: //64511/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:[email protected]:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3EC9241
From: "Bianca Africa" <sip:[email protected]>;tag=3C364D44-9E2
To: <sip:[email protected]>;tag=71913148-1417348035284
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 1020645888-0000065536-0000124117-0189862410
User-Agent: Cisco-SIPGateway/IOS-15.2.4.M5
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 102 INVITE
Max-Forwards: 70
Timestamp: 1417347889
Contact: <sip:[email protected]:5060>
Call-Info: <sip:10.18.81.2:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Length: 271
v=0
o=CiscoSystemsSIP-GW-UserAgent 7676 6959 IN IP4 10.18.81.2
s=SIP Call
c=IN IP4 0.0.0.0
t=0 0
m=audio 22256 RTP/AVP 18 101
c=IN IP4 0.0.0.0
a=inactive
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
Nov 30 11:44:49.278: //64511/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3EC9241
From: "Bianca Africa" <sip:[email protected]>;tag=3C364D44-9E2
To: <sip:[email protected]>;tag=71913148-1417348035284
Call-ID: [email protected]
CSeq: 102 INVITE
Timestamp: 1417347889
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE
Supported:
Accept: application/media_control+xml,application/sdp,application/xml
Contact: <sip:[email protected]:5060;transport=udp>
X-BroadWorks-Correlation-Info: bbf94839-a234-4237-95e6-a7037322f0f4
Content-Type: application/sdp
Content-Length: 360
v=0
o=BroadWorks 316169737 2 IN IP4 10.111.111.254
s=-
c=IN IP4 0.0.0.0
t=0 0
m=audio 20074 RTP/AVP 18 101 100
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:100 X-NSE/8000
a=fmtp:100 200-202
a=X-sqn:0
a=X-cap: 1 audio RTP/AVP 100
a=X-cpar: a=rtpmap:100 X-NSE/8000
a=X-cpar: a=fmtp:100 200-202
a=X-cap: 2 image udptl t38
a=inactive
Nov 30 11:44:49.278: //64511/3CD5D2000001/SIP/Call/sipSPICallInfo:
The Call Setup Information is:
Call Control Block (CCB) : 0x0x3D7B1458
State of The Call : STATE_ACTIVE
TCP Sockets Used : NO
Calling Number : 27218091323
Called Number : 0862000000
Source IP Address (Sig ): 10.18.81.2
Destn SIP Req Addr:Port : 10.111.111.254:5060
Destn SIP Resp Addr:Port : 10.111.111.254:5060
Destination Name : 10.111.111.254
Nov 30 11:44:49.278: //64511/3CD5D2000001/SIP/Call/sipSPIMediaCallInfo:
Number of Media Streams: 1
Media Stream : 1
Negotiated Codec : g729br8
Negotiated Codec Bytes : 20
Nego. Codec payload : 18 (tx), 18 (rx)
Negotiated Dtmf-relay : 6
Dtmf-relay Payload : 101 (tx), 101 (rx)
Source IP Address (Media): 10.18.81.2
Source IP Port (Media): 22256
Destn IP Address (Media): 0.0.0.0
Destn IP Port (Media): 20074
Orig Destn IP Address:Port (Media): [ - ]:0
Nov 30 11:44:49.282: //64511/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:[email protected]:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3ECA2633
From: "Bianca Africa" <sip:[email protected]>;tag=3C364D44-9E2
To: <sip:[email protected]>;tag=71913148-1417348035284
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
Max-Forwards: 70
CSeq: 102 ACK
Allow-Events: telephone-event
Content-Length: 0
Nov 30 11:44:49.282: //64510/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.18.81.11:5060;branch=z9hG4bK2e720852ab8b92
From: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
To: <sip:[email protected]>;tag=3C365010-1E42
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
CSeq: 102 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <sip:[email protected]:5060>
Supported: replaces
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-15.2.4.M5
Supported: timer
Content-Type: application/sdp
Content-Length: 271
v=0
o=CiscoSystemsSIP-GW-UserAgent 7965 2748 IN IP4 10.18.81.2
s=SIP Call
c=IN IP4 0.0.0.0
t=0 0
m=audio 22350 RTP/AVP 18 101
c=IN IP4 0.0.0.0
a=inactive
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
Nov 30 11:44:49.282: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.18.81.11:5060;branch=z9hG4bK2e72094953dfea
From: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
To: <sip:[email protected]>;tag=3C365010-1E42
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
Max-Forwards: 70
CSeq: 102 ACK
Allow-Events: presence
Content-Length: 0
Nov 30 11:44:49.290: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.18.81.11:5060;branch=z9hG4bK2e720a6918040f
From: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
To: <sip:[email protected]>;tag=3C365010-1E42
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
Supported: timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM9.1
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 103 INVITE
Max-Forwards: 70
Expires: 180
Allow-Events: presence
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Contact: <sip:[email protected]:5060>
Content-Length: 0
Nov 30 11:44:49.294: //64510/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.18.81.11:5060;branch=z9hG4bK2e720a6918040f
From: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
To: <sip:[email protected]>;tag=3C365010-1E42
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
CSeq: 103 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.2.4.M5
Content-Length: 0
Nov 30 11:44:49.294: //64511/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:[email protected]:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3ECB16F3
From: "Bianca Africa" <sip:[email protected]>;tag=3C364D44-9E2
To: <sip:[email protected]>;tag=71913148-1417348035284
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
Supported: timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 1020645888-0000065536-0000124117-0189862410
User-Agent: Cisco-SIPGateway/IOS-15.2.4.M5
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 103 INVITE
Max-Forwards: 70
Timestamp: 1417347889
Contact: <sip:[email protected]:5060>
Expires: 180
Allow-Events: telephone-event
Content-Length: 0
Nov 30 11:44:49.338: //64511/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3ECB16F3
From: "Bianca Africa" <sip:[email protected]>;tag=3C364D44-9E2
To: <sip:[email protected]>;tag=71913148-1417348035284
Call-ID: [email protected]
CSeq: 103 INVITE
Timestamp: 1417347889
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE
Supported:
Accept: application/media_control+xml,application/sdp,application/xml
Contact: <sip:[email protected]:5060;transport=udp>
Content-Type: application/sdp
Content-Length: 306
v=0
o=BroadWorks 316169737 3 IN IP4 10.111.111.254
s=-
c=IN IP4 10.111.111.254
t=0 0
m=audio 20074 RTP/AVP 18 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=X-sqn:0
a=X-cap: 1 audio RTP/AVP 100
a=X-cpar: a=rtpmap:100 X-NSE/8000
a=X-cpar: a=fmtp:100 200-202
a=X-cap: 2 image udptl t38
Nov 30 11:44:49.342: //64510/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 2
PM-HO-VG-01#00 OK
Via: SIP/2.0/UDP 10.18.81.11:5060;branch=z9hG4bK2e720a6918040f
From: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
To: <sip:[email protected]>;tag=3C365010-1E42
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
CSeq: 103 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <sip:[email protected]:5060>
Supported: replaces
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-15.2.4.M5
Supported: timer
Content-Type: application/sdp
Content-Length: 289
v=0
o=CiscoSystemsSIP-GW-UserAgent 7965 2749 IN IP4 10.18.81.2
s=SIP Call
c=IN IP4 10.18.81.2
t=0 0
m=audio 22350 RTP/AVP 18 101 19
c=IN IP4 10.18.81.2
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:19 CN/8000
a=ptime:20
Nov 30 11:44:49.350: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.18.81.11:5060;branch=z9hG4bK2e720b594cd517
From: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
To: <sip:[email protected]>;tag=3C365010-1E42
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
Max-Forwards: 70
CSeq: 103 ACK
Allow-Events: presence
Content-Type: application/sdp
Content-Length: 213
v=0
o=CiscoSystemsCCM-SIP 9082578 3 IN IP4 10.18.81.11
s=SIP Call
c=IN IP4 10.18.81.10
t=0 0
m=audio 4000 RTP/AVP 18
a=X-cisco-media:umoh
a=rtpmap:18 G729/8000
a=ptime:20
a=fmtp:18 annexb=no
a=sendonly
Nov 30 11:44:49.354: //64510/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3ECC55
From: <sip:[email protected]>;tag=3C365010-1E42
To: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
User-Agent: Cisco-SIPGateway/IOS-15.2.4.M5
Max-Forwards: 70
Timestamp: 1417347889
CSeq: 101 BYE
Reason: Q.850;cause=86
P-RTP-Stat: PS=874,OS=17480,PR=872,OR=17440,PL=0,JI=0,LA=0,DU=17
Content-Length: 0
Nov 30 11:44:49.354: //64511/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:[email protected]:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3ECD1ECD
From: "Bianca Africa" <sip:[email protected]>;tag=3C364D44-9E2
To: <sip:[email protected]>;tag=71913148-1417348035284
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
User-Agent: Cisco-SIPGateway/IOS-15.2.4.M5
Max-Forwards: 70
Timestamp: 1417347889
CSeq: 104 BYE
Reason: Q.850;cause=65
P-RTP-Stat: PS=872,OS=17440,PR=952,OR=19040,PL=0,JI=0,LA=0,DU=17
Content-Length: 0
Nov 30 11:44:49.374: //64511/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 Race Condition
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3ECD1ECD
From: "Bianca Africa" <sip:[email protected]>;tag=3C364D44-9E2
To: <sip:[email protected]>;tag=71913148-1417348035284
Call-ID: [email protected]
Timestamp: 1417347889
CSeq: 104 BYE
Content-Length: 0
Nov 30 11:44:49.374: //64511/3CD5D2000001/SIP/Call/sipSPICallInfo:
The Call Setup Information is:
Call Control Block (CCB) : 0x0x3D7B1458
State of The Call : STATE_DEAD
TCP Sockets Used : NO
Calling Number : 27218091323
Called Number : 0862000000
Source IP Address (Sig ): 10.18.81.2
Destn SIP Req Addr:Port : 10.111.111.254:5060
Destn SIP Resp Addr:Port : 10.111.111.254:5060
Destination Name : 10.111.111.254
Nov 30 11:44:49.374: //64511/3CD5D2000001/SIP/Call/sipSPIMediaCallInfo:
Number of Media Streams: 1
Media Stream : 1
Negotiated Codec : g729br8
Negotiated Codec Bytes : 20
Nego. Codec payload : 18 (tx), 18 (rx)
Negotiated Dtmf-relay : 6
Dtmf-relay Payload : 101 (tx), 101 (rx)
Source IP Address (Media): 10.18.81.2
Source IP Port (Media): 22256
Destn IP Address (Media): 10.111.111.254
Destn IP Port (Media): 20074
Orig Destn IP Address:Port (Media): [ - ]:0
Nov 30 11:44:49.374: //64511/3CD5D2000001/SIP/Call/sipSPICallInfo:
Disconnect Cause (CC) : 65
Disconnect Cause (SIP) : 200
Nov 30 11:44:49.406: //64510/3CD5D2000001/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.18.81.2:5060;branch=z9hG4bK3ECC55
From: <sip:[email protected]>;tag=3C365010-1E42
To: "Bianca Africa" <sip:[email protected]>;tag=9082578~cdf4c5a6-dd2b-4c71-bca0-b262ad997720-44517224
Date: Sun, 30 Nov 2014 11:44:49 GMT
Call-ID: [email protected]
CSeq: 101 BYE
Content-Length: 0
Nov 30 11:44:49.406: //64510/3CD5D2000001/SIP/Call/sipSPICallInfo:
The Call Setup Information is:
Call Control Block (CCB) : 0x0x3D816D70
State of The Call : STATE_DEAD
TCP Sockets Used : NO
Calling Number : 0218091323
Called Number : 0862000000
Source IP Address (Sig ): 10.18.81.2
Destn SIP Req Addr:Port : 10.18.81.11:5060
Destn SIP Resp Addr:Port : 10.18.81.11:5060
Destination Name : 10.18.81.11
Nov 30 11:44:49.406: //64510/3CD5D2000001/SIP/Call/sipSPIMediaCallInfo:
Number of Media Streams: 1
Media Stream : 1
Negotiated Codec : g729br8
Negotiated Codec Bytes : 20
Nego. Codec payload : 18 (tx), 18 (rx)
Negotiated Dtmf-relay : 6
Dtmf-relay Payload : 101 (tx), 101 (rx)
Source IP Address (Media): 10.18.81.2
Source IP Port (Media): 22350
Destn IP Address (Media): 0.0.0.0
Destn IP Port (Media): 21928
Orig Destn IP Address:Port (Media): [ - ]:0
Nov 30 11:44:49.406: //64510/3CD5D2000001/SIP/Call/sipSPICallInfo:
Disconnect Cause (CC) : 86
Disconnect Cause (SIP) : 200
PM-HO-VG-01#

Hi Manish,
Again, excellent feedback. Much appreciated.
I will try the commands suggested above and see if I can get DTMF to work correctly while interworking H.323 and SIP.
But my ultimate goal is to have SIP all way from the CUCM to the CUBE and from the CUBE to the ITSP.
If I enable SIP Early Offer with MTP on the CUCM going to the CUBE, all SIP Invite sent from the CUCM to the CUBE uses G.729r8 as the codec and once the call is established using G.729r8 should the ITSP reply with that codec, the call succeed and I am able to see an active MTP session using G.729 when I issue the command # show sccp connections.
One thing that I saw is that my ITSP love so much sending G.729br8 most of the times, so even if using SIP EO with MTP on the SIP Trunk to the CUBE, when I sent my INVITE out from the CUCM to the CUBE using G.729r8, specially on call center numbers such as 0800 numbers, you will see that the call established but the codec being negotiated is G.729br8 which is voice only (missing DTMF).
I will be doing some intensive test again later on this week and will send the logs.
Here is my question to both of you:
Which is the best way of having a proper SIP to SIP setup all the way that will not pose any problem?
Do I have to enable Early Offer on the SIP Profile used by the CUBE SIP Trunk or should I use the normal Standard SIP Profile? Do I need to enable MTP on my CUBE SIP Trunk or not?
From the CUBE point of view, I have a voice class codec that support G.729r8 or G.729br8 and the DTMF Relay method supported by the ITSP is RFC 2833.
I will send more logs for each scenario. I think that we are getting close to the resolution of this problem.
Thanks again for your support fellows.

Configuring Level3 SIP trunk with Lync 2013

Hi, I ran into some issues trying to configure SIP trunk from Level 3 and I was hoping someone here can help. We have our mediation server collocated with FE and SIP traffic goes from public IP, port 5060 via NAT, to local IP on FE, port 5060.
Level 3 provided us with one signaling IP and two RTP IPs.
I tried multiple trunk configuration settings and I can see that when I'm placing a call from Lync to an outside number I'm getting INVITE from Level 3 signaling IP, the session is established, phone rings, but there is no audio on either side. There's also
a METHOD NOT ALLOWED message coming from them, which doesn't tell me much about what's happening.
If I call to a Level 3 DID (assigned to my Lync user account) there's also INVITE from their side, but later I receive a CANCEL from them due to idle session. The phone never rings.
Questions:
1) Does anyone have Level 3 SIP trunks configured and can share their Get-TrunkConfiguration settings? What settings should I have for encryption, refer, sessionTimer / RTCP, and others? Level 3 refuses to provide any additional information besides IPs.
2) Do I understand this correctly that when configuring PSTN gateways in topology, one of the RTP IPs should be entered in the "alternate media IP" field? We have SIP trunks from another provider (which work fine), and they only use one IP
for everything, so I don't have any experience configuring separate SIP and media IPs with Lync.
Thanks, and let me know if I should provide additional info.

Hi,
On Lync topology PSTN gateways interface, please check if you enter gateway listening port 5060 and enable TCP option.
Please also check if you enable refer support on Lync Server Control Panel, if you enable it please uncheck it.
You can compare the trunk configuration for Level 3 in the part “Sample Trunk Configuration for Level 3” in the link below with yours’, it is for Lync server 2010 but similar for Lync server 2013:
http://blogs.technet.com/b/nexthop/archive/2013/04/10/configuring-lync-2010-server-to-work-with-level-3-sip-trunking-services.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Redirect SIP Trunk calls to FXO port

Hi,
This is the scenario. There are 3 branches, two of them are Cisco Call Manager Express and one of them is Elastix-based.
So, as the image explains, the three branches have SIP trunks fully operational. The branches are in different cities, so the numbers structure changes. In city A it begins with 2, in B begins with 3 and in C begins with 4. Every POTS number is a 7 digit number (2XXXXXX, 3XXXXXX, 4XXXXXX). And every user, in every branch, have a 4 digit number beginning with the city code (2XXX, 3XXX, 4XXX).
But, every time city A wants to make a call to a POTS number in city B, it goes across the A´s FXO line. So it charges a inter-city cost to the call.
The client wants that every time a city A user wants to call a POTS number in city B, goes over the SIP trunk to city B and use the FXO on the city B call manager.
I have made a pattern for city A. So, everytime the user dials 3XXXXXX, it does not use the city A´s FXO, but it goes to the branch in city B.
What do I have to do now in branch B´s Call Manager Express to redirect that call to a local FXO?
Thanks in advanced!
Regards
PS. There is a diagram of the topology. Want to do what the red line is doing.

In this situation I would do an answer-address based on ANI so you are specifically identifying your site A and then just piggy back off the local FXO out.
So assuming you are sending just 4 digits over the SIP for each site:
Dial-peer voice X voip
answer-address "blah"
protocol sipv2
...(whatever else you need to configure in these dots)
At this point your CME at site B will take the call see that it is destined for a POTs line and it should send it out whatever local dial-peer you have setup for that site when they dial out to the PSTN locally.
EDIT:
Then again, you probably already have a general incoming dial-peer, the above design would just be specific for your site A and isn't really needed.

Best Practice to Integrate CER with RedSky E911 Anywhere via SIP Trunk

We are trying to integrate CER 9 with RedSky for V911 using a SIP trunk and need assistance with best practice and configuration. There is very little documentation regarding "best practice" for routing these calls to RedSky. This trunk will be handling the majority of our geographically dispersed company's 911 calls.
My question is: should we use an IPsec tunnel for this? The only reference I found was this: http://www.cisco.com/c/en/us/solutions/collateral/enterprise-networks/virtual-office/deployment_guide_c07-636876.htmlm which recommends an IPsec tunnel for the SIP trunk to Intrado. I would think there are issues with an unsecure SIP trunk for 911 calls. Looking for advice or specifics on how to configure this. Does the SIP trunk require a CUBE or is a CUBE only required for the IPsec tunnel?
Any insight is appreciated.
Thank you.

you can use Session Trace in RTMT to check who is disconnecting the call and why.

BE6000 and SIP trunk

Hello!
Now we use Cisco IP telephony based on Cisco CME. Cisco CME is installed on 2821 router with IOS C2800NM-ADVENTERPRISEK9-M, Version 12.4(24)T7. A SIP trunk is configured between CME router and telephony provider.
We plan to upgrade our telephone system and begin using Cisco CBE6000. I study the documentation and in "Cisco Business Edition Unified Communications and Collaboration Solutions for Small and Midsized Companies", I find that for SIP trunk to works in CBE6000 a Cisco Integrated Services Router with Cisco Unified Border Element is required. Or other quote from this document "Public switched telephone network (PSTN) connections using SIP is available through any Cisco Integrated Services Router voice gateway".
In this regard there is a question: what is the functions of this router when I make a trunk between CBE6000 and telephony provider SIP gateway and whether it is possible to use existing Cisco 2821 router as such router.
Thanks.

Hi Ayodeji,
I too have a somewhat similar query.
We have UC560 running currently at our company, the UC560 is connected to an ISDN modem from the network provider. We are now upgrading to BE6000. To connect to the ISDN E1/T1 line, we've ordered Cisco 2921 with a E1/T1 VWIC card (VWIC3-2MFT-T1/E1) which will connect to BE6000 and internal LAN. I just wanted to know what would I need to configure on 2921?
Do I need to install CUBE or just configure it to connect to ISDN line?
Many thanks for any help.
regards,

CUCM route calls diferents gateways/sip trunks

Hi at all, I have CUCM 6.1.1 and I want to route calls throughs diferents gateways or sip trunks.
I planned to do with route groups, but I can not add on a route group a H323 gateway and a SIP trunk at the same time.
How can route calls in different ways?
In the CUCM page "Route patterns" I want to make alternative routes, for example, the number 6666 is on route "666X" through a "gateway/route list", but if I can not contact by going this route I need to go through the alternative route "XXXX" through another "gateway/route list".
How can I make by going first to one pattern and then the other pattern?
Thanks!
Fran

Ok thanks but one question more.... if I have a MGCP Gateway? Can I do this from my MGCP Gateway? or I need an H323 Gateway.
And another possibility.... I dont know if it's right....
Can I do this with Partitions and CSS?
This is for example I 'll have a CSS "Global" with Partitions (Primary and Secondary);
It could go the route first to 666x Gateway with CSS "Global" and partitions (Primary and Secondary). This way I do not know if it is routed first through the Gateway of the partition as Primary and Secondary alternative partition that is served by the SIP Trunk.
Using the "Dial Number Analyzer" I get the second path XXXX (SIP Trunk) as an alternative route ...

Calls via Gamme sip trunk

Has anyone set up Lync server 2010 to use the Gamma SIP trunks, that dont require the use of a gateway?
No requirement for an additional gateway device, with direct MS Lync connectivity
The trouble is i cannot get Lync to connect to the trunks. We have purchased the SIP trunks from a gamma supplier(we didnt now they were a supplier, until recently when we asked for support and they went 'duhhhhhh me no know, we just
sell things dunow how to set things up' what a PAIN IN THE A***), and they say that the SIP trunks are pointed at our EFM IP address. which also has the DDIs assigned to it.
So, i setup a PSTN gateway on lync topology using IP of EFM, Listening port 5060 using TCP. Are these ports and protocol okay?
The VoIP phones seem to want to call, they just lack any sound, no ringing tone, no dissconnected tone. Just says calling "+44157322****" So the dial plan is changing 22**** to the correct local code and whatever the +44 thing
is.
Any advice on how i can find the problem, or how to setup the trunks up would be hugely appreciated.
P.S We initially tried to use an audiocodes mediant 1000, which was what we asked our trunk supplier about, and then they informed us about being a gamma supplier, and that the gamma trunks do not require a gateway. Followed setting
up guide for mediant 1000 with gamma trunks through audiocodes blah, to no success. I think thats because it was changing the coders, which was not needed if the trunks are directly compatable.

Hi,
Please review the SIP trunk topology.
http://technet.microsoft.com/en-us/library/gg398720.aspx
To
implement SIP trunking, you must route the connection through a Mediation Server, which proxies communications sessions between Lync Server 2010 clients and the service provider and transcodes media when necessary. Each Mediation Server has
an internal and an external network interface. The internal interface connects to the Front End Servers. The external interface is commonly called the gateway interface because it has traditionally been used to connect the Mediation Server to a PSTN gateway
or an IP-PBX. To implement a SIP trunk, you connect the external interface of the Mediation Server to the external edge component of the ITSP. The external edge component of the ITSP could be a Session Border Controller (SBC), a router, or a gateway.
Generally the gateway is not required in your organization. You need to configure Mediation Server setting. For the details about
the SIP trunk configuration of ITSP side, you need to contact Gamme Support for further assistance.
Regards,
Kent Huang
TechNet Community Support ************************************************************************************************************************ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a
marked post does not actually answer your question.

CUCM SIP Trunk Unable to find a device handler for the request received

I have a lab running CUCM 10.0 that has a SIP trunk to a VCS. Previously I was able to place and receive calls across the trunk, but now I can only place calls, not receive. I did recently upgrade to 10.5, but I really can't recall if it ever worked after the upgrade. The error I'm getting in CUCM is
Unable to route message, Cannot find the SIP Device with Name=192.1.1.61, Source Port=5060, IpAddress Type=0
This confuses me, because the destination IP/port of the VCS SIP trunk is 192.1.1.61:5060. The trunk on CUCM show as up and the Zone in VCS shows as up. What is going on?
Thanks, Mike

I figured it out. Long story short, it was a port mismatch. When you configure Mobile Remote Access on the Expressway Core it creates a SIP trunk from Expressway to CUCM using port 5060. If you then create another SIP trunk from the same Expressway to CUCM for firewall traversal or external calling, you must use a different port. The port used for the zone in Expressway must match the SIP security profile used on the CUCM side SIP trunk. So I had created another SIP Security profile in CUCM with port 5062 for this purpose. However, the VCS in question that I was working with was only being used for FW traversal, so I used 5060 as the port on the VCS side, but I applied the SIP security profile that used 5062 on the CUCM side. That's why CUCM was throwing that "device not found" error. Once I changed the Security Profile to match the same port used on VCS (5060) all was well. Sorry for the long winded answer. Hope it helps someone else down the road.

Testing new sip trunk for an upgraded system....

Hey all,
Hoping I can get a quick direction on this.....
We are upgrading our call center servers and need to point a few test toll free numbers.
I have already created a test sip trunk....here's where it all gets muddy for me. What do I need to do to route 4 specific toll free numbers to hit this specific sip trunk instead of going to our current one?
Any docs and verbal guidance would be appreciated.
Thanks in advance all!

Ok, so here's what i did....
I created the following >>> RG with new server as member>RL with the new RG as member>RP
We already have a RP of 5[1-9]XXX which matches the DNIS of the 4 toll free numbers we are using for this test, so I just went ahead and created an exact match RP of 59796. (I'll create the other 3 if I can get this to work)
Before I created all this, the call went to our sales dept like designed. After creating it, now I get a "this number has been disconnected" message. What did I miss?

Lync Enterprise Voice Deployment - Can't get SIP trunks to work

Hey guys,
So i'm doing a proof-of-concept for Lync 2013 Enterprise voice. I've just purchased two sip trunks with 3 DIDs. I've followed their directions but have had no luck making outgoing PSTN numbers. I always get the error message "Disconnected service unavailable".
I did some troubleshooting with their tech support, did some logging with Lync & gave them our SIP Logs.
Here is what they told me back:
I have reviewed the log and found the following:
Your logs state the below:
Direction: outgoing;source="local"
Peer: lync2013.network.caedm.ca:5070
sip:[email protected]:5070
ß this particular line states to send the call of 780-719-8033 to 208.82.88.120 at port 5070. Please change this to port 5060.
In your outbound To field you have the following:
To: <sip:7807198033;phone-context=[email protected];user=phone>;epid=EC06E70A33;tag=b91b46715a
Please change this to reflect: To:
sip:[email protected];user=phone>;epid=EC06E70A33;tag=b91b46715a
Where can I set the outgoing port to 5060? In the topology builder I have already configured the listening port under "PSTN gateway" to be TCP 5060. I don't see anything in the topology builder relating to outgoing ports, only "listening ports".
Thanks.

Looks exactly the same as mine. (I also use a SIP trunk.)
I assume you can ping the SIP provider from your mediation server? (and telnet to TCP 5060) without any issue.
Sorry, try netstat -ano
You should have some entries that look this: (where 10.0.0.3 is your mediation servers local IP)
TCP 10.0.0.3:5060 208.82.88.120:58869 ESTABLISHED 1780
TCP 10.0.0.3:5060 208.82.88.120:58924 ESTABLISHED 1780
TCP 10.0.0.3:5060 208.82.88.120:59094 ESTABLISHED 1780
TCP 10.0.0.3:5060 208.82.88.120:59216 ESTABLISHED 1780
TCP 10.0.0.3:5060 208.82.88.120:59658 ESTABLISHED 1780
TCP 10.0.0.3:5060 208.82.88.120:59734 ESTABLISHED 1780
TCP 10.0.0.3:5060 208.82.88.120:59953 ESTABLISHED 1780
TCP 10.0.0.3:5060 208.82.88.120:60255 ESTABLISHED 1780
TCP 10.0.0.3:5060 208.82.88.120:60318 ESTABLISHED 1780
TCP 10.0.0.3:5060 208.82.88.120:60631 ESTABLISHED 1780
TCP 10.0.0.3:5060 208.82.88.120:60765 ESTABLISHED 1780
TCP 10.0.0.3:5060 208.82.88.120:60834 ESTABLISHED 1780
TCP 10.0.0.3:5060 208.82.88.120:60885 ESTABLISHED 1780
TCP 10.0.0.3:5060 208.82.88.120:60934 ESTABLISHED 1780
TCP 10.0.0.3:5060 208.82.88.120:61141 ESTABLISHED 1780
If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer"
Georg Thomas | Lync MVP
Blog www.lynced.com.au | Twitter
@georgathomas
Lync Edge Port Check (Beta)
This forum post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Dual sip trunk on uc500

Hi all.
i would like to know if it is possible to configure a dual sip trunk on a uc500, its like a dual redundant link to a sip server.
best regarts

Then it would be better to ask on forum related to Cisco technology in question. You are off-topic here and your's chances to receive valuable reply here are rather low.
Please delete this threat here (big red [ Delete ] button) and recreate it in a more appropriate forum.
Thank you.

Design Question Sip Trunk

Similar Messages

Maybe you are looking for