H323 to SIP calls
Can someone explain how h323 to SIP calls work & vice versa.
The following messages are mapped:
SIP <---> H323
INVITE - SETUP
100 Trying - Call Proc
180 Ringing - Alerting
183 Session Progress - Progress
200 OK (for INVITE) - Connect
BYE - Release Complete
With H323 to SIP CUBE, if fast start occurs on one leg, early offer needs to happen on the other (and vice versa). Most SIP devices these days to early offer (SDP in invite) so you typically need fast start enabled on both directions of the H323 leg for this design.
Check out this link for more information:
http://www.cisco.com/en/US/docs/ios/voice/cube/configuration/guide/vb-gw-h323sip_ps5640_TSD_Products_Configuration_Guide_Chapter.html
Similar Messages
-
SIP to SIP call on CME 8.6
Hi all, I'm trying to setup a video call between 9951 and IP door station 2N Helios IP that support H264 over SIP.
The audio call is working well but I see only black screen on my 9951, I don't see video also with other SIP client connected on the same CME 8.6.
This is my config:
voice service voip
no notify redirect ip2ip
clid network-provided
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
supplementary-service h450.12
redirect ip2ip
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback cisco
modem passthrough nse codec g711alaw
sip
registrar server
asymmetric payload full
voice register global
mode cme
source-address 192.168.99.204 port 5060
bandwidth video tias-modifier 512000 negotiate end-to-end
max-dn 20
max-pool 10
load 9951 sip9951.9-1-1SR1
authenticate presence
authenticate register
authenticate realm cme
timezone 23
date-format D/M/Y
tftp-path flash:
file text
create profile sync 0010244609221862
network-locale IT
user-locale IT
ntp-server 192.168.99.254 mode directedbroadcast
camera
video
voice register dn 1
number 200
allow watch
name 200
no-reg
label 200
voice register dn 2
number 201
allow watch
name 201
no-reg
label 201
voice register dn 3
number 202
allow watch
name 202
no-reg
label 202
voice register pool 1
id mac 0000.0000.0000
number 1 dn 1
presence call-list
dtmf-relay rtp-nte
username 200 password xxxxx
codec g711ulaw
camera
video
voice register pool 2
id mac 0000.0000.0000
type 9951
number 1 dn 2
presence call-list
dtmf-relay sip-notify
username 201 password xxxxx
codec g711ulaw
camera
video
voice register pool 3
id mac 0000.0000.0000
number 1 dn 3
presence call-list
dtmf-relay rtp-nte
username 202 password xxxxx
codec g711ulaw
camera
video
Anyone have a CME with SIP video call working that can help me to debug my problem?
Thanks
Enrico.Hi William
Thanks for the response.
i have attached screen shots from 2N Admin page.
can you please check and let me know the settings are correct.
door is not opening by dialing 11 during the call or after call.
Regards
shameer -
AS5400 Performance runining Both H323 and SIP
Dear All,
Is there any way to run Voice Gateway like AS5400 with two protocol H323 and SIP simultaneously? Any voice gateway performance afftected? or Voice quality affected? if we run both protocol in only one gateway?
Best Regards,
DanethAS5400 supports H.323 and SIP dial-peer at the same time without problems.
I've used AS5400 in IP2IP gateway mode to convert SIP in H.323 and vice versa with about 150 concurrent calls.
In lab I also tested SIP, H.323 and MGCP at same time.
In default configuration SIP and H.323 are both active.
AS5400 uses H.323 like default signalling protocol. Is sufficient create a voip dial-peer. To specify SIP you must use the command "session protocol sipv2" under a dial-peer.
To shut down SIP use
voice service voip
sip
call service stop
To shut down H.323 use
no gateway -
I currently have an H323 gateway with one PRI. All the phones are SCCP phones registering to CUCM. I want to add a 9971 SIP phone to this gateway. The only configuration I have done thus far is to allow connection between H323 and SIP, SIP to H323. The internal calls work fine, but when trying to dial out there is just blank noise and it eventually goes busy and disconnects. Can anyone help me set this up or point me in the right direction.
Thanks!!Hi,
Cisco IPIPGW IOS can support h323 and Sip interworking.
You can find it under voice products. -
Hello,
We have a VC system with public IP address registered to VCS-E receiving various rogue SIP calls. All of these SIP calls are 3 - 6 digit alias lasting for 32 sec each. The incoming call address is: alias@ our VC system's public IP address. All calls are video calls at 384k
To avoid the calls, I have turned off the SIP option and since then we have not received any of these calls. However, we need to connect to other devices using SIP. Is there another way to stop these incoming calls?
Thanks in advance for your help.
AmritSet the following on your endpoints:
xConfiguration SIP ListenPort: Off
xConfiguration SIP Profile 1 Outbound: On
See bug CSCue55239 for more details.
You'll also need to take steps to secure your VCS if you haven't already, turning off SIP UDP will stop the SIP calls. However, within the last year we've seen these calls come over H323 TCP, the only way to stop the H323 calls is either secure the endpoint behind your firewall, and use a CPL script on the VCS. See the sourceh323idcisco-incomingcalls discussion on how to setup a CPL.
FYI, searching the forums would be my first place to look, or bug search. It's been asked all over the place in the forums. -
Hi there,
I'm having problems modifying the 'Dialed Number (DN)' text box under 'Advanced Configuration->Patterns for RNA timeout on outbound SIP calls' of the SIP tab in the Cisco Unified Customer Voice Portal 8.5(1) opsconsole. In a nut shell, I need to change the RNA timeout but some reason when typing into the Dialed Number text box, the input is not taken. The reason I want to change this settings is because my ICM Rona is not working with CVP:
https://supportforums.cisco.com/thread/2031366
Thanks in advance for any help.
Carlos A Trivino
[email protected]Hello Dale,
CVP doesn't allow you to exceed the RNA more than 60 Seconds. If you want to configure the timer for DN Patterns you should do it via OPS console, It would update the sip.properties files in correct way, the above way is incorrect.
Regards,
Senthil -
SIP to SIP Call Failures on CME to CME - sip-ua conflict/issue?
Hi,
I have two existing CME systems which I wish to allow internal calls between. These calls will go over an IPSec VPN. However the calls are failing.
Phones DN22xx - London CME 2801 - PIX505 --- Internet ---ASA5505 - India CME 2801 - Phones DN400x
I have configured dial peers on both CME's and the IPSec VPN. I can ping between both systems. The VPN allows traffic between the interface IP's of the CME systems only.
London CME (local SCCP phones 22xx):
interface FastEthernet0/0.100
encapsulation dot1Q 100 native
ip address 10.0.10.250 255.255.255.0
voice class codec 101
codec preference 1 g729r8
codec preference 2 g711ulaw
codec preference 3 g711alaw
dial-peer voice 25 voip
description *** SIP Peer to India ***
answer-address 400.
destination-pattern 400.
voice-class codec 101
session protocol sipv2
session target ipv4:192.168.15.10
incoming called-number 400.
no vad
India CME (Local SSCP phones 400x):
interface FastEthernet0/0
ip address 192.168.15.10 255.255.255.0
voice class codec 100
codec preference 1 g729r8
codec preference 2 g711ulaw
codec preference 3 g711alaw
dial-peer voice 10 voip
description *** SIP Peer to London UK ***
answer-address 22..
destination-pattern 22..
voice-class codec 100
session protocol sipv2
session target ipv4:10.0.10.250
incoming called-number 22..
no vad
The CME system at India also has an existing SIP dial peer to a service provider and has sip-ua configured (username, password, realm and registrar).
A call from India (4005) to London (DN2207) fails, the ccsip debug attached. I'm assuming its because the sip-ua configuration is being used for these calls to when I don't want it to be. The from field shows âFrom: <sip:[email protected]â when I need this to be the internal IP 192.168.15.10.
Can anyone offer any assistance with this?
Regards,
ChrisHi,
thanks for your input however thats not the problem. 201.196.128.56 isn't an address on the router, it only has one IP and its 192.168.15.10.
The 201.196.128.56 address is the NAT'd address on the firewall. So that when a SIP call is made to the internet with sip-ua the from address is the public IP.
Chris -
cucm 10.1version - any free training videos and hand guides on understanding voice gateway h323 and SIP and how to configure one? thanks
Learncisco gives a very good introduction to CUCM - I recommend you start there.
-
Incoming sip calls are not working but outgoing is working with cme
I have CME setup with voip.ms on my 2800 router, my outgoing calls are working but my incoming calls are not. Below is my config, please let me know if it is something with my config:
voice translation-rule 3
rule 1 /^9142281\(...\)$/ /\1/
voice translation-profile INCOMING_CALL_1
translate called 3
dial-peer voice 1 voip
translation-profile incoming INCOMING_CALL_1
session protocol sipv2
session target sip-server
incoming called-number .%
voice-class codec 1
dtmf-relay rtp-nte
no vadI made the change, but I am getting no output from debug voip ccapi inout. What does concern me from debug ccsip messages is:
Aug 31 12:42:04.195: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 400 Bad Request - 'Invalid Host'
Via: SIP/2.0/UDP 107.6.67.238:5060;branch=z9hG4bK000d3c36;rport
From: "+19144410197" <sip:[email protected]>;tag=as7439b9c1
To: <sip:[email protected]:1061>;tag=829C8-2532
Date: Sun, 31 Aug 2014 12:42:04 GMT
Call-ID: [email protected]:5060
CSeq: 102 INVITE
Allow-Events: telephone-event
Reason: Q.850;cause=100
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0
I also am getting this:
voicertr2#debug ccsip error
SIP Call error tracing is enabled
voicertr2#
Aug 31 12:45:07.359: //-1/xxxxxxxxxxxx/SIP/Error/sipSPI_validate_own_ip_addr: ReqLine IP addr does not match with host IP addr
Aug 31 12:45:07.359: //-1/78AE76E98009/SIP/Error/sact_idle_new_message_invite: Invalid URL in incoming INVITE -
Running H323 and SIP on the same cisco gateway
Hi there!
I running Yate and Asterisk/IAX2 in the same box, to get H323 and convert to SIP, but I have a costumer that wants to send H323 with codec g723, but it doesn?t work good at all. So, can have H323 and SIP running on the same box like a c3600 or c2600?
Thanks,
JonasI may go out of topic, but:
1. If you want reliable protocol (H323<-> SIP) and codec conversation and
2. If you wanto to show your cusotomer nice PBX features,
then go fo either MERA MVTS or Alterteks PSS softswitches. -
How can i configure SIP call using uc320 in india
Hi,
I have one uc 320w box. now wannt to call my itally office in cost effective way.
how can use it?
i heaard about SIP calling. is it avalaible in india? or suggest me the possiblw ways.
Thanks
Sujish SudhakarHi Sudhakaran,
I think this article about SIP Configuration would help you as a step-by-step process.
Generic SIP Configuration on UC320W -
Any idea which Gateway can support H323 and SIP interworking(RFC4123)?
Hi,
Cisco IPIPGW IOS can support h323 and Sip interworking.
You can find it under voice products. -
Question regarding the use of Built-in Bridge SIP call setup to recording device
We have an application that uses Built-in Bridge (BiB) to setup a SIP call to our recording application. Recently the topology of our network was changed and for some reason the RTP for the call is not being sent. What appears to be happenning is that the SIP messages are sent from the UCCM and once the call is established we get an end call event.
We are not sure how to troubleshoot our network to determine the root cause. Any pointers will be appreciated.
Thanks.
-ArunHi
Did you ever figure this out? I am having an issue with recording calls to the PSTN from 9971 SIP phones. Station to station calls seem fine, and 7945 phones running SCCP seem fine to the PSTN.
Thanks,
Aaron -
Outbound SIP calls to invalid numbers
what is the expected behavior for a sip call to an invalid number? and what would cause it to behave differently?
Hi Ronald,
Whats the call flow ex IP Phone --SCCP-> CUCM --SIP --> CUBE -SIP-> Telco
If called number is invalid then call should not ring. Why is far end responding back with ringing.
Can you grab below debugs from the VG
++ debug voice ccapi inout
++ debug ccsip messages
HTH,
Regards,
Mohammed Noor -
SIP Calls Drop. Receive Bye From Cube 15min,30min, 45min
Hello,
Running into an odd issue. I've seen several others having this problem with calls dropping after 15min duration. But this is a bit different. Sometimes long duration calls drop at 15min. Some at 30min, others at 45min. And sometimes not at all. Call flow is such.
8831-sip--CUCM--sip--Cube--ITSP
I'm convinced this is likely a problem with the refresh timer. But I can't explain why it wouldn't just fail only at 15min. It's also interesting to note I've only seen this on the 8831. I tried getting the issue with debugs from the cube but of course it didn't happen once I turned on ccsip message.
From the callmanager traces I see the bye arrive from cube with Reason Q.850 cause=102.
The CUCM version is 9.1.2 and cube is 15.2(4)M1. I did see some odd defect in 15.1 related to this where the refresh on the cube would send out 3 invites to the ITSP on an update. I guess it would have only 33% chance of getting it right. Any help someone could provide I'd appreciate it.Thanks for the replies.
So was able to capture it while had debugs running. This time it disconnected after an hour. Same cause=102.
Now here is where it gets interesting in the debugs. I see an invite is sent 3 seconds from callmanager. I assume this is a refresher with the same call-id. Cube receives it and sends out to ITSP. With a new call-id. We then receive a bye from ITSP cause=86. Which then of course is sent to callmanager. Here are the relevent sections of debugs.
Received from cucm to cube:
820421: May 6 09:00:42.976: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
2014-05-06 09:00:43 2365082: Received:
2014-05-06 09:00:43 2365083: INVITE sip:[email protected]:5060;transport=tcp SIP/2.0
2014-05-06 09:00:43 2365084: Via: SIP/2.0/TCP 10.38.246.136:5060;branch=z9hG4bK28bab16dbd5664
2014-05-06 09:00:43 2365085: From: "Marcos Vazquez" <sip:[email protected]>;tag=3831180~dfbf10b3-6c69-4443-852f-cbf609935a6f-35009402
2014-05-06 09:00:43 2365086: To: <sip:[email protected]>;tag=5EBA2282-19C8
2014-05-06 09:00:43 2365087: Date: Tue, 06 May 2014 15:00:42 GMT
2014-05-06 09:00:43 2365088: Call-ID: [email protected]
2014-05-06 09:00:43 2365089: Supported: 100rel,timer,resource-priority,replaces
2014-05-06 09:00:43 2365090: Min-SE: 1800
2014-05-06 09:00:43 2365091: User-Agent: Cisco-CUCM9.1
2014-05-06 09:00:43 2365092: Allow: INVITE, OPTIONS, I
2014-05-06 09:00:43 2365093: NFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
2014-05-06 09:00:43 2365094: CSeq: 106 INVITE
2014-05-06 09:00:43 2365095: Max-Forwards: 70
2014-05-06 09:00:43 2365096: Expires: 300
2014-05-06 09:00:43 2365097: Allow-Events: presence, kpml
2014-05-06 09:00:43 2365098: Supported: X-cisco-srtp-fallback
2014-05-06 09:00:43 2365099: Supported: Geolocation
2014-05-06 09:00:43 2365100: P-Asserted-Identity: "Marcos Vazquez" <sip:[email protected]>
2014-05-06 09:00:43 2365101: Remote-Party-ID: "Marcos Vazquez" <sip:[email protected]>;party=calling;screen=yes;privacy=off
2014-05-06 09:00:43 2365102: Contact: <sip:[email protected]:5060;transport=tcp>
2014-05-06 09:00:43 2365103: Content-Type: application/sdp
2014-05-06 09:00:43 2365104: Content-Length: 371
2014-05-06 09:00:43 2365105:
2014-05-06 09:00:43 2365106: v=0
2014-05-06 09:00:43 2365107: o=CiscoSystemsCCM-
2014-05-06 09:00:43 2365108: SIP 3831180 1 IN IP4 10.38.246.136
2014-05-06 09:00:43 2365109: s=SIP Call
2014-05-06 09:00:43 2365110: c=IN IP4 10.96.5.28
2014-05-06 09:00:43 2365111: b=TIAS:64000
2014-05-06 09:00:43 2365112: b=AS:64
2014-05-06 09:00:43 2365113: t=0 0
2014-05-06 09:00:43 2365114: m=audio 31146 RTP/AVP 18 0 116 101
2014-05-06 09:00:43 2365115: a=rtpmap:0 PCMU/8000
2014-05-06 09:00:43 2365116: a=ptime:20
2014-05-06 09:00:43 2365117: a=rtpmap:116 iLBC/8000
2014-05-06 09:00:43 2365118: a=ptime:20
2014-05-06 09:00:43 2365119: a=maxptime:60
2014-05-06 09:00:43 2365120: a=fmtp:116 mode=20
2014-05-06 09:00:43 2365121: a=rtpmap:18 G729/8000
2014-05-06 09:00:43 2365122: a=ptime:20
2014-05-06 09:00:43 2365123: a=fmtp:18 annexb=no
2014-05-06 09:00:43 2365124: a=rtpmap:101 telephone-event/8000
2014-05-06 09:00:43 2365125: a=fmtp:101 0-15
2014-05-06 09:00:43 2365126: 5820422: May 6 09:00:42.978: //3024943/CC044C80000B/SIP/Msg/ccsipDisplayMsg:
Sent to ITSP:
Sent: Which looks like 3 are sent.
2014-05-06 09:00:43 2365128: INVITE sip:12.194.190.26:5060;transport=udp SIP/2.0
2014-05-06 09:00:43 2365129: Via: SIP/2.0/UDP 12.17.223.243:5060;branch=z9hG4bK2D699C1126
2014-05-06 09:00:43 2365130: P-Asserted-Identity: "Marcos Vazquez" <sip:[email protected]>
2014-05-06 09:00:43 2365131: From: "Marcos Vazquez" <sip:[email protected]>;tag=5EBA1628-22FC
2014-05-06 09:00:43 2365132: To: <sip:[email protected]>;tag=8088820710430052_c2b05.1.1.1385369448756.0_9843675_19511361
2014-05-06 09:00:43 2365133: Date: Tue, 06 May 2014 15:00:42 GMT
2014-05-06 09:00:43 2365134: Call-ID: [email protected]
2014-05-06 09:00:43 2365135: Supported: 100rel,timer,resource-priority,replaces,sdp-an
2014-05-06 09:00:43 2365136: at
2014-05-06 09:00:43 2365137: Min-SE: 1800
2014-05-06 09:00:43 2365138: Cisco-Guid: 3422833792-0000065536-0000746374-2297832970
2014-05-06 09:00:43 2365139: User-Agent: Cisco-SIPGateway/IOS-15.2.4.M1
2014-05-06 09:00:43 2365140: Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
2014-05-06 09:00:43 2365141: CSeq: 105 INVITE
2014-05-06 09:00:43 2365142: Max-Forwards: 70
2014-05-06 09:00:43 2365143: Timestamp: 1399388442
2014-05-06 09:00:43 2365144: Contact: <sip:[email protected]:5060>
2014-05-06 09:00:43 2365145: Expires: 60
2014-05-06 09:00:43 2365146: Allow-Events: telephone-event
2014-05-06 09:00:43 2365147: Content-Type: application/sdp
2014-05-06 09:00:43 2365148: Content-Length: 334
2014-05-06 09:00:43 2365149:
2014-05-06 09:00:43 2365150: v=0
2014-05-06 09:00:43 2365151: o=CiscoSystemsSIP-GW-UserAgent 8182 4488 IN IP4 12.17.223.243
2014-05-06 09:00:43 2365152: s=SIP Call
2014-05-06 09:00:43 2365153: c=IN IP4 1
2014-05-06 09:00:43 2365154: 2.17.223.243
2014-05-06 09:00:43 2365155: t=0 0
2014-05-06 09:00:43 2365156: m=audio 18760 RTP/AVP 18 0 100 101
2014-05-06 09:00:43 2365157: c=IN IP4 12.17.223.243
2014-05-06 09:00:43 2365158: a=rtpmap:18 G729/8000
2014-05-06 09:00:43 2365159: a=fmtp:18 annexb=no
2014-05-06 09:00:43 2365160: a=rtpmap:0 PCMU/8000
2014-05-06 09:00:43 2365161: a=rtpmap:100 X-NSE/8000
2014-05-06 09:00:43 2365162: a=fmtp:100 192-194
2014-05-06 09:00:43 2365163: a=rtpmap:101 telephone-event/8000
2014-05-06 09:00:43 2365164: a=fmtp:101 0-15
2014-05-06 09:00:43 2365165: 5820423: May 6 09:00:42.978: //3024942/CC044C80000B/SIP/Msg/ccsipDisplayMsg:
2014-05-06 09:00:43 2365166: Sent:
2014-05-06 09:00:43 2365167: SIP/2.0 100 Trying
2014-05-06 09:00:43 2365168: Via: SIP/2.0/TCP 10.38.246.136:5060;branch=z9hG4bK28bab16dbd5664
2014-05-06 09:00:43 2365169: From: "Marcos Vazquez" <sip:[email protected]>;tag=3831180~dfbf10b3-6c69-4443-852f-cbf609935a6f-35009402
2014-05-06 09:00:43 2365170: To: <sip:[email protected]>;tag=5EBA2282-19C8
2014-05-06 09:00:43 2365171: Date: Tue, 06 May 2014 15:00:42 GMT
2014-05-06 09:00:43 2365172: Call-ID: [email protected]
2014-05-06 09:00:43 2365173: CSeq: 106 INVITE
2014-05-06 09:00:43 2365174: Allow-Events: telephone-event
2014-05-06 09:00:43 2365175: Server: Cisco-SIPGateway/IOS-15.2.4.M1
2014-05-06 09:00:43 2365176: Content-Length: 0
2014-05-06 09:00:43 2365177:
2014-05-06 09:00:43 2365178: 5820424: May 6 09:00:43.479: //3024943/CC044C80000B/SIP/Msg/ccsipDisplayMsg:
2014-05-06 09:00:43 2365179: Sent:
2014-05-06 09:00:43 2365180: INVITE sip:12.194.190.26:5060;transport=udp SIP/2.0
2014-05-06 09:00:43 2365181: Via: SIP/2.0/UDP 12.17.223.243:5060;branch=z9hG4bK2D699C1126
2014-05-06 09:00:43 2365182: P-Asserted-Identity: "Marcos Vazquez" <sip:[email protected]>
2014-05-06 09:00:43 2365183: From: "Marcos Vazquez" <sip:[email protected]>;tag=5EBA1628-22FC
2014-05-06 09:00:43 2365184: To: <sip:[email protected]>;tag=8088820710430052_c2b05.1.1.1385369448756.0_9843675_19511361
2014-05-06 09:00:43 2365185: Date: Tue, 06 May 2014 15:00:43 GMT
2014-05-06 09:00:43 2365186: Call-ID: [email protected]
2014-05-06 09:00:43 2365187: Supported: 100rel,timer,resource-priority,replaces,sdp-an
2014-05-06 09:00:43 2365188: at
2014-05-06 09:00:43 2365189: Min-SE: 1800
2014-05-06 09:00:43 2365190: Cisco-Guid: 3422833792-0000065536-0000746374-2297832970
2014-05-06 09:00:43 2365191: User-Agent: Cisco-SIPGateway/IOS-15.2.4.M1
2014-05-06 09:00:43 2365192: Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
2014-05-06 09:00:43 2365193: CSeq: 105 INVITE
2014-05-06 09:00:43 2365194: Max-Forwards: 70
2014-05-06 09:00:43 2365195: Timestamp: 1399388443
2014-05-06 09:00:43 2365196: Contact: <sip:[email protected]:5060>
2014-05-06 09:00:43 2365197: Expires: 60
2014-05-06 09:00:43 2365198: Allow-Events: telephone-event
2014-05-06 09:00:43 2365199: Content-Type: application/sdp
2014-05-06 09:00:43 2365200: Content-Length: 334
2014-05-06 09:00:43 2365201:
2014-05-06 09:00:43 2365202: v=0
2014-05-06 09:00:43 2365203: o=CiscoSystemsSIP-GW-UserAgent 8182 4488 IN IP4 12.17.223.243
2014-05-06 09:00:43 2365204: s=SIP Call
2014-05-06 09:00:43 2365205: c=IN IP4 1
2014-05-06 09:00:44 2365206: 2.17.223.243
2014-05-06 09:00:44 2365207: t=0 0
2014-05-06 09:00:44 2365208: m=audio 18760 RTP/AVP 18 0 100 101
2014-05-06 09:00:44 2365209: c=IN IP4 12.17.223.243
2014-05-06 09:00:44 2365210: a=rtpmap:18 G729/8000
2014-05-06 09:00:44 2365211: a=fmtp:18 annexb=no
2014-05-06 09:00:44 2365212: a=rtpmap:0 PCMU/8000
2014-05-06 09:00:44 2365213: a=rtpmap:100 X-NSE/8000
2014-05-06 09:00:44 2365214: a=fmtp:100 192-194
2014-05-06 09:00:44 2365215: a=rtpmap:101 telephone-event/8000
2014-05-06 09:00:44 2365216: a=fmtp:101 0-15
2014-05-06 09:00:44 2365217: 5820425: May 6 09:00:44.479: //3024943/CC044C80000B/SIP/Msg/ccsipDisplayMsg:
2014-05-06 09:00:44 2365218: Sent:
2014-05-06 09:00:44 2365219: INVITE sip:12.194.190.26:5060;transport=udp SIP/2.0
2014-05-06 09:00:44 2365220: Via: SIP/2.0/UDP 12.17.223.243:5060;branch=z9hG4bK2D699C1126
2014-05-06 09:00:44 2365221: P-Asserted-Identity: "Marcos Vazquez" <sip:[email protected]>
2014-05-06 09:00:44 2365222: From: "Marcos Vazquez" <sip:[email protected]>;tag=5EBA1628-22FC
2014-05-06 09:00:44 2365223: To: <sip:[email protected]>;tag=8088820710430052_c2b05.1.1.1385369448756.0_9843675_19511361
2014-05-06 09:00:44 2365224: Date: Tue, 06 May 2014 15:00:44 GMT
2014-05-06 09:00:44 2365225: Call-ID: [email protected]
2014-05-06 09:00:44 2365226: Supported: 100rel,timer,resource-priority,replaces,sdp-an
2014-05-06 09:00:44 2365227: at
2014-05-06 09:00:44 2365228: Min-SE: 1800
2014-05-06 09:00:44 2365229: Cisco-Guid: 3422833792-0000065536-0000746374-2297832970
2014-05-06 09:00:44 2365230: User-Agent: Cisco-SIPGateway/IOS-15.2.4.M1
2014-05-06 09:00:44 2365231: Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
2014-05-06 09:00:44 2365232: CSeq: 105 INVITE
2014-05-06 09:00:44 2365233: Max-Forwards: 70
2014-05-06 09:00:44 2365234: Timestamp: 1399388444
2014-05-06 09:00:44 2365235: Contact: <sip:[email protected]:5060>
2014-05-06 09:00:44 2365236: Expires: 60
2014-05-06 09:00:44 2365237: Allow-Events: telephone-event
2014-05-06 09:00:44 2365238: Content-Type: application/sdp
2014-05-06 09:00:44 2365239: Content-Length: 334
2014-05-06 09:00:44 2365240:
2014-05-06 09:00:44 2365241: v=0
2014-05-06 09:00:44 2365242: o=CiscoSystemsSIP-GW-UserAgent 8182 4488 IN IP4 12.17.223.243
2014-05-06 09:00:44 2365243: s=SIP Call
2014-05-06 09:00:44 2365244: c=IN IP4 1
2014-05-06 09:00:44 2365245: 2.17.223.243
2014-05-06 09:00:44 2365246: t=0 0
2014-05-06 09:00:44 2365247: m=audio 18760 RTP/AVP 18 0 100 101
2014-05-06 09:00:44 2365248: c=IN IP4 12.17.223.243
2014-05-06 09:00:44 2365249: a=rtpmap:18 G729/8000
2014-05-06 09:00:44 2365250: a=fmtp:18 annexb=no
2014-05-06 09:00:44 2365251: a=rtpmap:0 PCMU/8000
2014-05-06 09:00:44 2365252: a=rtpmap:100 X-NSE/8000
2014-05-06 09:00:44 2365253: a=fmtp:100 192-194
2014-05-06 09:00:44 2365254: a=rtpmap:101 telephone-event/8000
2014-05-06 09:00:44 2365255: a=fmtp:101 0-15
2014-05-06 09:00:45 2365256: 5820426: May 6 09:00:45.147: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
2014-05-06 09:00:45 2365257: Received:
And then I don't see a response then send out a bye:
Sent:
2014-05-06 09:00:46 2365897: BYE sip:12.194.190.26:5060;transport=udp SIP/2.0
2014-05-06 09:00:46 2365898: Via: SIP/2.0/UDP 12.17.223.243:5060;branch=z9hG4bK2D69A54BC
2014-05-06 09:00:46 2365899: From: "Marcos Vazquez" <sip:[email protected]>;tag=5EBA1628-22FC
2014-05-06 09:00:46 2365900: To: <sip:[email protected]>;tag=8088820710430052_c2b05.1.1.1385369448756.0_9843675_19511361
2014-05-06 09:00:46 2365901: Date: Tue, 06 May 2014 15:00:44 GMT
2014-05-06 09:00:46 2365902: Call-ID: [email protected]
2014-05-06 09:00:46 2365903: User-Agent: Cisco-SIPGateway/IOS-15.2.4.M1
2014-05-06 09:00:46 2365904: Max-Forwards: 70
2014-05-06 09:00:46 2365905: P-Asserted-Identity: "Marcos Vazquez" <sip:[email protected]>
2014-05-06 09:00:46 2365906: Timestamp: 1399388446
2014-05-06 09:00:46 2365907: CSeq: 106 BYE
2014-05-06 09:00:46 2365908: Reason: Q.850;cause=86
2014-05-06 09:00:46 2365909: P-RTP-Stat: PS=180295,OS=3604444,PR=180354,OR=3607080,PL=0,JI=0,LA=0,DU=3603
2014-05-06 09:00:46 2365910: Content-Length: 0
2014-05-06 09:00:46 2365911:
2014-05-06 09:00:46 2365912: 5820458: May 6 09:00:46.479: //3024942/CC044C80000B/SIP/Msg/ccsipDisplayMsg:
2014-05-06 09:00:46 2365913: Sent:
2014-05-06 09:00:46 2365914: BYE sip:[email protected]:5060;transport=tcp SIP/2.0
2014-05-06 09:00:46 2365915: Via: SIP/2.0/TCP 10.38.246.166:5060;branch=z9hG4bK2D69A6E75
2014-05-06 09:00:46 2365916: From: <sip:[email protected]>;tag=5EBA2282-19C8
2014-05-06 09:00:46 2365917: To: "Marcos Vazquez" <sip:[email protected]>;tag=3831180~dfbf10b3-6c69-4443-852f-cbf609935a6f-35009402
2014-05-06 09:00:46 2365918: Date: Tue, 06 May 2014 15:00:42 GMT
2014-05-06 09:00:46 2365919: Call-ID: [email protected]
2014-05-06 09:00:46 2365920: User-Agent: Cisco-SIPGateway/IOS-15.2.4.M1
2014-05-06 09:00:46 2365921: Max-Forwards: 70
2014-05-06 09:00:46 2365922: Timestamp: 1399388446
2014-05-06 09:00:46 2365923: CSeq: 101 BYE
2014-05-06 09:00:46 2365924: Reason: Q.850;cause=102
2014-05-06 09:00:46 2365925: P-R
2014-05-06 09:00:46 2365926: TP-Stat: PS=180239,OS=3604780,PR=180295,OR=3604444,PL=0,JI=0,LA=0,DU=3603
2014-05-06 09:00:46 2365927: Content-Length: 0
2014-05-06 09:00:46 2365928:
Maybe you are looking for
-
Stateful session bean hot deployment error?
Hi, i'm getting an exception ... 1. Deploy a stateful session bean. 2. Hit the server and create an instance, then remove it. 3. Change Stateful session bean source compile and hot deploy it. 4. Hit the server and try creating an instance...exception
-
How to insert a photo in between two photos ?
I have a series of photos with all the transition in placed. I now wanted to place a still photo in between the 2 still photos. But when I drag the clip to the boundary between them, it doesn't allow me to do it as the when I release the mouse, the p
-
Why can't I delete files from networked computer?
I have my iMac G5 networked to a PC. Lately, when I try to delete PC files and directories from the Mac, I keep getting the error message: "The operation cannot be complete because you do not have sufficient privileges for some of the items." It will
-
my dear readers, I might classified myself as the least person for not knowing this but since I am "newly CLAD passer", (I just received the result TODAY!) then it will be my 1st time to have a logo here in the discussion forum. I know it will be a b
-
Ok so I am on the verge of ripping out my hair. I spent a good 2 hours trying to recreate the SIMPLEST Andrew Kramer tutorial, bought his plug ins and all that. I finally finished and it (in my opinion) looked great but when i make a movie the file b