Remove trunking from a port in catos?

All,
Simple question: I want to remove all trunking from a port on a switch running catos. Clear Trunk seemed the obvious option, though it seems to just remove the vlans that are allowed to pass over the trunk port. Set Trunk mod/port Off doesn't do the trick either. Any thoughts?
thanks!

Hi Chris,
"set trunk x/y off" is the correct syntax. When you try that, what happens?
HTH,
Bobby

Similar Messages

How do you safely remove hardware from USB port, How do you safely remove hardware from USB port

How do you remove hardware safely from usb ports? i cannot see any icons located on my screen

What kind of hardware?
Only drives need to be "safely" removed in Mac OS X. If they are not on your desktop open a Finder window and they will be in the right hand column

Removing lint from charging port - PLEASE HELP!

Hey guys,
I really need to charge my 3G iPhone, but when I went to plug it in, I noticed the plug wouldn't go in all the way. So, I removed it and inspected the charging port, and discovered that I have a piece of lint from my jeans pocket stuck between the board and the side of the case... It appears to be lodged, and I'm not sure how to remove this... any thoughts?
Jeff

I had a similar issue..
I used a sewing needle and canned air.
Be warned that if there is any damage to the device in doing so, it may void your warranty.

Cannot remove iPod Shuffle from USB port

I cannot physically remove iPod from the USB port on my Dell Latitude (Windows XP Pro). The device is recognized intermittently in My Computer. Powering the notebook off doesn;t solve the problem and I have done the "Five Rs".
The deveice is physically locked - can slide it partially from USB prot, but it does not release.
Any ideas?

Wow!!! Take it to a Apple or Dell computer shop and hope they can remove it for you

[svn:fx-trunk] 5140: Removing [ExcludeClass] from classes outside the package.

Revision: 5140
Author: [email protected]
Date: 2009-03-02 12:09:24 -0800 (Mon, 02 Mar 2009)
Log Message:
Removing [ExcludeClass] from classes outside the package.
QE Notes: None.
Doc Notes: None.
tests: checkintests
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/layout/HorizontalLayout.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/layout/VerticalLayout.as

[svn:fx-trunk] 12925: Remove FIXME from SliderBase.

Revision: 12925
Revision: 12925
Author:   [email protected]
Date:     2009-12-14 14:19:53 -0800 (Mon, 14 Dec 2009)
Log Message:
Remove FIXME from SliderBase. It is correct for Slider to set the pendingValue during an animation, and it should not actually set the value or dispatch valueCommit events for an animation.
QE notes: No
Doc notes: No
Bugs: None
Reviewer: -
Tests run: -
Is noteworthy for integration: No
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/SliderBase.a s

[svn:fx-trunk] 8825: Normalizing URLs to remove [[DYNAMIC]] from LoaderInfo .url information which occurs when linking against RSLs.

Revision: 8825
Author:   [email protected]
Date:     2009-07-27 11:51:15 -0700 (Mon, 27 Jul 2009)
Log Message:
Normalizing URLs to remove [[DYNAMIC]] from LoaderInfo.url information which occurs when linking against RSLs. This fixes RPC services trying to resolve a fully qualified URL for relative resources.
QE: Yes, please ensure RPC tests that make use of relative paths are compiled with RSLs.
Doc: No
Checkintests: Pass
Reviewer: Darrell
Bugs:
FB-21713 - HTTPService to relative file in CF project fails due to incorrectly re-written URL
SDK-22362 - RemoteObject method calls for invoking php code fails when relative URL is given for endpoint
Ticket Links:
    http://bugs.adobe.com/jira/browse/FB-21713
    http://bugs.adobe.com/jira/browse/SDK-22362
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/managers/systemClasses/ChildManager.a s
    flex/sdk/trunk/frameworks/projects/framework/src/mx/messaging/config/LoaderConfig.as

