Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Send all 4000's series numbers down route 6 1
- Thread starter RyanEOD
- Start date
NortelGuy1979
Programmer
So in LD 87 you have a CDP code (might be DSC or TSC) pointed to an RLI.
On that RLI in LD 86, you have your route, and the prompt "DMI" which probably says "0" right now.
Also in LD 86:
REQ PRT
CUST 0
FEAT DGT
DMI x
A DMI lets you insert or remove digits and change call types before the call hits the route. The CTYP prompt controls the call type. The options are NPA, NXX, SPN, CDP, UKWN, NCHG, etc....
If your Asterisk guy says the call never gets there, then something isn't right in NRS. First, from what I've seen online, most people bypass NRS when calling Asterisk --> CS1K, so that works, we'll leave it alone.
Sounds to me like either the number is failing lookup due to the call type when it hits the NRS, or the NRS can't talk to the Asterisk.
Is your NRS running a signaling server? If so, can you telnet to that IP address and log in with regular admin1 credentials from your PBX, you'll get an oam> prompt. Type:
ping "192.168.1.80"
See if the NRS/SS can even ping the Asterisk.
Matthew - Technical Support Engineer
On that RLI in LD 86, you have your route, and the prompt "DMI" which probably says "0" right now.
Also in LD 86:
REQ PRT
CUST 0
FEAT DGT
DMI x
A DMI lets you insert or remove digits and change call types before the call hits the route. The CTYP prompt controls the call type. The options are NPA, NXX, SPN, CDP, UKWN, NCHG, etc....
If your Asterisk guy says the call never gets there, then something isn't right in NRS. First, from what I've seen online, most people bypass NRS when calling Asterisk --> CS1K, so that works, we'll leave it alone.
Sounds to me like either the number is failing lookup due to the call type when it hits the NRS, or the NRS can't talk to the Asterisk.
Is your NRS running a signaling server? If so, can you telnet to that IP address and log in with regular admin1 credentials from your PBX, you'll get an oam> prompt. Type:
ping "192.168.1.80"
See if the NRS/SS can even ping the Asterisk.
Matthew - Technical Support Engineer
- Thread starter
- #22
First step, check!
ping 192.168.1.80
PING 192.168.1.80 (84=20+8+56 bytes)
64 bytes from 192.168.1.80: icmp_seq=16782. time=0. ms
64 bytes from 192.168.1.80: icmp_seq=16783. time=0. ms
64 bytes from 192.168.1.80: icmp_seq=16784. time=0. ms
64 bytes from 192.168.1.80: icmp_seq=16785. time=0. ms
----192.168.1.80 PING Statistics----
4 packets transmitted, 4 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0
oam>
ping 192.168.1.80
PING 192.168.1.80 (84=20+8+56 bytes)
64 bytes from 192.168.1.80: icmp_seq=16782. time=0. ms
64 bytes from 192.168.1.80: icmp_seq=16783. time=0. ms
64 bytes from 192.168.1.80: icmp_seq=16784. time=0. ms
64 bytes from 192.168.1.80: icmp_seq=16785. time=0. ms
----192.168.1.80 PING Statistics----
4 packets transmitted, 4 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0
oam>
- Thread starter
- #23
NortelGuy1979
Programmer
Backing up to the PBX a bit; can you:
PRT your SIP route RDB
LTM the trunks in your SIP route
STAT all the trunks in that route
Do you make VoIP calls out that route to any other peer system? If those work, then you can ignore those 3 commands above...
Build a new DMI to set the CTYP as UKWN
Set the NRS numbering type as Private Special
If that doesn't work, try the DMI to set the CTYP as SPN
During all this, leave your DCH trace on and ask your Asterisk guru to be watching the SIP trace...
Matthew - Technical Support Engineer
PRT your SIP route RDB
LTM the trunks in your SIP route
STAT all the trunks in that route
Do you make VoIP calls out that route to any other peer system? If those work, then you can ignore those 3 commands above...
Build a new DMI to set the CTYP as UKWN
Set the NRS numbering type as Private Special
If that doesn't work, try the DMI to set the CTYP as SPN
During all this, leave your DCH trace on and ask your Asterisk guru to be watching the SIP trace...
Matthew - Technical Support Engineer
bhassell2000
Technical User
DMI 0 is a default DMI in the PBX, it doesn't list but its there
Thanks,
Buddy
Linked in Profile
Thanks,
Buddy
Linked in Profile
NortelGuy1979
Programmer
Wait. What is your Asterisk IP address?
What is your NRS (TLAN, if it's on the SS) IP address?
What is your SS ELAN and TLAN IP address?
What is your PBX ELAN IP address?
When you pinged 192.168.1.80, your travel time was 0ms. That is NOT possible unless you're pinging yourself.
Did you put in the Asterisk endpoint using the signaling server IP address?
Matthew - Technical Support Engineer
What is your NRS (TLAN, if it's on the SS) IP address?
What is your SS ELAN and TLAN IP address?
What is your PBX ELAN IP address?
When you pinged 192.168.1.80, your travel time was 0ms. That is NOT possible unless you're pinging yourself.
Did you put in the Asterisk endpoint using the signaling server IP address?
Matthew - Technical Support Engineer
- Thread starter
- #27
SO many questions Ok, in order:
PRT your SIP route RDB:
TYPE RDB
CUST 00
ROUT 6
DES SIP
TKTP TIE
M911P NO
ESN NO
CNVT NO
SAT NO
RCLS EXT
VTRK YES
ZONE 003
PCID SIP
CRID NO
NODE 1
DTRK NO
ISDN YES
MODE ISLD
DCH 6
IFC SL1
PNI 00001
NCNA NO
NCRD NO
FALT NO
CTYP UKWN
INAC NO
ISAR NO
DAPC NO
PTYP ATT
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD 86
TCPP NO
TARG 04
CLEN 1
BILN NO
OABS
INST
IDC NO
DCNO 0 *
NDNO 0
DEXT NO
ANTK
SIGO STD
STYP SDAT
ICIS YES
TIMR ICF 512
OGF 512
EOD 13952
DSI 34944
NRD 10112
DDL 70
ODT 4096
RGV 640
GRD 896
SFB 3
NBS 2048
NBL 4096
PAGE 002
TFD 0
SST 5 0
NEDC ORG
FEDC ORG
CPDC NO
DLTN NO
HOLD 02 02 40
SEIZ 02 02
SVFL 02 02
DRNG NO
CDR NO
MUS YES
MRT 9
MANO NO
FRL 0 0
FRL 1 0
FRL 2 0
FRL 3 0
FRL 4 0
FRL 5 0
FRL 6 0
FRL 7 0
AUTH NO
TDET NO
TTBL 0
ATAN NO
OHTD NO
PLEV 2
ALRM NO
ART 0
SGRP 0
ARDN NO
AACR NO
LTM the trunks in your SIP route:
REQ: ltm
CUST 0
ROUT 6
TYPE TLST
TKTP TIE
ROUT 6
DES SIP
TN 096 0 02 00 MBER 1 SIP_TRUNK
STAT all the trunks in that route:
>ld 20
REQ: stat 96 0 2 0
IDLE REGISTERED
Do you make VoIP calls out that route to any other peer system? Negative, new route
Build a new DMI to set the CTYP as UKWN
Set the NRS numbering type as Private Special
Tried both, no dice
Trace still going:
DCH 6 OMSG SETUP REF 00000186 CH 96 0 2 0 TOD 17:11:40
FEAT :CRID
FEAT :CDS
FEAT :NCID
PROGRESS: ORIG ADDR IS NOT ISDN
CALLING #:6785 NUM PLAN: PRIVATE/UNKNOWN (UNKNOWN)
CALLED #:4790 NUM PLAN: PRIVATE/NETWORK SPECIFIC (SPN)
DCH 6 IMSG CALLPROC REF 00000186 CH 96 0 2 0 TOD 17:11:40
DCH 6 IMSG DISC REF 00000186 CH 96 0 2 0 TOD 17:11:40
CAUSE :NTWK TEMP FAIL
DCH 6 OMSG RELEASE REF 00000186 CH 96 0 2 0 TOD 17:11:40
DCH 6 IMSG REL COMP REF 00000186 CH 96 0 2 0 TOD 17:11:40
***
Ok, now for the other set of questions:
What is your Asterisk IP address? 192.168.1.80
What is your NRS (TLAN, if it's on the SS) IP address? Well I don't know for positive but when I go into the NRS website it is: 192.168.1.32
My Element Manager and what I telnet to program the switch is 192.168.1.30
Does this help?
PRT your SIP route RDB:
TYPE RDB
CUST 00
ROUT 6
DES SIP
TKTP TIE
M911P NO
ESN NO
CNVT NO
SAT NO
RCLS EXT
VTRK YES
ZONE 003
PCID SIP
CRID NO
NODE 1
DTRK NO
ISDN YES
MODE ISLD
DCH 6
IFC SL1
PNI 00001
NCNA NO
NCRD NO
FALT NO
CTYP UKWN
INAC NO
ISAR NO
DAPC NO
PTYP ATT
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD 86
TCPP NO
TARG 04
CLEN 1
BILN NO
OABS
INST
IDC NO
DCNO 0 *
NDNO 0
DEXT NO
ANTK
SIGO STD
STYP SDAT
ICIS YES
TIMR ICF 512
OGF 512
EOD 13952
DSI 34944
NRD 10112
DDL 70
ODT 4096
RGV 640
GRD 896
SFB 3
NBS 2048
NBL 4096
PAGE 002
TFD 0
SST 5 0
NEDC ORG
FEDC ORG
CPDC NO
DLTN NO
HOLD 02 02 40
SEIZ 02 02
SVFL 02 02
DRNG NO
CDR NO
MUS YES
MRT 9
MANO NO
FRL 0 0
FRL 1 0
FRL 2 0
FRL 3 0
FRL 4 0
FRL 5 0
FRL 6 0
FRL 7 0
AUTH NO
TDET NO
TTBL 0
ATAN NO
OHTD NO
PLEV 2
ALRM NO
ART 0
SGRP 0
ARDN NO
AACR NO
LTM the trunks in your SIP route:
REQ: ltm
CUST 0
ROUT 6
TYPE TLST
TKTP TIE
ROUT 6
DES SIP
TN 096 0 02 00 MBER 1 SIP_TRUNK
STAT all the trunks in that route:
>ld 20
REQ: stat 96 0 2 0
IDLE REGISTERED
Do you make VoIP calls out that route to any other peer system? Negative, new route
Build a new DMI to set the CTYP as UKWN
Set the NRS numbering type as Private Special
Tried both, no dice
Trace still going:
DCH 6 OMSG SETUP REF 00000186 CH 96 0 2 0 TOD 17:11:40
FEAT :CRID
FEAT :CDS
FEAT :NCID
PROGRESS: ORIG ADDR IS NOT ISDN
CALLING #:6785 NUM PLAN: PRIVATE/UNKNOWN (UNKNOWN)
CALLED #:4790 NUM PLAN: PRIVATE/NETWORK SPECIFIC (SPN)
DCH 6 IMSG CALLPROC REF 00000186 CH 96 0 2 0 TOD 17:11:40
DCH 6 IMSG DISC REF 00000186 CH 96 0 2 0 TOD 17:11:40
CAUSE :NTWK TEMP FAIL
DCH 6 OMSG RELEASE REF 00000186 CH 96 0 2 0 TOD 17:11:40
DCH 6 IMSG REL COMP REF 00000186 CH 96 0 2 0 TOD 17:11:40
***
Ok, now for the other set of questions:
What is your Asterisk IP address? 192.168.1.80
What is your NRS (TLAN, if it's on the SS) IP address? Well I don't know for positive but when I go into the NRS website it is: 192.168.1.32
My Element Manager and what I telnet to program the switch is 192.168.1.30
Does this help?
NortelGuy1979
Programmer
Let's do a SIP trace on your signaling server... telnet to it, and at the oam> prompt:
oam> SIPOutput 1
oam> SIPTraceLevel 1
oam> SIPCallTrace on
Now make your call and capture it all.
Is this your first SIP implementation on the PBX? Never had SIP on it before? I'm surprised you only have one SIP trunk...
Matthew - Technical Support Engineer
oam> SIPOutput 1
oam> SIPTraceLevel 1
oam> SIPCallTrace on
Now make your call and capture it all.
Is this your first SIP implementation on the PBX? Never had SIP on it before? I'm surprised you only have one SIP trunk...
Matthew - Technical Support Engineer
- Thread starter
- #29
NICE command, that is going in the notebook too! 
Yes this is my first SIP attempt, we have an order in for like 30 more SIP trunks, just wanted to get 1 setup first to make sure it worked. We were/are a Nortel Developing partner so last time we upgraded the switch they tossed in 1 SIP license. Here is the trace:
15/09/2010 17:38:45 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
SIPCallTrace: (15/09/10 17:38:46) Outgoing -- method INVITE(0) chid: 6 Far End Signaling IP: 192.168.1.30:5060 Calling: 6785 Called : 4790
SIPCallTrace: (15/09/10 17:38:46)
INVITE sip:4790@tmetss.corp.tmetrics.com;user=phone SIP/2.0
From: <sip:6785@tmetss.corp.tmetrics.com;user=phone>;tag=192ef018-1e01a8c0-13c4-40030-473b8b-466a9f2d-473b8b
To: <sip:4790@tmetss.corp.tmetrics.com;user=phone>
SIPCallTrace: (15/09/10 17:38:46)
Call-ID: 18a5cee8-1e01a8c0-13c4-40030-473b8b-2e80af97-473b8b
CSeq: 1 INVITE
Via: SIP/2.0/UDP 192.168.1.30:5060;branch=z9hG4bK-473b8b-164098c4-4379e2b2
Max-Forwards: 70
Supported: 100rel,x-nortel-sipvc,replaces,timer
SIPCallTrace: (15/09/10 17:38:46)
User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31
P-Asserted-Identity: <sip:6785@tmetss.corp.tmetrics.com;user=phone>
Privacy: none
History-Info: <sip:4790@tmetss.corp.tmetrics.com;user=phone>;index=1
SIPCallTrace: (15/09/10 17:38:46)
x-nt-corr-id: 000000111126250f09@001bbafd28df-0ceef522
Contact: <sip:6785@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.30;transport=tcp;user=phone>
Min-SE: 0
SIPCallTrace: (15/09/10 17:38:46)
Allow: INVITE,ACK,BYE,REGISTER,REFER,NOTIFY,CANCEL,PRACK,OPTIONS,INFO,SUBSCRIBE,UPDATE
Content-Type: multipart/mixed;boundary=unique-boundary-1
Content-Length: 796
--unique-boundary-1
Content-Type: application/sdp
v=0
SIPCallTrace: (15/09/10 17:38:46)
o=- 179780 1 IN IP4 192.168.1.30
s=-
t=0 0
m=audio 5356 RTP/AVP 0 8 18 101 111
c=IN IP4 192.168.1.31
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:111 X-nt-inforeq/8000
a=ptime:20
SIPCallTrace: (15/09/10 17:38:46)
a=sendrecv
--unique-boundary-1
Content-Type: application/x-nt-mcdn-frag-hex;version=sse-5.00.31;base=x2611
Content-Disposition: signal;handling=optional
05008601
0107130081900000a200
09090f00e9a0830001000600
SIPCallTrace: (15/09/10 17:38:46)
1315070011fa0f00a10d02010102020100cc040000894d00
1e0403008183
460e01000a0001000100010000000000
--unique-boundary-1
Content-Type: application/x-nt-epid-frag-hex;version=sse-5.00.31;base=x2611
SIPCallTrace: (15/09/10 17:38:46)
Content-Disposition: signal;handling=optional
011201
00:1b:ba:fd:29:d7
--unique-boundary-1--
SIPCallTrace: (15/09/10 17:38:46) Outgoing -- response 503 Service Unavailable chid: 0 Far End Signaling IP: 192.168.1.30:5060 Calling: 6785 Called : 4790
SIPCallTrace: (15/09/10 17:38:46)
SIP/2.0 503 Service Unavailable
From: <sip:6785@tmetss.corp.tmetrics.com;user=phone>;tag=192ef018-1e01a8c0-13c4-40030-473b8b-466a9f2d-473b8b
SIPCallTrace: (15/09/10 17:38:46)
To: <sip:4790@tmetss.corp.tmetrics.com;user=phone>;tag=192f1958-1e01a8c0-13c4-40030-473b8b-77ac7e79-473b8b
Call-ID: 18a5cee8-1e01a8c0-13c4-40030-473b8b-2e80af97-473b8b
CSeq: 1 INVITE
SIPCallTrace: (15/09/10 17:38:46)
Via: SIP/2.0/TCP 192.168.1.30:5060;branch=z9hG4bK-473b8b-164098c4-4379e2b2
Supported: 100rel,x-nortel-sipvc,replaces,timer
User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31
SIPCallTrace: (15/09/10 17:38:46)
Allow: INVITE,ACK,BYE,REGISTER,REFER,NOTIFY,CANCEL,PRACK,OPTIONS,INFO,SUBSCRIBE,UPDATE
Content-Length: 0
SIPCallTrace: (15/09/10 17:38:46) Incoming -- response 503 Service Unavailable chid: 6 Far End Signaling IP: 192.168.1.30:5060 Calling: 6785 Called : 4790
SIPCallTrace: (15/09/10 17:38:46)
SIP/2.0 503 Service Unavailable
From: <sip:6785@tmetss.corp.tmetrics.com;user=phone>;tag=192ef018-1e01a8c0-13c4-40030-473b8b-466a9f2d-473b8b
SIPCallTrace: (15/09/10 17:38:46)
To: <sip:4790@tmetss.corp.tmetrics.com;user=phone>;tag=192f1958-1e01a8c0-13c4-40030-473b8b-77ac7e79-473b8b
Call-ID: 18a5cee8-1e01a8c0-13c4-40030-473b8b-2e80af97-473b8b
CSeq: 1 INVITE
SIPCallTrace: (15/09/10 17:38:46)
Via: SIP/2.0/TCP 192.168.1.30:5060;branch=z9hG4bK-473b8b-164098c4-4379e2b2
Supported: 100rel,x-nortel-sipvc,replaces,timer
User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31
SIPCallTrace: (15/09/10 17:38:46)
Allow: INVITE,ACK,BYE,REGISTER,REFER,NOTIFY,CANCEL,PRACK,OPTIONS,INFO,SUBSCRIBE,UPDATE
Content-Length: 0
SIPCallTrace: (15/09/10 17:38:46) Outgoing -- method ACK(1) chid: 6 Far End Signaling IP: 192.168.1.30:5060 Calling: 6785 Called : 4790
SIPCallTrace: (15/09/10 17:38:46)
ACK sip:4790@tmetss.corp.tmetrics.com;user=phone SIP/2.0
From: <sip:6785@tmetss.corp.tmetrics.com;user=phone>;tag=192ef018-1e01a8c0-13c4-40030-473b8b-466a9f2d-473b8b
SIPCallTrace: (15/09/10 17:38:46)
To: <sip:4790@tmetss.corp.tmetrics.com;user=phone>;tag=192f1958-1e01a8c0-13c4-40030-473b8b-77ac7e79-473b8b
Call-ID: 18a5cee8-1e01a8c0-13c4-40030-473b8b-2e80af97-473b8b
CSeq: 1 ACK
SIPCallTrace: (15/09/10 17:38:46)
Via: SIP/2.0/TCP 192.168.1.30:5060;branch=z9hG4bK-473b8b-164098c4-4379e2b2
Max-Forwards: 70
User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31
x-nt-corr-id: 000000111126250f09@001bbafd28df-0ceef522
SIPCallTrace: (15/09/10 17:38:46)
Contact: <sip:6785@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.30;transport=tcp;user=phone>
Allow: INVITE,ACK,BYE,REGISTER,REFER,NOTIFY,CANCEL,PRACK,OPTIONS,INFO,SUBSCRIBE,UPDATE
Content-Length: 0
SIPCallTrace: (15/09/10 17:38:46) Incoming -- method ACK(1) chid: 0 Far End Signaling IP: 192.168.1.30:5060 Calling: 6785 Called : 4790
SIPCallTrace: (15/09/10 17:38:46)
ACK sip:4790@tmetss.corp.tmetrics.com;user=phone SIP/2.0
From: <sip:6785@tmetss.corp.tmetrics.com;user=phone>;tag=192ef018-1e01a8c0-13c4-40030-473b8b-466a9f2d-473b8b
SIPCallTrace: (15/09/10 17:38:46)
To: <sip:4790@tmetss.corp.tmetrics.com;user=phone>;tag=192f1958-1e01a8c0-13c4-40030-473b8b-77ac7e79-473b8b
Call-ID: 18a5cee8-1e01a8c0-13c4-40030-473b8b-2e80af97-473b8b
CSeq: 1 ACK
SIPCallTrace: (15/09/10 17:38:46)
Via: SIP/2.0/TCP 192.168.1.30:5060;branch=z9hG4bK-473b8b-164098c4-4379e2b2
Max-Forwards: 70
User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31
x-nt-corr-id: 000000111126250f09@001bbafd28df-0ceef522
SIPCallTrace: (15/09/10 17:38:46)
Contact: <sip:6785@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.30;transport=tcp;user=phone>
Allow: INVITE,ACK,BYE,REGISTER,REFER,NOTIFY,CANCEL,PRACK,OPTIONS,INFO,SUBSCRIBE,UPDATE
Content-Length: 0
15/09/2010 17:38:46 LOG0004 SIPNPM: sipNpmCallLegStateChangedEv: Call rejected from Calling party : 6785 to Called party : 4790 as the request for idle channel from VTRK failed for hCallLeg 0x18a5d078
15/09/2010 17:38:54 LOG0003 GKNPM: gkNpmLightRRQ: Non-Ras Endpoint tmetss 192.168.1.30 is trying to register
15/09/2010 17:38:54 LOG0004 GKNPM: ITG4065 Endpoint tmetss 192.168.1.30 status: Unregistered (93)
15/09/2010 17:38:54 LOG0003 NPM: cmEvRASReject: GK 192.168.1.32 Registration rejected
15/09/2010 17:39:00 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
15/09/2010 17:39:04 LOG0004 GKNPM: ITG4065 Endpoint tmetss 192.168.1.30 status: Registered (93)
15/09/2010 17:39:04 LOG0006 NPM: cmEvRASConfirm: GK 192.168.1.32, Registration OK, rasSession(0x2d112cec)
15/09/2010 17:39:15 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
Yes this is my first SIP attempt, we have an order in for like 30 more SIP trunks, just wanted to get 1 setup first to make sure it worked. We were/are a Nortel Developing partner so last time we upgraded the switch they tossed in 1 SIP license. Here is the trace:15/09/2010 17:38:45 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
SIPCallTrace: (15/09/10 17:38:46) Outgoing -- method INVITE(0) chid: 6 Far End Signaling IP: 192.168.1.30:5060 Calling: 6785 Called : 4790
SIPCallTrace: (15/09/10 17:38:46)
INVITE sip:4790@tmetss.corp.tmetrics.com;user=phone SIP/2.0
From: <sip:6785@tmetss.corp.tmetrics.com;user=phone>;tag=192ef018-1e01a8c0-13c4-40030-473b8b-466a9f2d-473b8b
To: <sip:4790@tmetss.corp.tmetrics.com;user=phone>
SIPCallTrace: (15/09/10 17:38:46)
Call-ID: 18a5cee8-1e01a8c0-13c4-40030-473b8b-2e80af97-473b8b
CSeq: 1 INVITE
Via: SIP/2.0/UDP 192.168.1.30:5060;branch=z9hG4bK-473b8b-164098c4-4379e2b2
Max-Forwards: 70
Supported: 100rel,x-nortel-sipvc,replaces,timer
SIPCallTrace: (15/09/10 17:38:46)
User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31
P-Asserted-Identity: <sip:6785@tmetss.corp.tmetrics.com;user=phone>
Privacy: none
History-Info: <sip:4790@tmetss.corp.tmetrics.com;user=phone>;index=1
SIPCallTrace: (15/09/10 17:38:46)
x-nt-corr-id: 000000111126250f09@001bbafd28df-0ceef522
Contact: <sip:6785@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.30;transport=tcp;user=phone>
Min-SE: 0
SIPCallTrace: (15/09/10 17:38:46)
Allow: INVITE,ACK,BYE,REGISTER,REFER,NOTIFY,CANCEL,PRACK,OPTIONS,INFO,SUBSCRIBE,UPDATE
Content-Type: multipart/mixed;boundary=unique-boundary-1
Content-Length: 796
--unique-boundary-1
Content-Type: application/sdp
v=0
SIPCallTrace: (15/09/10 17:38:46)
o=- 179780 1 IN IP4 192.168.1.30
s=-
t=0 0
m=audio 5356 RTP/AVP 0 8 18 101 111
c=IN IP4 192.168.1.31
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:111 X-nt-inforeq/8000
a=ptime:20
SIPCallTrace: (15/09/10 17:38:46)
a=sendrecv
--unique-boundary-1
Content-Type: application/x-nt-mcdn-frag-hex;version=sse-5.00.31;base=x2611
Content-Disposition: signal;handling=optional
05008601
0107130081900000a200
09090f00e9a0830001000600
SIPCallTrace: (15/09/10 17:38:46)
1315070011fa0f00a10d02010102020100cc040000894d00
1e0403008183
460e01000a0001000100010000000000
--unique-boundary-1
Content-Type: application/x-nt-epid-frag-hex;version=sse-5.00.31;base=x2611
SIPCallTrace: (15/09/10 17:38:46)
Content-Disposition: signal;handling=optional
011201
00:1b:ba:fd:29:d7
--unique-boundary-1--
SIPCallTrace: (15/09/10 17:38:46) Outgoing -- response 503 Service Unavailable chid: 0 Far End Signaling IP: 192.168.1.30:5060 Calling: 6785 Called : 4790
SIPCallTrace: (15/09/10 17:38:46)
SIP/2.0 503 Service Unavailable
From: <sip:6785@tmetss.corp.tmetrics.com;user=phone>;tag=192ef018-1e01a8c0-13c4-40030-473b8b-466a9f2d-473b8b
SIPCallTrace: (15/09/10 17:38:46)
To: <sip:4790@tmetss.corp.tmetrics.com;user=phone>;tag=192f1958-1e01a8c0-13c4-40030-473b8b-77ac7e79-473b8b
Call-ID: 18a5cee8-1e01a8c0-13c4-40030-473b8b-2e80af97-473b8b
CSeq: 1 INVITE
SIPCallTrace: (15/09/10 17:38:46)
Via: SIP/2.0/TCP 192.168.1.30:5060;branch=z9hG4bK-473b8b-164098c4-4379e2b2
Supported: 100rel,x-nortel-sipvc,replaces,timer
User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31
SIPCallTrace: (15/09/10 17:38:46)
Allow: INVITE,ACK,BYE,REGISTER,REFER,NOTIFY,CANCEL,PRACK,OPTIONS,INFO,SUBSCRIBE,UPDATE
Content-Length: 0
SIPCallTrace: (15/09/10 17:38:46) Incoming -- response 503 Service Unavailable chid: 6 Far End Signaling IP: 192.168.1.30:5060 Calling: 6785 Called : 4790
SIPCallTrace: (15/09/10 17:38:46)
SIP/2.0 503 Service Unavailable
From: <sip:6785@tmetss.corp.tmetrics.com;user=phone>;tag=192ef018-1e01a8c0-13c4-40030-473b8b-466a9f2d-473b8b
SIPCallTrace: (15/09/10 17:38:46)
To: <sip:4790@tmetss.corp.tmetrics.com;user=phone>;tag=192f1958-1e01a8c0-13c4-40030-473b8b-77ac7e79-473b8b
Call-ID: 18a5cee8-1e01a8c0-13c4-40030-473b8b-2e80af97-473b8b
CSeq: 1 INVITE
SIPCallTrace: (15/09/10 17:38:46)
Via: SIP/2.0/TCP 192.168.1.30:5060;branch=z9hG4bK-473b8b-164098c4-4379e2b2
Supported: 100rel,x-nortel-sipvc,replaces,timer
User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31
SIPCallTrace: (15/09/10 17:38:46)
Allow: INVITE,ACK,BYE,REGISTER,REFER,NOTIFY,CANCEL,PRACK,OPTIONS,INFO,SUBSCRIBE,UPDATE
Content-Length: 0
SIPCallTrace: (15/09/10 17:38:46) Outgoing -- method ACK(1) chid: 6 Far End Signaling IP: 192.168.1.30:5060 Calling: 6785 Called : 4790
SIPCallTrace: (15/09/10 17:38:46)
ACK sip:4790@tmetss.corp.tmetrics.com;user=phone SIP/2.0
From: <sip:6785@tmetss.corp.tmetrics.com;user=phone>;tag=192ef018-1e01a8c0-13c4-40030-473b8b-466a9f2d-473b8b
SIPCallTrace: (15/09/10 17:38:46)
To: <sip:4790@tmetss.corp.tmetrics.com;user=phone>;tag=192f1958-1e01a8c0-13c4-40030-473b8b-77ac7e79-473b8b
Call-ID: 18a5cee8-1e01a8c0-13c4-40030-473b8b-2e80af97-473b8b
CSeq: 1 ACK
SIPCallTrace: (15/09/10 17:38:46)
Via: SIP/2.0/TCP 192.168.1.30:5060;branch=z9hG4bK-473b8b-164098c4-4379e2b2
Max-Forwards: 70
User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31
x-nt-corr-id: 000000111126250f09@001bbafd28df-0ceef522
SIPCallTrace: (15/09/10 17:38:46)
Contact: <sip:6785@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.30;transport=tcp;user=phone>
Allow: INVITE,ACK,BYE,REGISTER,REFER,NOTIFY,CANCEL,PRACK,OPTIONS,INFO,SUBSCRIBE,UPDATE
Content-Length: 0
SIPCallTrace: (15/09/10 17:38:46) Incoming -- method ACK(1) chid: 0 Far End Signaling IP: 192.168.1.30:5060 Calling: 6785 Called : 4790
SIPCallTrace: (15/09/10 17:38:46)
ACK sip:4790@tmetss.corp.tmetrics.com;user=phone SIP/2.0
From: <sip:6785@tmetss.corp.tmetrics.com;user=phone>;tag=192ef018-1e01a8c0-13c4-40030-473b8b-466a9f2d-473b8b
SIPCallTrace: (15/09/10 17:38:46)
To: <sip:4790@tmetss.corp.tmetrics.com;user=phone>;tag=192f1958-1e01a8c0-13c4-40030-473b8b-77ac7e79-473b8b
Call-ID: 18a5cee8-1e01a8c0-13c4-40030-473b8b-2e80af97-473b8b
CSeq: 1 ACK
SIPCallTrace: (15/09/10 17:38:46)
Via: SIP/2.0/TCP 192.168.1.30:5060;branch=z9hG4bK-473b8b-164098c4-4379e2b2
Max-Forwards: 70
User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31
x-nt-corr-id: 000000111126250f09@001bbafd28df-0ceef522
SIPCallTrace: (15/09/10 17:38:46)
Contact: <sip:6785@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.30;transport=tcp;user=phone>
Allow: INVITE,ACK,BYE,REGISTER,REFER,NOTIFY,CANCEL,PRACK,OPTIONS,INFO,SUBSCRIBE,UPDATE
Content-Length: 0
15/09/2010 17:38:46 LOG0004 SIPNPM: sipNpmCallLegStateChangedEv: Call rejected from Calling party : 6785 to Called party : 4790 as the request for idle channel from VTRK failed for hCallLeg 0x18a5d078
15/09/2010 17:38:54 LOG0003 GKNPM: gkNpmLightRRQ: Non-Ras Endpoint tmetss 192.168.1.30 is trying to register
15/09/2010 17:38:54 LOG0004 GKNPM: ITG4065 Endpoint tmetss 192.168.1.30 status: Unregistered (93)
15/09/2010 17:38:54 LOG0003 NPM: cmEvRASReject: GK 192.168.1.32 Registration rejected
15/09/2010 17:39:00 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
15/09/2010 17:39:04 LOG0004 GKNPM: ITG4065 Endpoint tmetss 192.168.1.30 status: Registered (93)
15/09/2010 17:39:04 LOG0006 NPM: cmEvRASConfirm: GK 192.168.1.32, Registration OK, rasSession(0x2d112cec)
15/09/2010 17:39:15 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
NortelGuy1979
Programmer
Sorry, had to help a sales rep figure out that his CFW key was active...
Ok, first SIPCallTrace off to turn off all that logging.
Then, can I get a TNB of your one SIP trunk?
Then, back in the SS, can I get:
oam> vtrkShow
I'm looking at that SIP trace in the mean time; looks like your node IP is 192.168.1.30 and your SS/NRS real IP is 192.168.1.32
Of course, our lab PBX is so hosed at the moment I can't duplicate this. ;-)
Matthew - Technical Support Engineer
Ok, first SIPCallTrace off to turn off all that logging.
Then, can I get a TNB of your one SIP trunk?
Then, back in the SS, can I get:
oam> vtrkShow
I'm looking at that SIP trace in the mean time; looks like your node IP is 192.168.1.30 and your SS/NRS real IP is 192.168.1.32
Of course, our lab PBX is so hosed at the moment I can't duplicate this. ;-)
Matthew - Technical Support Engineer
NortelGuy1979
Programmer
Also, can we see the signaling server SIP gateway config, as well as the endpoint configuration in NRS for you CS1000? Sorry, I know not much of this is text and you can't do screenshots...
-Matthew
Matthew - Technical Support Engineer
-Matthew
Matthew - Technical Support Engineer
- Thread starter
- #32
SIP Gateway Config:
Endpoint Name: tmetss
Endpoint Desciption: Static SIP
Static endpoint address: 1923168.1.32
H.323 Support: Not RAS H.323 endpoint
SIP Support: Static SIP endpoint
SIP transport: TCP
SIP port: 5060
No Routing entries for the tmetss . . . is that my problem?
I have no problem typing it all out . . as I really appreciate the help!
Endpoint Name: tmetss
Endpoint Desciption: Static SIP
Static endpoint address: 1923168.1.32
H.323 Support: Not RAS H.323 endpoint
SIP Support: Static SIP endpoint
SIP transport: TCP
SIP port: 5060
No Routing entries for the tmetss . . . is that my problem?
I have no problem typing it all out . . as I really appreciate the help!
- Thread starter
- #33
I do see these errors though, makes me believe something is wrong on the tmetss setup:
oam> 16/09/2010 15:44:58 LOG0003 GKNPM: gkNpmLightRRQ: Non-Ras Endpoint tmetss 192.168.1.30 is trying to register
16/09/2010 15:44:58 LOG0004 GKNPM: ITG4065 Endpoint tmetss 192.168.1.30 status: Unregistered (93)
16/09/2010 15:44:58 LOG0003 NPM: cmEvRASReject: GK 192.168.1.32 Registration rejected
?16/09/2010 15:45:08 LOG0004 GKNPM: ITG4065 Endpoint tmetss 192.168.1.30 status: Registered (93)
16/09/2010 15:45:08 LOG0006 NPM: cmEvRASConfirm: GK 192.168.1.32, Registration OK, rasSession(0x2d113dbc)
16/09/2010 15:45:09 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
oam> 16/09/2010 15:44:58 LOG0003 GKNPM: gkNpmLightRRQ: Non-Ras Endpoint tmetss 192.168.1.30 is trying to register
16/09/2010 15:44:58 LOG0004 GKNPM: ITG4065 Endpoint tmetss 192.168.1.30 status: Unregistered (93)
16/09/2010 15:44:58 LOG0003 NPM: cmEvRASReject: GK 192.168.1.32 Registration rejected
?16/09/2010 15:45:08 LOG0004 GKNPM: ITG4065 Endpoint tmetss 192.168.1.30 status: Registered (93)
16/09/2010 15:45:08 LOG0006 NPM: cmEvRASConfirm: GK 192.168.1.32, Registration OK, rasSession(0x2d113dbc)
16/09/2010 15:45:09 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
NortelGuy1979
Programmer
Your CS1K endpoint isn't set up right; it should be a dynamic SIP endpoint that supports registration. Can you send me the SIP settings from the signaling server?
Element Manger --> IP Telephony --> Nodes, Servers, etc... then open the node then expand the signaling server.
However, I don't see that it would deny the call; I could be wrong though.
-Matthew
Matthew - Technical Support Engineer
Element Manger --> IP Telephony --> Nodes, Servers, etc... then open the node then expand the signaling server.
However, I don't see that it would deny the call; I could be wrong though.
-Matthew
Matthew - Technical Support Engineer
- Thread starter
- #35
NortelGuy1979
Programmer
It's that checkbox right below your NRS address; but I think your NRS address is wrong.
From what I gather:
Node IP = 192.168.1.30
Signaling Server IP = 192.168.1.32; also NRS
Asterisk IP = 192.168.1.80
Correct? If so, then your signaling server is programmed w/ the wrong NRS IP. 192.168.1.32 should go in your "Primary Proxy or Redirect Server" IP address field. Then re-transmit the node.
Matthew - Technical Support Engineer
From what I gather:
Node IP = 192.168.1.30
Signaling Server IP = 192.168.1.32; also NRS
Asterisk IP = 192.168.1.80
Correct? If so, then your signaling server is programmed w/ the wrong NRS IP. 192.168.1.32 should go in your "Primary Proxy or Redirect Server" IP address field. Then re-transmit the node.
Matthew - Technical Support Engineer
- Thread starter
- #37
Yes you are correct, I changed it to .32 and transferred. Still getting the errors:
16/09/2010 16:43:09 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
16/09/2010 16:43:20 LOG0003 GKNPM: gkNpmLightRRQ: Non-Ras Endpoint tmetss 192.168.1.30 is trying to register
16/09/2010 16:43:20 LOG0004 GKNPM: ITG4065 Endpoint tmetss 192.168.1.30 status: Unregistered (93)
16/09/2010 16:43:20 LOG0003 NPM: cmEvRASReject: GK 192.168.1.32 Registration rejected
16/09/2010 16:43:24 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
16/09/2010 16:43:30 LOG0004 GKNPM: ITG4065 Endpoint tmetss 192.168.1.30 status: Registered (93)
16/09/2010 16:43:30 LOG0006 NPM: cmEvRASConfirm: GK 192.168.1.32, Registration OK, rasSession(0x2d113b9c)
16/09/2010 16:43:09 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
16/09/2010 16:43:20 LOG0003 GKNPM: gkNpmLightRRQ: Non-Ras Endpoint tmetss 192.168.1.30 is trying to register
16/09/2010 16:43:20 LOG0004 GKNPM: ITG4065 Endpoint tmetss 192.168.1.30 status: Unregistered (93)
16/09/2010 16:43:20 LOG0003 NPM: cmEvRASReject: GK 192.168.1.32 Registration rejected
16/09/2010 16:43:24 LOG0003 SIPNPM: CSTAAmlHandler_ItgMsgPBXAmlLinkRes: pbxAmlLinkInit( Unknown 0x1 )
16/09/2010 16:43:30 LOG0004 GKNPM: ITG4065 Endpoint tmetss 192.168.1.30 status: Registered (93)
16/09/2010 16:43:30 LOG0006 NPM: cmEvRASConfirm: GK 192.168.1.32, Registration OK, rasSession(0x2d113b9c)
NortelGuy1979
Programmer
Looks like it registered now; see the last two lines. Can you screenshot that again, and also the endpoint config in NRS? Making progress step by step hehe.
NOW, back to your RLI / DMI etc. We know that CDP call type will at least go to the NRS now. So make your CDP code a DSC, and on the DMI I'd do call type NCHG (so it stays a CDP code). In NRS make it a CDP routing entry. Then try and place the call with those SIP traces on and see what we get.
I un-fubar'd our lab but I have no Asterisk system to test against.
Matthew - Technical Support Engineer
NOW, back to your RLI / DMI etc. We know that CDP call type will at least go to the NRS now. So make your CDP code a DSC, and on the DMI I'd do call type NCHG (so it stays a CDP code). In NRS make it a CDP routing entry. Then try and place the call with those SIP traces on and see what we get.
I un-fubar'd our lab but I have no Asterisk system to test against.
Matthew - Technical Support Engineer
- Thread starter
- #39
Na, it keeps scrolling through those lines, I just took it out of the gateway endpoint and re-added it.
After the commit and cutover:
Endpoint config:
Ld 87
REQ prt
CUST 0
FEAT cdp
TYPE dsc
DSC 47
DSC 47
FLEN 4
DSP LSC
RLI 3
NPA
NXX
>ld 86
REQ prt
CUST 0
FEAT rlb
RLI 3
RLI 3
ENTR 0
LTER NO
ROUT 6
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
SCNV NO
CNV NO
EXP NO
FRL 0
DMI 2
ISDM 0
FCI 0
FSNI 0
DORG NO
SBOC NRR
CBQ NO
ISET 0
NALT 5
MFRL 0
OVLL 0
REQ prt
CUST 0
FEAT dgt
DMI 2
DMI 2
DEL 0
ISPN NO
CTYP NCHG
When making the CDP Routing entry in the NRS, is it for the Asterisk endpoint or the tmetss endpoint? . . I think I got everything else you asked!
After the commit and cutover:
Endpoint config:
Ld 87
REQ prt
CUST 0
FEAT cdp
TYPE dsc
DSC 47
DSC 47
FLEN 4
DSP LSC
RLI 3
NPA
NXX
>ld 86
REQ prt
CUST 0
FEAT rlb
RLI 3
RLI 3
ENTR 0
LTER NO
ROUT 6
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
SCNV NO
CNV NO
EXP NO
FRL 0
DMI 2
ISDM 0
FCI 0
FSNI 0
DORG NO
SBOC NRR
CBQ NO
ISET 0
NALT 5
MFRL 0
OVLL 0
REQ prt
CUST 0
FEAT dgt
DMI 2
DMI 2
DEL 0
ISPN NO
CTYP NCHG
When making the CDP Routing entry in the NRS, is it for the Asterisk endpoint or the tmetss endpoint? . . I think I got everything else you asked!
- Thread starter
- #40
Forgot the trace but without adding the CDP to NRS I don't think we are there yet, but just to be sure I tested, here it is:
oam> SIPCallTrace on
oam> SIPCallTrace: (16/09/10 17:09:53) Outgoing -- method INVITE(0) chid: 6 Far End Signaling IP: 192.168.1.32:5060 Calling: 6785 Called : 4790
SIPCallTrace: (16/09/10 17:09:53)
INVITE sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone SIP/2.0
From: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=1924d9d8-1e01a8c0-13c4-40030-48866a-4cfc5cfa-48866a
SIPCallTrace: (16/09/10 17:09:53)
To: <sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>
Call-ID: 18a5eb08-1e01a8c0-13c4-40030-48866a-7c51119c-48866a
CSeq: 1 INVITE
Via: SIP/2.0/UDP 192.168.1.30:5060;branch=z9hG4bK-48866a-1b4d0e10-300701c4
SIPCallTrace: (16/09/10 17:09:53)
Max-Forwards: 70
Supported: 100rel,x-nortel-sipvc,replaces,timer
User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31
P-Asserted-Identity: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>
SIPCallTrace: (16/09/10 17:09:53)
Privacy: none
History-Info: <sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;index=1
x-nt-corr-id: 0000001a1108391009@001bbafd28df-0ceef522
SIPCallTrace: (16/09/10 17:09:53)
Contact: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.30;transport=tcp;user=phone>
Min-SE: 0
Allow: INVITE,ACK,BYE,REGISTER,REFER,NOTIFY,CANCEL,PRACK,OPTIONS,INFO,SUBSCRIBE,UPDATE
SIPCallTrace: (16/09/10 17:09:53)
Content-Type: multipart/mixed;boundary=unique-boundary-1
Content-Length: 796
--unique-boundary-1
Content-Type: application/sdp
v=0
o=- 182985 1 IN IP4 192.168.1.30
s=-
t=0 0
m=audio 5414 RTP/AVP 0 8 18 101 111
SIPCallTrace: (16/09/10 17:09:53)
c=IN IP4 192.168.1.31
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:111 X-nt-inforeq/8000
a=ptime:20
a=sendrecv
--unique-boundary-1
SIPCallTrace: (16/09/10 17:09:53)
Content-Type: application/x-nt-mcdn-frag-hex;version=sse-5.00.31;base=x2611
Content-Disposition: signal;handling=optional
05008601
0107130081900000a200
09090f00e9a0830001000600
SIPCallTrace: (16/09/10 17:09:53)
1315070011fa0f00a10d02010102020100cc040000d34a00
1e0403008183
460e01000a0001000100010000000000
--unique-boundary-1
Content-Type: application/x-nt-epid-frag-hex;version=sse-5.00.31;base=x2611
SIPCallTrace: (16/09/10 17:09:53)
Content-Disposition: signal;handling=optional
011201
00:1b:ba:fd:29:d7
--unique-boundary-1--
SIPCallTrace: (16/09/10 17:09:53) Incoming -- response 302 Moved Temporarily chid: 6 Far End Signaling IP: 192.168.1.80:5060 Calling: 6785 Called : 4790
SIPCallTrace: (16/09/10 17:09:53)
SIP/2.0 302 Moved Temporarily
From: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=1924d9d8-1e01a8c0-13c4-40030-48866a-4cfc5cfa-48866a
SIPCallTrace: (16/09/10 17:09:53)
To: <sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=6270
Call-ID: 18a5eb08-1e01a8c0-13c4-40030-48866a-7c51119c-48866a
CSeq: 1 INVITE
SIPCallTrace: (16/09/10 17:09:53)
Via: SIP/2.0/TCP 192.168.1.30:5060;received=192.168.1.30;branch=z9hG4bK-48866a-1b4d0e10-300701c4
SIPCallTrace: (16/09/10 17:09:53)
Contact: <sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.80;transport=udp;user=phone;x-nt-redirect=redirect-server>
Content-Length: 0
SIPCallTrace: (16/09/10 17:09:53) Outgoing -- method ACK(1) chid: 6 Far End Signaling IP: 192.168.1.32:5060 Calling: 6785 Called : 4790
SIPCallTrace: (16/09/10 17:09:53)
ACK sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone SIP/2.0
From: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=1924d9d8-1e01a8c0-13c4-40030-48866a-4cfc5cfa-48866a
SIPCallTrace: (16/09/10 17:09:53)
To: <sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=6270
Call-ID: 18a5eb08-1e01a8c0-13c4-40030-48866a-7c51119c-48866a
CSeq: 1 ACK
SIPCallTrace: (16/09/10 17:09:53)
Via: SIP/2.0/TCP 192.168.1.30:5060;branch=z9hG4bK-48866a-1b4d0e10-300701c4
Max-Forwards: 70
User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31
x-nt-corr-id: 0000001a1108391009@001bbafd28df-0ceef522
SIPCallTrace: (16/09/10 17:09:53)
Contact: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.30;transport=tcp;user=phone>
Allow: INVITE,ACK,BYE,REGISTER,REFER,NOTIFY,CANCEL,PRACK,OPTIONS,INFO,SUBSCRIBE,UPDATE
Content-Length: 0
SIPCallTrace: (16/09/10 17:09:53) Outgoing -- method INVITE(0) chid: 6 Far End Signaling IP: 192.168.1.80:5060 Calling: 6785 Called : 4790
SIPCallTrace: (16/09/10 17:09:53)
INVITE sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.80;transport=udp;user=phone;x-nt-redirect=redirect-server SIP/2.0
SIPCallTrace: (16/09/10 17:09:53)
From: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=1924be58-1e01a8c0-13c4-40030-48866a-79d59956-48866a
To: <sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>
SIPCallTrace: (16/09/10 17:09:53)
Call-ID: 18a5ec98-1e01a8c0-13c4-40030-48866a-4af40038-48866a
CSeq: 1 INVITE
Via: SIP/2.0/UDP 192.168.1.30:5060;branch=z9hG4bK-48866a-1b4d0e10-411bcf0
Max-Forwards: 70
Supported: 100rel,x-nortel-sipvc,replaces,timer
SIPCallTrace: (16/09/10 17:09:53)
User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31
P-Asserted-Identity: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>
Privacy: none
SIPCallTrace: (16/09/10 17:09:53)
History-Info: <sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;index=1
x-nt-corr-id: 0000001a1108391009@001bbafd28df-0ceef522
SIPCallTrace: (16/09/10 17:09:53)
Contact: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.30;transport=udp;user=phone>
Min-SE: 0
Allow: INVITE,ACK,BYE,REGISTER,REFER,NOTIFY,CANCEL,PRACK,OPTIONS,INFO,SUBSCRIBE,UPDATE
SIPCallTrace: (16/09/10 17:09:53)
Content-Type: multipart/mixed;boundary=unique-boundary-1
Content-Length: 796
--unique-boundary-1
Content-Type: application/sdp
v=0
o=- 182985 1 IN IP4 192.168.1.30
s=-
t=0 0
m=audio 5414 RTP/AVP 0 8 18 101 111
SIPCallTrace: (16/09/10 17:09:53)
c=IN IP4 192.168.1.31
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:111 X-nt-inforeq/8000
a=ptime:20
a=sendrecv
--unique-boundary-1
SIPCallTrace: (16/09/10 17:09:53)
Content-Type: application/x-nt-mcdn-frag-hex;version=sse-5.00.31;base=x2611
Content-Disposition: signal;handling=optional
05008601
0107130081900000a200
09090f00e9a0830001000600
SIPCallTrace: (16/09/10 17:09:53)
1315070011fa0f00a10d02010102020100cc040000d34a00
1e0403008183
460e01000a0001000100010000000000
--unique-boundary-1
Content-Type: application/x-nt-epid-frag-hex;version=sse-5.00.31;base=x2611
SIPCallTrace: (16/09/10 17:09:53)
Content-Disposition: signal;handling=optional
011201
00:1b:ba:fd:29:d7
--unique-boundary-1--
SIPCallTrace: (16/09/10 17:09:53) Incoming -- response 401 Unauthorized chid: 6 Far End Signaling IP: 192.168.1.80:5060 Calling: 6785 Called : 4790
SIPCallTrace: (16/09/10 17:09:53)
SIP/2.0 401 Unauthorized
From: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=1924be58-1e01a8c0-13c4-40030-48866a-79d59956-48866a
SIPCallTrace: (16/09/10 17:09:53)
To: <sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=as5bc06ce1
Call-ID: 18a5ec98-1e01a8c0-13c4-40030-48866a-4af40038-48866a
CSeq: 1 INVITE
SIPCallTrace: (16/09/10 17:09:53)
Via: SIP/2.0/UDP 192.168.1.30:5060;received=192.168.1.30;branch=z9hG4bK-48866a-1b4d0e10-411bcf0
Server: Asterisk PBX 1.6.2.11
Supported: replaces,timer
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,SUBSCRIBE,NOTIFY,INFO
SIPCallTrace: (16/09/10 17:09:53)
Digest realm="asterisk",nonce="15748283",algorithm=MD5
Content-Length: 0
SIPCallTrace: (16/09/10 17:09:53) Outgoing -- method ACK(1) chid: 6 Far End Signaling IP: 192.168.1.80:5060 Calling: 6785 Called : 4790
SIPCallTrace: (16/09/10 17:09:53)
ACK sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.80;transport=udp;user=phone;x-nt-redirect=redirect-server SIP/2.0
SIPCallTrace: (16/09/10 17:09:53)
From: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=1924be58-1e01a8c0-13c4-40030-48866a-79d59956-48866a
To: <sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=as5bc06ce1
SIPCallTrace: (16/09/10 17:09:53)
Call-ID: 18a5ec98-1e01a8c0-13c4-40030-48866a-4af40038-48866a
CSeq: 1 ACK
Via: SIP/2.0/UDP 192.168.1.30:5060;branch=z9hG4bK-48866a-1b4d0e10-411bcf0
Max-Forwards: 70
SIPCallTrace: (16/09/10 17:09:53)
User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31
x-nt-corr-id: 0000001a1108391009@001bbafd28df-0ceef522
SIPCallTrace: (16/09/10 17:09:53)
Contact: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.30;transport=udp;user=phone>
Allow: INVITE,ACK,BYE,REGISTER,REFER,NOTIFY,CANCEL,PRACK,OPTIONS,INFO,SUBSCRIBE,UPDATE
Content-Length: 0
SIPCallTrace: (16/09/10 17:09:53) Outgoing -- method INVITE(0) chid: 6 Far End Signaling IP: 192.168.1.80:5060 Calling: 6785 Called : 4790
SIPCallTrace: (16/09/10 17:09:53)
INVITE sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.80;transport=udp;user=phone;x-nt-redirect=redirect-server SIP/2.0
SIPCallTrace: (16/09/10 17:09:53)
From: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=1924be58-1e01a8c0-13c4-40030-48866a-79d59956-48866a
To: <sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>
SIPCallTrace: (16/09/10 17:09:53)
Call-ID: 18a5ec98-1e01a8c0-13c4-40030-48866a-4af40038-48866a
CSeq: 2 INVITE
Via: SIP/2.0/UDP 192.168.1.30:5060;branch=z9hG4bK-48866a-1b4d0e10-78c1a916
Max-Forwards: 70
Supported: 100rel,x-nortel-sipvc,replaces,timer
SIPCallTrace: (16/09/10 17:09:53)
User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31
P-Asserted-Identity: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>
Privacy: none
SIPCallTrace: (16/09/10 17:09:53)
History-Info: <sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;index=1
x-nt-corr-id: 0000001a1108391009@001bbafd28df-0ceef522
SIPCallTrace: (16/09/10 17:09:53)
Contact: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.30;transport=udp;user=phone>
SIPCallTrace: (16/09/10 17:09:53)
SIPCallTrace: (16/09/10 17:09:53)
67837b465f5b15652f0c3a4e9a3",algorithm=MD5
Min-SE: 0
Allow: INVITE,ACK,BYE,REGISTER,REFER,NOTIFY,CANCEL,PRACK,OPTIONS,INFO,SUBSCRIBE,UPDATE
Content-Type: multipart/mixed;boundary=unique-boundary-1
Content-Length: 796
SIPCallTrace: (16/09/10 17:09:53)
SIPCallTrace: (16/09/10 17:09:53)
--unique-boundary-1
Content-Type: application/sdp
v=0
o=- 182985 1 IN IP4 192.168.1.30
s=-
t=0 0
m=audio 5414 RTP/AVP 0 8 18 101 111
c=IN IP4 192.168.1.31
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
SIPCallTrace: (16/09/10 17:09:53)
SIPCallTrace: (16/09/10 17:09:53)
a=fmtp:101 0-15
a=rtpmap:111 X-nt-inforeq/8000
a=ptime:20
a=sendrecv
--unique-boundary-1
Content-Type: application/x-nt-mcdn-frag-hex;version=sse-5.00.31;base=x2611
Content-Disposition: signal;handling=optional
SIPCallTrace: (16/09/10 17:09:53)
SIPCallTrace: (16/09/10 17:09:53)
05008601
0107130081900000a200
09090f00e9a0830001000600
1315070011fa0f00a10d02010102020100cc040000d34a00
1e0403008183
460e01000a0001000100010000000000
--unique-boundary-1
SIPCallTrace: (16/09/10 17:09:53)
SIPCallTrace: (16/09/10 17:09:53)
Content-Type: application/x-nt-epid-frag-hex;version=sse-5.00.31;base=x2611
Content-Disposition: signal;handling=optional
011201
00:1b:ba:fd:29:d7
--unique-boundary-1--
SIPCallTrace: (16/09/10 17:09:53) Incoming -- response 403 Forbidden chid: 6 Far End Signaling IP: 192.168.1.80:5060 Calling: 6785 Called : 4790
SIPCallTrace: (16/09/10 17:09:53)
SIP/2.0 403 Forbidden
From: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=1924be58-1e01a8c0-13c4-40030-48866a-79d59956-48866a
SIPCallTrace: (16/09/10 17:09:53)
To: <sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=as5bc06ce1
Call-ID: 18a5ec98-1e01a8c0-13c4-40030-48866a-4af40038-48866a
CSeq: 2 INVITE
SIPCallTrace: (16/09/10 17:09:53)
Via: SIP/2.0/UDP 192.168.1.30:5060;received=192.168.1.30;branch=z9hG4bK-48866a-1b4d0e10-78c1a916
Server: Asterisk PBX 1.6.2.11
Supported: replaces,timer
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,SUBSCRIBE,NOTIFY,INFO
SIPCallTrace: (16/09/10 17:09:53)
Content-Length: 0
SIPCallTrace: (16/09/10 17:09:53) Outgoing -- method ACK(1) chid: 6 Far End Signaling IP: 192.168.1.80:5060 Calling: 6785 Called : 4790
SIPCallTrace: (16/09/10 17:09:53)
ACK sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.80;transport=udp;user=phone;x-nt-redirect=redirect-server SIP/2.0
SIPCallTrace: (16/09/10 17:09:53)
From: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=1924be58-1e01a8c0-13c4-40030-48866a-79d59956-48866a
To: <sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=as5bc06ce1
SIPCallTrace: (16/09/10 17:09:53)
Call-ID: 18a5ec98-1e01a8c0-13c4-40030-48866a-4af40038-48866a
CSeq: 2 ACK
Via: SIP/2.0/UDP 192.168.1.30:5060;branch=z9hG4bK-48866a-1b4d0e10-78c1a916
Max-Forwards: 70
SIPCallTrace: (16/09/10 17:09:53)
User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31
x-nt-corr-id: 0000001a1108391009@001bbafd28df-0ceef522
SIPCallTrace: (16/09/10 17:09:53)
Contact: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.30;transport=udp;user=phone>
Allow: INVITE,ACK,BYE,REGISTER,REFER,NOTIFY,CANCEL,PRACK,OPTIONS,INFO,SUBSCRIBE,UPDATE
Content-Length: 0
oam> SIPCallTrace on
oam> SIPCallTrace: (16/09/10 17:09:53) Outgoing -- method INVITE(0) chid: 6 Far End Signaling IP: 192.168.1.32:5060 Calling: 6785 Called : 4790
SIPCallTrace: (16/09/10 17:09:53)
INVITE sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone SIP/2.0
From: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=1924d9d8-1e01a8c0-13c4-40030-48866a-4cfc5cfa-48866a
SIPCallTrace: (16/09/10 17:09:53)
To: <sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>
Call-ID: 18a5eb08-1e01a8c0-13c4-40030-48866a-7c51119c-48866a
CSeq: 1 INVITE
Via: SIP/2.0/UDP 192.168.1.30:5060;branch=z9hG4bK-48866a-1b4d0e10-300701c4
SIPCallTrace: (16/09/10 17:09:53)
Max-Forwards: 70
Supported: 100rel,x-nortel-sipvc,replaces,timer
User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31
P-Asserted-Identity: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>
SIPCallTrace: (16/09/10 17:09:53)
Privacy: none
History-Info: <sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;index=1
x-nt-corr-id: 0000001a1108391009@001bbafd28df-0ceef522
SIPCallTrace: (16/09/10 17:09:53)
Contact: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.30;transport=tcp;user=phone>
Min-SE: 0
Allow: INVITE,ACK,BYE,REGISTER,REFER,NOTIFY,CANCEL,PRACK,OPTIONS,INFO,SUBSCRIBE,UPDATE
SIPCallTrace: (16/09/10 17:09:53)
Content-Type: multipart/mixed;boundary=unique-boundary-1
Content-Length: 796
--unique-boundary-1
Content-Type: application/sdp
v=0
o=- 182985 1 IN IP4 192.168.1.30
s=-
t=0 0
m=audio 5414 RTP/AVP 0 8 18 101 111
SIPCallTrace: (16/09/10 17:09:53)
c=IN IP4 192.168.1.31
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:111 X-nt-inforeq/8000
a=ptime:20
a=sendrecv
--unique-boundary-1
SIPCallTrace: (16/09/10 17:09:53)
Content-Type: application/x-nt-mcdn-frag-hex;version=sse-5.00.31;base=x2611
Content-Disposition: signal;handling=optional
05008601
0107130081900000a200
09090f00e9a0830001000600
SIPCallTrace: (16/09/10 17:09:53)
1315070011fa0f00a10d02010102020100cc040000d34a00
1e0403008183
460e01000a0001000100010000000000
--unique-boundary-1
Content-Type: application/x-nt-epid-frag-hex;version=sse-5.00.31;base=x2611
SIPCallTrace: (16/09/10 17:09:53)
Content-Disposition: signal;handling=optional
011201
00:1b:ba:fd:29:d7
--unique-boundary-1--
SIPCallTrace: (16/09/10 17:09:53) Incoming -- response 302 Moved Temporarily chid: 6 Far End Signaling IP: 192.168.1.80:5060 Calling: 6785 Called : 4790
SIPCallTrace: (16/09/10 17:09:53)
SIP/2.0 302 Moved Temporarily
From: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=1924d9d8-1e01a8c0-13c4-40030-48866a-4cfc5cfa-48866a
SIPCallTrace: (16/09/10 17:09:53)
To: <sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=6270
Call-ID: 18a5eb08-1e01a8c0-13c4-40030-48866a-7c51119c-48866a
CSeq: 1 INVITE
SIPCallTrace: (16/09/10 17:09:53)
Via: SIP/2.0/TCP 192.168.1.30:5060;received=192.168.1.30;branch=z9hG4bK-48866a-1b4d0e10-300701c4
SIPCallTrace: (16/09/10 17:09:53)
Contact: <sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.80;transport=udp;user=phone;x-nt-redirect=redirect-server>
Content-Length: 0
SIPCallTrace: (16/09/10 17:09:53) Outgoing -- method ACK(1) chid: 6 Far End Signaling IP: 192.168.1.32:5060 Calling: 6785 Called : 4790
SIPCallTrace: (16/09/10 17:09:53)
ACK sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone SIP/2.0
From: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=1924d9d8-1e01a8c0-13c4-40030-48866a-4cfc5cfa-48866a
SIPCallTrace: (16/09/10 17:09:53)
To: <sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=6270
Call-ID: 18a5eb08-1e01a8c0-13c4-40030-48866a-7c51119c-48866a
CSeq: 1 ACK
SIPCallTrace: (16/09/10 17:09:53)
Via: SIP/2.0/TCP 192.168.1.30:5060;branch=z9hG4bK-48866a-1b4d0e10-300701c4
Max-Forwards: 70
User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31
x-nt-corr-id: 0000001a1108391009@001bbafd28df-0ceef522
SIPCallTrace: (16/09/10 17:09:53)
Contact: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.30;transport=tcp;user=phone>
Allow: INVITE,ACK,BYE,REGISTER,REFER,NOTIFY,CANCEL,PRACK,OPTIONS,INFO,SUBSCRIBE,UPDATE
Content-Length: 0
SIPCallTrace: (16/09/10 17:09:53) Outgoing -- method INVITE(0) chid: 6 Far End Signaling IP: 192.168.1.80:5060 Calling: 6785 Called : 4790
SIPCallTrace: (16/09/10 17:09:53)
INVITE sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.80;transport=udp;user=phone;x-nt-redirect=redirect-server SIP/2.0
SIPCallTrace: (16/09/10 17:09:53)
From: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=1924be58-1e01a8c0-13c4-40030-48866a-79d59956-48866a
To: <sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>
SIPCallTrace: (16/09/10 17:09:53)
Call-ID: 18a5ec98-1e01a8c0-13c4-40030-48866a-4af40038-48866a
CSeq: 1 INVITE
Via: SIP/2.0/UDP 192.168.1.30:5060;branch=z9hG4bK-48866a-1b4d0e10-411bcf0
Max-Forwards: 70
Supported: 100rel,x-nortel-sipvc,replaces,timer
SIPCallTrace: (16/09/10 17:09:53)
User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31
P-Asserted-Identity: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>
Privacy: none
SIPCallTrace: (16/09/10 17:09:53)
History-Info: <sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;index=1
x-nt-corr-id: 0000001a1108391009@001bbafd28df-0ceef522
SIPCallTrace: (16/09/10 17:09:53)
Contact: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.30;transport=udp;user=phone>
Min-SE: 0
Allow: INVITE,ACK,BYE,REGISTER,REFER,NOTIFY,CANCEL,PRACK,OPTIONS,INFO,SUBSCRIBE,UPDATE
SIPCallTrace: (16/09/10 17:09:53)
Content-Type: multipart/mixed;boundary=unique-boundary-1
Content-Length: 796
--unique-boundary-1
Content-Type: application/sdp
v=0
o=- 182985 1 IN IP4 192.168.1.30
s=-
t=0 0
m=audio 5414 RTP/AVP 0 8 18 101 111
SIPCallTrace: (16/09/10 17:09:53)
c=IN IP4 192.168.1.31
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:111 X-nt-inforeq/8000
a=ptime:20
a=sendrecv
--unique-boundary-1
SIPCallTrace: (16/09/10 17:09:53)
Content-Type: application/x-nt-mcdn-frag-hex;version=sse-5.00.31;base=x2611
Content-Disposition: signal;handling=optional
05008601
0107130081900000a200
09090f00e9a0830001000600
SIPCallTrace: (16/09/10 17:09:53)
1315070011fa0f00a10d02010102020100cc040000d34a00
1e0403008183
460e01000a0001000100010000000000
--unique-boundary-1
Content-Type: application/x-nt-epid-frag-hex;version=sse-5.00.31;base=x2611
SIPCallTrace: (16/09/10 17:09:53)
Content-Disposition: signal;handling=optional
011201
00:1b:ba:fd:29:d7
--unique-boundary-1--
SIPCallTrace: (16/09/10 17:09:53) Incoming -- response 401 Unauthorized chid: 6 Far End Signaling IP: 192.168.1.80:5060 Calling: 6785 Called : 4790
SIPCallTrace: (16/09/10 17:09:53)
SIP/2.0 401 Unauthorized
From: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=1924be58-1e01a8c0-13c4-40030-48866a-79d59956-48866a
SIPCallTrace: (16/09/10 17:09:53)
To: <sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=as5bc06ce1
Call-ID: 18a5ec98-1e01a8c0-13c4-40030-48866a-4af40038-48866a
CSeq: 1 INVITE
SIPCallTrace: (16/09/10 17:09:53)
Via: SIP/2.0/UDP 192.168.1.30:5060;received=192.168.1.30;branch=z9hG4bK-48866a-1b4d0e10-411bcf0
Server: Asterisk PBX 1.6.2.11
Supported: replaces,timer
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,SUBSCRIBE,NOTIFY,INFO
SIPCallTrace: (16/09/10 17:09:53)
Digest realm="asterisk",nonce="15748283",algorithm=MD5
Content-Length: 0
SIPCallTrace: (16/09/10 17:09:53) Outgoing -- method ACK(1) chid: 6 Far End Signaling IP: 192.168.1.80:5060 Calling: 6785 Called : 4790
SIPCallTrace: (16/09/10 17:09:53)
ACK sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.80;transport=udp;user=phone;x-nt-redirect=redirect-server SIP/2.0
SIPCallTrace: (16/09/10 17:09:53)
From: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=1924be58-1e01a8c0-13c4-40030-48866a-79d59956-48866a
To: <sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=as5bc06ce1
SIPCallTrace: (16/09/10 17:09:53)
Call-ID: 18a5ec98-1e01a8c0-13c4-40030-48866a-4af40038-48866a
CSeq: 1 ACK
Via: SIP/2.0/UDP 192.168.1.30:5060;branch=z9hG4bK-48866a-1b4d0e10-411bcf0
Max-Forwards: 70
SIPCallTrace: (16/09/10 17:09:53)
User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31
x-nt-corr-id: 0000001a1108391009@001bbafd28df-0ceef522
SIPCallTrace: (16/09/10 17:09:53)
Contact: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.30;transport=udp;user=phone>
Allow: INVITE,ACK,BYE,REGISTER,REFER,NOTIFY,CANCEL,PRACK,OPTIONS,INFO,SUBSCRIBE,UPDATE
Content-Length: 0
SIPCallTrace: (16/09/10 17:09:53) Outgoing -- method INVITE(0) chid: 6 Far End Signaling IP: 192.168.1.80:5060 Calling: 6785 Called : 4790
SIPCallTrace: (16/09/10 17:09:53)
INVITE sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.80;transport=udp;user=phone;x-nt-redirect=redirect-server SIP/2.0
SIPCallTrace: (16/09/10 17:09:53)
From: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=1924be58-1e01a8c0-13c4-40030-48866a-79d59956-48866a
To: <sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>
SIPCallTrace: (16/09/10 17:09:53)
Call-ID: 18a5ec98-1e01a8c0-13c4-40030-48866a-4af40038-48866a
CSeq: 2 INVITE
Via: SIP/2.0/UDP 192.168.1.30:5060;branch=z9hG4bK-48866a-1b4d0e10-78c1a916
Max-Forwards: 70
Supported: 100rel,x-nortel-sipvc,replaces,timer
SIPCallTrace: (16/09/10 17:09:53)
User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31
P-Asserted-Identity: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>
Privacy: none
SIPCallTrace: (16/09/10 17:09:53)
History-Info: <sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;index=1
x-nt-corr-id: 0000001a1108391009@001bbafd28df-0ceef522
SIPCallTrace: (16/09/10 17:09:53)
Contact: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.30;transport=udp;user=phone>
SIPCallTrace: (16/09/10 17:09:53)
SIPCallTrace: (16/09/10 17:09:53)
67837b465f5b15652f0c3a4e9a3",algorithm=MD5
Min-SE: 0
Allow: INVITE,ACK,BYE,REGISTER,REFER,NOTIFY,CANCEL,PRACK,OPTIONS,INFO,SUBSCRIBE,UPDATE
Content-Type: multipart/mixed;boundary=unique-boundary-1
Content-Length: 796
SIPCallTrace: (16/09/10 17:09:53)
SIPCallTrace: (16/09/10 17:09:53)
--unique-boundary-1
Content-Type: application/sdp
v=0
o=- 182985 1 IN IP4 192.168.1.30
s=-
t=0 0
m=audio 5414 RTP/AVP 0 8 18 101 111
c=IN IP4 192.168.1.31
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
SIPCallTrace: (16/09/10 17:09:53)
SIPCallTrace: (16/09/10 17:09:53)
a=fmtp:101 0-15
a=rtpmap:111 X-nt-inforeq/8000
a=ptime:20
a=sendrecv
--unique-boundary-1
Content-Type: application/x-nt-mcdn-frag-hex;version=sse-5.00.31;base=x2611
Content-Disposition: signal;handling=optional
SIPCallTrace: (16/09/10 17:09:53)
SIPCallTrace: (16/09/10 17:09:53)
05008601
0107130081900000a200
09090f00e9a0830001000600
1315070011fa0f00a10d02010102020100cc040000d34a00
1e0403008183
460e01000a0001000100010000000000
--unique-boundary-1
SIPCallTrace: (16/09/10 17:09:53)
SIPCallTrace: (16/09/10 17:09:53)
Content-Type: application/x-nt-epid-frag-hex;version=sse-5.00.31;base=x2611
Content-Disposition: signal;handling=optional
011201
00:1b:ba:fd:29:d7
--unique-boundary-1--
SIPCallTrace: (16/09/10 17:09:53) Incoming -- response 403 Forbidden chid: 6 Far End Signaling IP: 192.168.1.80:5060 Calling: 6785 Called : 4790
SIPCallTrace: (16/09/10 17:09:53)
SIP/2.0 403 Forbidden
From: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=1924be58-1e01a8c0-13c4-40030-48866a-79d59956-48866a
SIPCallTrace: (16/09/10 17:09:53)
To: <sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=as5bc06ce1
Call-ID: 18a5ec98-1e01a8c0-13c4-40030-48866a-4af40038-48866a
CSeq: 2 INVITE
SIPCallTrace: (16/09/10 17:09:53)
Via: SIP/2.0/UDP 192.168.1.30:5060;received=192.168.1.30;branch=z9hG4bK-48866a-1b4d0e10-78c1a916
Server: Asterisk PBX 1.6.2.11
Supported: replaces,timer
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,SUBSCRIBE,NOTIFY,INFO
SIPCallTrace: (16/09/10 17:09:53)
Content-Length: 0
SIPCallTrace: (16/09/10 17:09:53) Outgoing -- method ACK(1) chid: 6 Far End Signaling IP: 192.168.1.80:5060 Calling: 6785 Called : 4790
SIPCallTrace: (16/09/10 17:09:53)
ACK sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.80;transport=udp;user=phone;x-nt-redirect=redirect-server SIP/2.0
SIPCallTrace: (16/09/10 17:09:53)
From: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=1924be58-1e01a8c0-13c4-40030-48866a-79d59956-48866a
To: <sip:4790;phone-context=udp.cdp@tmetss.corp.tmetrics.com;user=phone>;tag=as5bc06ce1
SIPCallTrace: (16/09/10 17:09:53)
Call-ID: 18a5ec98-1e01a8c0-13c4-40030-48866a-4af40038-48866a
CSeq: 2 ACK
Via: SIP/2.0/UDP 192.168.1.30:5060;branch=z9hG4bK-48866a-1b4d0e10-78c1a916
Max-Forwards: 70
SIPCallTrace: (16/09/10 17:09:53)
User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31
x-nt-corr-id: 0000001a1108391009@001bbafd28df-0ceef522
SIPCallTrace: (16/09/10 17:09:53)
Contact: <sip:6785;phone-context=udp.cdp@tmetss.corp.tmetrics.com:5060;maddr=192.168.1.30;transport=udp;user=phone>
Allow: INVITE,ACK,BYE,REGISTER,REFER,NOTIFY,CANCEL,PRACK,OPTIONS,INFO,SUBSCRIBE,UPDATE
Content-Length: 0
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question