Hallöchen,
hier ein Trace von einem Faxempfang. Macht der Lancom hier ein Fallback nach G.711 oder nicht? Meiner Meinung ja. Wie sehen das die Experten?:-)
16.08.2007 12:51:21 @<<<<<<<<<<@
[SIP-Packet] 2007/08/16 12:51:21,600
Receiving datagram with length 1301 from 212.117.200.148:5060 to 87.167.214.25:32931
INVITE sip:491801xxxxxxxxxxxx@87.167.214.25:32931 SIP/2.0
Record-Route: <sip:212.117.200.148;ftag=988489a24ef1d69c20ed4e4745f604fc;lr>
Via: SIP/2.0/UDP 212.117.200.148;branch=z9hG4bKebb1.71cce6e3395508b17201c0962c1af3cf.0
Via: SIP/2.0/UDP 212.117.200.148:5061;branch=z9hG4bKc982b0be10102a03c3413a8c62cf71b9;rport=5061
Max-Forwards: 16
From: 49613132710899 <sip:0613132710899@212.117.200.148>;tag=988489a24ef1d69c20ed4e4745f604fc
To: <sip:491801xxxxxxxxxxxx@212.117.200.148>
Call-ID: 50e5864b240078713271e6c071f69d3f@80.237.199.41
CSeq: 200 INVITE
Contact: Anonymous <sip:212.117.200.148:5061>
Expires: 300
User-Agent: Sippy
cisco-GUID: 1528060119-1273369052-2602500111-526871165
h323-conf-id: 1528060119-1273369052-2602500111-526871165
Content-Length: 501
Content-Type: application/sdp
v=0
o=Sippy 143126092 0 IN IP4 212.117.200.148
s=session
t=0 0
m=audio 44412 RTP/AVP 8 0 97 3 111 18 4 101
c=IN IP4 212.117.200.148
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:97 iLBC/8000
a=rtpmap:3 GSM/8000
a=rtpmap:111 G726-32/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:4 G723/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
m=video 44414 RTP/AVP 31 34
c=IN IP4 212.117.200.148
a=rtpmap:31 H261/90000
a=rtpmap:34 H263/900
16.08.2007 12:51:21 @<<<<<<<<<<@00
[SIP-Packet] 2007/08/16 12:51:21,610
Sending datagram with length 685 from 87.167.214.25:32931 to 212.117.200.148:5060
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 212.117.200.148;branch=z9hG4bKebb1.71cce6e3395508b17201c0962c1af3cf.0
Via: SIP/2.0/UDP 212.117.200.148:5061;branch=z9hG4bKc982b0be10102a03c3413a8c62cf71b9;rport=5061
Record-Route: <sip:212.117.200.148:5060;ftag=988489a24ef1d69c20ed4e4745f604fc;lr>
From: "49613132710899 "<sip:0613132710899@212.117.200.148>;tag=988489a24ef1d69c20ed4e4745f604fc
To: <sip:491801xxxxxxxxxxxx@212.117.200.148>;tag=-1816924010--2002429040
Call-ID: 50e5864b240078713271e6c071f69d3f@80.237.199.41
CSeq: 200 INVITE
Expires: 300
Max-Forwards: 70
User-Agent: Sippy
Server: Mops
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS
Content-Length: 0
[SIP-Packet] 2007/08/16 12:51:21,620
Sending datagram with length 760 from 87.167.214.25:32931 to 212.117.200.148:5060
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 212.117.200.148;branch=z9hG4bKebb1.71cce6e3395508b17201c0962c1af3cf.0
Via: SIP/2.0/UDP 212.117.200.148:5061;branch=z9hG4bKc982b0be10102a03c3413a8c62cf71b9;rport=5061
Record-Route: <sip:212.117.200.148:5060;ftag=988489a24ef1d69c20ed4e4745f604fc;lr>
From: "49613132710899 "<sip:0613132710899@212.117.200.148>;tag=988489a24ef1d69c20ed4e4745f604fc
To: "491801xxxxxxxxxxxx"<sip:491801xxxxxxxxxxxx@212.117.200.148>;tag=-1816924010--2002429040
Call-ID: 50e5864b240078
16.08.2007 12:51:21 @<<<<<<<<<<@713271e6c071f69d3f@80.237.199.41
CSeq: 200 INVITE
Max-Forwards: 70
User-Agent: LANCOM 1823 VoIP (Annex B) / 7.20.0065 / 11.08.2007 (SerialNo=059900600127)
Server: Mops
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS
Content-Length: 0
16.08.2007 12:51:28 @<<<<<<<<<<@
[SIP-Packet] 2007/08/16 12:51:28,270
Sending datagram with length 977 from 87.167.214.25:32931 to 212.117.200.148:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 212.117.200.148;branch=z9hG4bKebb1.71cce6e3395508b17201c0962c1af3cf.0
Via: SIP/2.0/UDP 212.117.200.148:5061;branch=z9hG4bKc982b0be10102a03c3413a8c62cf71b9;rport=5061
Record-Route: <sip:212.117.200.148:5060;ftag=988489a24ef1d69c20ed4e4745f604fc;lr>
From: "49613132710899 "<sip:0613132710899@212.117.200.148>;tag=988489a24ef1d69c20ed4e4745f604fc
To: "491801xxxxxxxxxxxx"<sip:491801xxxxxxxxxxxx@212.117.200.148>;tag=-1816924010--2002429040
Call-ID: 50e5864b240078713271e6c071f69d3f@80.237.199.41
CSeq: 200 INVITE
Max-Forwards: 70
User-Agent: LANCOM 1823 VoIP (Annex B) / 7.20.0065 / 11.08.2007 (SerialNo=059900600127)
Server: Mops
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS
Contact: <sip:491801xxxxxxxxxxxx@87.167.214.25:32931>
Content-Type: application/sdp
Content-Length: 136
v=0
o=- 3371316959 3371316959 IN IP4 87.167.214.25
s=-
c=IN IP4 87.167.214.25
t=0 0
m=audio 37280 RTP/AVP 8
a=rtpmap:8 PCMA/8000
16.08.2007 12:51:28 @<<<<<<<<<<@
[SIP-Packet] 2007/08/16 12:51:28,320
Receiving datagram with length 531 from 212.117.200.148:5060 to 87.167.214.25:32931
ACK sip:491801xxxxxxxxxxxx@87.167.214.25:32931 SIP/2.0
Via: SIP/2.0/UDP 212.117.200.148;branch=z9hG4bKebb1.7a093c46da138e588035a0cbd5783fcc.0
Via: SIP/2.0/UDP 212.117.200.148:5061;rport=5061;branch=z9hG4bK0d9c170d89476b95d5e1738effb429fc
Max-Forwards: 16
From: 49613132710899 <sip:0613132710899@212.117.200.148>;tag=988489a24ef1d69c20ed4e4745f604fc
To: <sip:491801xxxxxxxxxxxx@212.117.200.148>;tag=-1816924010--2002429040
Call-ID: 50e5864b240078713271e6c071f69d3f@80.237.199.41
CSeq: 200 ACK
Expires: 300
User-Agent: Sippy
16.08.2007 12:51:32 @<<<<<<<<<<@
[SIP-Packet] 2007/08/16 12:51:32,190
Sending datagram with length 1027 from 87.167.214.25:32931 to 212.117.200.148:5060
INVITE sip:0613132710899@212.117.200.148 SIP/2.0
Via: SIP/2.0/UDP 87.167.214.25:32931;branch=z9hG4bK-88ccecff-44c7c8aa
Route: <SIP:212.117.200.148:5060;ftag=988489a24ef1d69c20ed4e4745f604fc;lr>
From: "491801xxxxxxxxxxxx"<sip:491801xxxxxxxxxxxx@212.117.200.148>;tag=-1816924010--2002429040
To: "49613132710899 "<sip:0613132710899@212.117.200.148>;tag=988489a24ef1d69c20ed4e4745f604fc
Call-ID: 50e5864b240078713271e6c071f69d3f@80.237.199.41
CSeq: 201 INVITE
Max-Forwards: 70
User-Agent: LANCOM 1823 VoIP (Annex B) / 7.20.0065 / 11.08.2007 (SerialNo=059900600127)
Server: Mops
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS
Contact: <sip:0613132710899@87.167.214.25:32931>
Content-Type: application/sdp
Content-Length: 276
v=0
o=- 2972897649 2972897649 IN IP4 87.167.214.25
s=-
c=IN IP4 87.167.214.25
t=0 0
m=image 37280 udptl t38
a=T38FaxVersion:0
a=T38MaxBitRate:14400
a=T38FaxRateManagement:transferredTCF
a=T38FaxMaxBuffer:1024
a=T38FaxMaxDatagram:122
a=T38FaxUdpEC:t38UDPRedundancy
16.08.2007 12:51:32 @<<<<<<<<<<@
[SIP-Packet] 2007/08/16 12:51:32,240
Receiving datagram with length 457 from 212.117.200.148:5060 to 87.167.214.25:32931
SIP/2.0 100 trying -- your call is important to us
Via: SIP/2.0/UDP 87.167.214.25:32931;branch=z9hG4bK-88ccecff-44c7c8aa
From: "491801xxxxxxxxxxxx"<sip:491801xxxxxxxxxxxx@212.117.200.148>;tag=-1816924010--2002429040
To: "49613132710899 "<sip:0613132710899@212.117.200.148>;tag=988489a24ef1d69c20ed4e4745f604fc
Call-ID: 50e5864b240078713271e6c071f69d3f@80.237.199.41
CSeq: 201 INVITE
Server: Sip EXpress router (0.9.6 (i386/freebsd))
Content-Length: 0
16.08.2007 12:51:32 @<<<<<<<<<<@
[SIP-Packet] 2007/08/16 12:51:32,320
Receiving datagram with length 701 from 212.117.200.148:5060 to 87.167.214.25:32931
SIP/2.0 200 OK
Via: SIP/2.0/UDP 87.167.214.25:32931;branch=z9hG4bK-88ccecff-44c7c8aa
Record-Route: <sip:212.117.200.148;ftag=-1816924010--2002429040;lr>
From: 491801xxxxxxxxxxxx <sip:491801xxxxxxxxxxxx@212.117.200.148>;tag=-1816924010--2002429040
To: "49613132710899 " <sip:0613132710899@212.117.200.148>;tag=988489a24ef1d69c20ed4e4745f604fc
Call-ID: 50e5864b240078713271e6c071f69d3f@80.237.199.41
CSeq: 201 INVITE
Server: Sippy
Contact: Anonymous <sip:212.117.200.148:5061>
Content-Length: 167
Content-Type: application/sdp
v=0
o=Sippy 143126092 1 IN IP4 212.117.200.148
s=session
t=0 0
m=audio 44412 RTP/AVP 8
c=IN IP4 212.117.200.148
a=rtpmap:8 PCMA/8000
a=silenceSupp:off - - - -
[SIP-Packet] 2007/08/16 12:51:32,320
Sending datagram with length 653 from 87.167.214.25:32931 to 212.117.200.148:5060
ACK sip:0613132710899@212.117.200.148 SIP/2.0
Via: SIP/2.0/UDP 87.167.214.25:32931;branch=z9hG4bK-03442f9d-5bc7f723
Route: <SIP:212.117.200.148:5060;ftag=-1816924010--2002429040;lr>
From: "491801xxxxxxxxxxxx"<sip:491801xxxxxxxxxxxx@212.117.200.148>;tag=-1816924010--2002429040
To: "49613132710899 "<sip:0613132710899@212.117.200.148>;tag=988489a24ef1d69c20ed4e4745f604fc
Call-ID: 50e5864b240078713271e6c071f69d3f@80.237.199.41
CSeq: 201 ACK
Max-Forwards: 70
User-Agent: LANCOM
16.08.2007 12:51:32 @<<<<<<<<<<@1823 VoIP (Annex B) / 7.20.0065 / 11.08.2007 (SerialNo=059900600127)
Server: Mops
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS
Content-Length: 0
16.08.2007 12:53:00 @<<<<<<<<<<@
[SIP-Packet] 2007/08/16 12:53:00,460
Receiving datagram with length 692 from 212.117.200.148:5060 to 87.167.214.25:32931
BYE sip:491801xxxxxxxxxxxx@87.167.214.25:32931 SIP/2.0
Via: SIP/2.0/UDP 212.117.200.148;branch=z9hG4bKfbb1.1907614afb0cba23da6ec446e7a675aa.0
Via: SIP/2.0/UDP 212.117.200.148:5061;branch=z9hG4bK66c9f3611d196c795cb3f2b5fe9b9999;rport=5061
Max-Forwards: 16
From: 49613132710899 <sip:0613132710899@212.117.200.148>;tag=988489a24ef1d69c20ed4e4745f604fc
To: <sip:491801xxxxxxxxxxxx@212.117.200.148>;tag=-1816924010--2002429040
Call-ID: 50e5864b240078713271e6c071f69d3f@80.237.199.41
CSeq: 201 BYE
Contact: Anonymous <sip:212.117.200.148:5061>
Expires: 300
User-Agent: Sippy
cisco-GUID: 1528060119-1273369052-2602500111-526871165
h323-conf-id: 1528060119-1273369052-2602500111-526871165
[SIP-Packet] 2007/08/16 12:53:00,460
Sending datagram with length 595 from 87.167.214.25:32931 to 212.117.200.148:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 212.117.200.148;branch=z9hG4bKfbb1.1907614afb0cba23da6ec446e7a675aa.0
Via: SIP/2.0/UDP 212.117.200.148:5061;branch=z9hG4bK66c9f3611d196c795cb3f2b5fe9b9999;rport=5061
From: "49613132710899 "<sip:0613132710899@212.117.200.148>;tag=988489a24ef1d69c20ed4e4745f604fc
To: <sip:491801xxxxxxxxxxxx@212.117.200.148>;tag=-1816924010--2002429040
Call-ID: 50e5864b240078713271e6c071f69d3f@80.237.199.41
CSeq: 201 BYE
Expires: 300
Max-Forwards: 70
User-Agent: Sippy
S
16.08.2007 12:53:00 @<<<<<<<<<<@erver: Mops
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS
Content-Length: 0
[SIP-Packet] 2007/08/16 12:53:00,470
Sending datagram with length 743 from 87.167.214.25:32931 to 212.117.200.148:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 212.117.200.148;branch=z9hG4bKfbb1.1907614afb0cba23da6ec446e7a675aa.0
Via: SIP/2.0/UDP 212.117.200.148:5061;branch=z9hG4bK66c9f3611d196c795cb3f2b5fe9b9999;rport=5061
Record-Route: <sip:212.117.200.148:5060;ftag=-1816924010--2002429040;lr>
From: "49613132710899 "<sip:0613132710899@212.117.200.148>;tag=988489a24ef1d69c20ed4e4745f604fc
To: "491801xxxxxxxxxxxx"<sip:491801xxxxxxxxxxxx@212.117.200.148>;tag=-1816924010--2002429040
Call-ID: 50e5864b240078713271e6c071f69d3f@80.237.199.41
CSeq: 201 BYE
Max-Forwards: 70
User-Agent: LANCOM 1823 VoIP (Annex B) / 7.20.0065 / 11.08.2007 (SerialNo=059900600127)
Server: Mops
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS
Content-Length: 0
Gruß
Dietmar
Analyse Fax T.38 Trace / Faxempfang. Wie zu interpretieren?
Moderator: Lancom-Systems Moderatoren
-
froeschi62
- Beiträge: 985
- Registriert: 13 Dez 2004, 10:44
Analyse Fax T.38 Trace / Faxempfang. Wie zu interpretieren?
Lancom 1823 VOIP
-
froeschi62
- Beiträge: 985
- Registriert: 13 Dez 2004, 10:44