Revision: 8825
Author:   [email protected]
Date:     2009-07-27 11:51:15 -0700 (Mon, 27 Jul 2009)
Log Message:
Normalizing URLs to remove [[DYNAMIC]] from LoaderInfo.url information which occurs when linking against RSLs. This fixes RPC services trying to resolve a fully qualified URL for relative resources.
QE: Yes, please ensure RPC tests that make use of relative paths are compiled with RSLs.
Doc: No
Checkintests: Pass
Reviewer: Darrell
Bugs:
FB-21713 - HTTPService to relative file in CF project fails due to incorrectly re-written URL
SDK-22362 - RemoteObject method calls for invoking php code fails when relative URL is given for endpoint
Ticket Links:
    http://bugs.adobe.com/jira/browse/FB-21713
    http://bugs.adobe.com/jira/browse/SDK-22362
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/managers/systemClasses/ChildManager.a s
    flex/sdk/trunk/frameworks/projects/framework/src/mx/messaging/config/LoaderConfig.as

[svn:fx-trunk] 8417: Remove themes from the package that are not compiling cleanly

Revision: 8417
Author:   [email protected]
Date:     2009-07-07 04:50:21 -0700 (Tue, 07 Jul 2009)
Log Message:
Remove themes from the package that are not compiling cleanly
bug: https://bugs.adobe.com/jira/browse/SDK-21144
qa: yes
doc:
checkintests: pass
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21144
Modified Paths:
    flex/sdk/trunk/build.xml

[svn:fx-trunk] 13298: Remove FIXMEs from DateChooser wireframe skins

Revision: 13298
Revision: 13298
Author:   [email protected]
Date:     2010-01-05 17:59:32 -0800 (Tue, 05 Jan 2010)
Log Message:
Remove FIXMEs from DateChooser wireframe skins
Wireframe skins don't need over and down states.
QE notes: -
Doc notes: -
Bugs: -
Reviewer: -
Tests run: -
Is noteworthy for integration: -
Modified Paths:
    flex/sdk/trunk/frameworks/projects/wireframe/src/mx/skins/wireframe/DateChooserNextMonthS kin.mxml
    flex/sdk/trunk/frameworks/projects/wireframe/src/mx/skins/wireframe/DateChooserNextYearSk in.mxml
    flex/sdk/trunk/frameworks/projects/wireframe/src/mx/skins/wireframe/DateChooserPrevMonthS kin.mxml
    flex/sdk/trunk/frameworks/projects/wireframe/src/mx/skins/wireframe/DateChooserPrevYearSk in.mxml

Please provide me with a simple example for creating a trunk from a 6506 to a 3750

An simple config example would be perfect

Here goes the configuration
3560 – example
Switch(config)#int fa0/2
Switch(config-if)#switchport
Switch(config-if)#switchport trunk encapsulation ?
dot1q Interface uses only 802.1q trunking encapsulation when trunking
Switch(config-if)#switchport trunk encapsulation dot1q
Switch(config-if)#switchport trunk native vlan ?
<1-1005> VLAN ID of the native VLAN when this port is in trunking mode
Switch(config-if)#switchport trunk native vlan 3
Switch(config-if)#switchport trunk allowed vlan ?
WORD VLAN IDs of the allowed VLANs when this port is in trunking mode
add add VLANs to the current list
all all VLANs
except all VLANs except the following
none no VLANs
remove remove VLANs from the current list
Switch(config-if)#switchport trunk allowed vlan 1 – 5 , 23 , 34
Switch(config-if)#switchport mode ?
access Set trunking mode to ACCESS unconditionally
dynamic Set trunking mode to dynamically negotiate access or trunk mode
trunk Set trunking mode to TRUNK unconditionally
Switch(config-if)#switchport mode trunk
Ok so now let’s confirm the port by using the show interface trunk command….
sh int trunk
Port Mode Encapsulation Status Native vlan
Fa0/2 on 802.1q trunking 3
Port Vlans allowed on trunk
Fa0/2 1-1005

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.

Error removing data from MDS using WLST

I'm new at MDS so i want to remove some data which I inserted in the wrong structure....sounds quite easy. After some looking around I should be able to do this using a deployment plan and WLST. I chose the last one as I am not realy familiar yet with deployment plans. I connect with my server and started WLST did the following:
wls:/offline> connect ('weblogic', 'mypassword' , 't3://localhost:8001')
Connecting to t3://localhost:8001 with userid weblogic ...
Successfully connected to managed Server 'soa_server1' that belongs to domain 'MY_DOMAIN'.
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
wls:/MY_DOMAIN/serverConfig> deleteMetadata(application='soa-infra', server='soa-server1', docs='/apps/deploy/*')The outcome was:
Location changed to custom tree. This is a writable tree with No root.
For more help, use help(custom)
and after a while it closed the WLST connection. Can anyone tell me how I can remove data from my repository or what is going wrong here?
Thanks in advance

Hi,
I think you were getting this error because you had your server name incorrect : soa-server1 instead of soa_server1. Also it might be possible that soa-infra is installed on the different server.
Regards,
Neeraj Sehgal

Error in java code for removing messages from a Topic

Trying to write a code using oracle.jms package to remove messages from Topic. I have a similar code with javax.jms package for removing messages from Queue and it is working well. Whereas i have written this new code for removing messages from topic using oracle.jms package as methods like CreateBrowser and CreateTopicReceiver for topic are provided in oracle package only and can't be used from javax.jms package.
Error i am getting is JMS-126: Invalid Topic specified at
         receiverTopic   = (Topic) ctx.lookup(((String)receiverProps.get( "Q_NAME")).trim() );
         System.out.println ("receiverTopic is[" + receiverTopic + "]");
         MBeanHome home = (MBeanHome) Helper.getAdminMBeanHome("username","pwd","url:port");
         ((AQjmsSession)topicSession).grantSystemPrivilege("MANAGE_ANY", "SA", true);
         for(Iterator i = home.getMBeansByType("JMSTopic").iterator();i.hasNext(); )
          WebLogicMBean wmb = (WebLogicMBean)i.next();
          System.out.println("topic name found: " + wmb.getName());
            topicBrowser   = ((AQjmsSession) topicSession).createBrowser(receiverTopic, "Edin");topic handle which i am receiving in receiverTopic is same as what i am expecting but still it says Invalid topic specified on createBrowser method. Anyone who can help me to write this type of code, please reply. If anyone has ready code for this situation, please reply with the same as i am working on a prodcution system and we are in serious situation to resolve this problem.

Hi,
I am afraid this is impossible. You need to find another solution like a filtering queue. Your messages can be sent to a queue that is monitored by let say a MDB. This MDB will maintain a map of title and only forward once a given title/message to your topic.
Hope it helps.
Arnaud
www.arjuna.com

How to remove switches from a fabric.

We have a couple of MDS9120's and a SUP1 9509 in our fabric that we want to retire.   I'm pretty sure that I don't want to just shut down these switches, unplug the cables and call it good.   Also the 9509 is the principal for two of our larger VSAN's and one of the 9120's is a principal for another that we are still using. Also, this same used to have an IVR zoneset which I think is gone, at least I don't see it when I look at IVR. Current all the switches in the fabric are running 3.31c code. Since we are planning moving to the 4.x we want remove these since they will not be supported.
So, what is the procedure to make another switch the principal of a VSAN, and once a switch is no longer a principal what is the procedure for cleanly removing it from the fabric?     If someone has some insights or can point to me to documentation that covers this, it would be greatly appreciated.
Thanks,
Jeff Blomendahl
University of Kansas Medical Center

In case anyone is still interested, I opened a TAC case on this because I could see that the information was all out there, but I wanted to make sure that I didn't miss anything that would bite me. It turnes out that it wasn't that big of a deal if you do it correctly.
To remove a switch that is the principal for a VSAN, as was mention earlier in this thread, you need to give it a lower priority and give the switch that you want to make the principal the highest priority. In our case, the "old" switch had a priority of 1 for 3 of our VSANs, so I changed it to the default of 128 and on the switch that was to be the "new" principal, the priority was set to 1. Assuming that you are in config mode on the switch, the commands from the CLI looked like this:
On the "old" switch:
fcdomain priority 128 vsan xx   (xx being the number of the VSAN, this sets the switch priority to the default of 128)
fcdomain restart xx     (again, xx being the number of the VSAN, This will non-disruptively restart the vsan on the switch and change the priority. Be aware that if you are using static domain ID's the restart may be disruptive on the switch, check the documention for more on this)
On the "new" switch:
fcdomain priority 1 vsan xx   (xx being the number of the VSAN, this sets the switch priority to the highest priority, 1)
fcdomain restart xx     (again, xx being the number of the VSAN, This will non-disruptively restart the vsan on the switch and change the priority. Be aware that if you are using static domain ID's the restart may be disruptive on the switch, check the documention for more on this)
Do this for every VSAN that the "old" switch is the principal and also on the "new" switch that is to be the principal. From what I saw in the Domain Manager this will change the priority but won't necessarily change the principal assignment. At this point the "old" switch is ready to be removed from the fabric. Obviously, since this switch was the principal, you'll want to make sure that all of the zoneset information for those zones has been replicated to the other switches in the fabric, particularly to the switch that is to become the new principal. Other than an ISL to the rest of the fabric and the connections to the management ports, there was nothing connected to the "old" switch.
At this point you can shutdown the ISL to the "old" switch from the switch that is on the other end of the ISL. At this point you will see the fabric segment (as viewed from Fabric Manager) At this point, I unplugged the management cables from the "old" switch, since I didn't want it talking to the Fabric Manager anymore. I purged the switch and after about 5 or 10 minutes the segmentation went away and the fabric returned to normal, less the "old" switch.    There was no disruption to any of the 240+ hosts that were on the affected VSANs and the switch with the priority of 1 became the principal just like it was supposed to.
I think that once the ISL has been brought down, you want to take the switch off of the network or shut it down so that it can't continue to talk to the FM. If this isn't done, FM will see that there are VSANs on that switch that are disconnected from the rest of the fabric and will show that the fabric is segmented. I went through this procedure successfully on a SUP1 MDS 9509 and a MDS 9120 that were running 3.3.1 code. One thing that did make my heart stop for a second was when I went to look at the zonesets after the segmentation cleared up. The zonesets were there, but the zones were gone!   Since my pager wasn't vibrating out of the holster, I reasoned that the zones were still there.   A quick look at the configs on the switches confirmed this. What had happened, was that the switch that I removed was the seed switch for FM when it discovered the fabric. To correct this I restarted FM and rediscovered the fabric using the "new" principal switch as the seed switch, and all of the zones were back were they were supposed to be.
Just for your piece of mind (read CYA), I recommend opening a TAC case just to have them look over your configs and make any recommendations. In our case, we had to remove IVR from one of our switches and the engineer pointed out a bug that can occur when removing IVR, and a work around for this bug.
Sorry for the long post, but I hope that this information is helpful to someone else that has to do this.
Jeff Blomendahl
Enterprise Systems Engineer
University of Kansas Medical Center

Remove U3Agent from Os X

Hello-
I'm trying to clean up my iMac and diagnose some of it's lack of responsiveness.
Upon inspecting some of my active processes, I discovered the annoying SanDisk U3Agent near the top of my CPU list. I can't figure out how to remove this from my computer (I've found plenty of tutorials about removing it from USB drivers, but not my computer).
I quit the process using Activity Monitor, but it just restarts itself.
I check it's "Open Files and Ports" and when I browse to the directory the files are supposedly located, there's nothing there (/Library/Application Support/Sandisk/Cruzer/U3Agent)
Any help would be appreciated.
-Nate

http://kb.sandisk.com/app/answers/detail/a_id/826/related/1
Even this did not remove the process from Activity Monitor. So, I have to say it's an incomplete uninstall. And a complete dud for you, because your only mission is to remove it from your active processes.
-mj
Message was edited by: macjack

Remove trunking from a port in catos?

Similar Messages

Maybe you are looking for