ISDN-SIP Gateway - T.38 FAX

Raudi · Beitrag von **Raudi** » 15 Aug 2007, 13:35

Hallo,

ich wollte mal testen, ob ich ein FAX von ISDN an eine SIP Applikation, die Faxen kann und T.38 voraussetzt, schicken kann. Leider kommt aber kein Verbindungsaufbau zustande.

Hier mal ein SIP-Trace vom Verbindungsaufbau:

Code: Alles auswählen

[SIP-Packet] 2007/08/15 13:26:49,900
Receiving datagram with length 346 from 192.168.99.13:5060 to 192.168.98.105:5060
BYE sip:0421491480@192.168.98.105:5060 SIP/2.0

Via: SIP/2.0/UDP 192.168.99.13:5060;branch=z9hG4bK1004510344-1966748

Max-Forwards: 70

From: <sip:41@raudonis.voip;user=phone>;tag=eicon_946870344-1835676

To: <sip:0421491480@raudonis.voip;user=phone>;tag=-284650404-1421828214

Call-ID: 3843686984@00a05711a64e

CSeq: 3 BYE

Content-Length: 0





[SIP-Packet] 2007/08/15 13:26:49,900
Sending datagram with length 517 from 192.168.98.105:5060 to 192.168.99.13:5060
SIP/2.0 481 Call/Transaction Does Not Exist

Via: SIP/2.0/UDP 192.168.99.13:5060;branch=z9hG4bK1004510344-1966748

From: <sip:41@raudonis.voip;user=phone>;tag=eicon_946870344-1835676

To: <sip:0421491480@raudonis.voip;user=phone>;tag=-284650404-1421828214

Call-ID: 3843686984@00a05711a64e

CSeq: 3 BYE

Max-Forwards: 70

User-Agent: LANCOM 1722 VoIP (Annex B) / 7.20.0065 / 11.08.2007 (SerialNo=047150600092)

Server: dsl-home

Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS

Content-Length: 0





[SIP-Packet] 2007/08/15 13:26:52,180
Sending datagram with length 909 from 192.168.98.105:5060 to 192.168.99.13:5060
INVITE sip:41@raudonis.voip SIP/2.0

Via: SIP/2.0/UDP 192.168.98.105:5060;branch=z9hG4bK-73b2e558-6661f1c3

From: <sip:0421491480@raudonis.voip;user=phone>;tag=-1797200894-779685667

To: <sip:41@raudonis.voip;user=phone>

Call-ID: 126758202@00a05711a64e

CSeq: 1 INVITE

Max-Forwards: 70

User-Agent: LANCOM 1722 VoIP (Annex B) / 7.20.0065 / 11.08.2007 (SerialNo=047150600092)

Server: dsl-home

Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS

Contact: <sip:0421491480@192.168.98.105:5060>

Content-Type: application/sdp

Content-Length: 345



v=0

o=- 63379101 63379101 IN IP4 192.168.98.105

s=-

c=IN IP4 192.168.98.105

t=0 0

m=audio 37550 RTP/AVP 8 0 106 2 104 103 101 102

a=rtpmap:8 PCMA/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:106 G726-40/8000

a=rtpmap:2 G726-32/8000

a=rtpmap:104 G726-24/8000

a=rtpmap:103 G726-16/8000

a=rtpmap:101 telephone-event/8000

a=rtpmap:102 tone/8000



[SIP-Packet] 2007/08/15 13:26:52,210
Receiving datagram with length 346 from 192.168.99.13:5060 to 192.168.98.105:5060
SIP/2.0 100 Trying

Via: SIP/2.0/UDP 192.168.98.105:5060;branch=z9hG4bK-73b2e558-6661f1c3

From: <sip:0421491480@raudonis.voip;user=phone>;tag=-1797200894-779685667

To: <sip:41@raudonis.voip;user=phone>;tag=eicon_1006823344-2097820

Call-ID: 126758202@00a05711a64e

CSeq: 1 INVITE

Contact: <sip:softip@192.168.99.13:5060>

Content-Length: 0





[SIP-Packet] 2007/08/15 13:26:52,290
Receiving datagram with length 678 from 192.168.99.13:5060 to 192.168.98.105:5060
SIP/2.0 200 OK

Via: SIP/2.0/UDP 192.168.98.105:5060;branch=z9hG4bK-73b2e558-6661f1c3

From: <sip:0421491480@raudonis.voip;user=phone>;tag=-1797200894-779685667

To: <sip:41@raudonis.voip;user=phone>;tag=eicon_1006823344-2097820

Call-ID: 126758202@00a05711a64e

CSeq: 1 INVITE

Contact: <sip:softip@192.168.99.13:5060>

Allow: SUBSCRIBE,NOTIFY,REFER,INVITE,ACK,OPTIONS,CANCEL,BYE

Content-Type: application/sdp

Content-Length: 242



v=0

o=eicon 256 2 IN IP4 192.168.99.13

s=SipSession with SoftIP

i=SoftIP

u=http://www.eicon.com

c=IN IP4 192.168.99.13

t=0 0

m=audio 20024 RTP/AVP 8 0 101

a=rtpmap:8 PCMA/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000



[SIP-Packet] 2007/08/15 13:26:52,290
Sending datagram with length 516 from 192.168.98.105:5060 to 192.168.99.13:5060
ACK sip:softip@192.168.99.13:5060 SIP/2.0

Via: SIP/2.0/UDP 192.168.98.105:5060;branch=z9hG4bK-8444c138-833554e2

From: <sip:0421491480@raudonis.voip;user=phone>;tag=-1797200894-779685667

To: <sip:41@raudonis.voip;user=phone>;tag=eicon_1006823344-2097820

Call-ID: 126758202@00a05711a64e

CSeq: 1 ACK

Max-Forwards: 70

User-Agent: LANCOM 1722 VoIP (Annex B) / 7.20.0065 / 11.08.2007 (SerialNo=047150600092)

Server: dsl-home

Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS

Content-Length: 0





[SIP-Packet] 2007/08/15 13:26:52,320
Receiving datagram with length 912 from 192.168.99.13:5060 to 192.168.98.105:5060
INVITE sip:0421491480@192.168.98.105:5060 SIP/2.0

Via: SIP/2.0/UDP 192.168.99.13:5060;branch=z9hG4bK1006932344-2163356

Max-Forwards: 70

Allow: SUBSCRIBE,NOTIFY,REFER,INVITE,ACK,OPTIONS,CANCEL,BYE

Supported: timer,replaces

From: <sip:41@raudonis.voip;user=phone>;tag=eicon_1006823344-2097820

To: <sip:0421491480@raudonis.voip;user=phone>;tag=-1797200894-779685667

Call-ID: 126758202@00a05711a64e

CSeq: 2 INVITE

Contact: <sip:softip@192.168.99.13:5060>

Content-Type: application/sdp

Content-Length: 397



v=0

o=eicon 256 3 IN IP4 192.168.99.13

s=SipSession with SoftIP

i=SoftIP

u=http://www.eicon.com

c=IN IP4 192.168.99.13

t=0 0

m=image 20026 udptl t38

a=T38FaxVersion:0

a=T38maxBitRate:14400

a=T38FaxFillBitRemoval:0

a=T38FaxTranscodingMMR:0

a=T38FaxTranscodingJBIG:0

a=T38FaxRateManagement:transferredTCF

a=T38FaxMaxBuffer:284

a=T38FaxMaxDatagram:128

a=T38FaxUdpEC:t38UDPRedundancy



[SIP-Packet] 2007/08/15 13:26:52,320
Sending datagram with length 495 from 192.168.98.105:5060 to 192.168.99.13:5060
SIP/2.0 100 Trying

Via: SIP/2.0/UDP 192.168.99.13:5060;branch=z9hG4bK1006932344-2163356

From: <sip:41@raudonis.voip;user=phone>;tag=eicon_1006823344-2097820

To: <sip:0421491480@raudonis.voip;user=phone>;tag=-1797200894-779685667

Call-ID: 126758202@00a05711a64e

CSeq: 2 INVITE

Max-Forwards: 70

User-Agent: LANCOM 1722 VoIP (Annex B) / 7.20.0065 / 11.08.2007 (SerialNo=047150600092)

Server: dsl-home

Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS

Content-Length: 0





[SIP-Packet] 2007/08/15 13:26:52,330
Sending datagram with length 498 from 192.168.98.105:5060 to 192.168.99.13:5060
SIP/2.0 404 Not Found

Via: SIP/2.0/UDP 192.168.99.13:5060;branch=z9hG4bK1006932344-2163356

From: <sip:41@raudonis.voip;user=phone>;tag=eicon_1006823344-2097820

To: <sip:0421491480@raudonis.voip;user=phone>;tag=-1797200894-779685667

Call-ID: 126758202@00a05711a64e

CSeq: 2 INVITE

Max-Forwards: 70

User-Agent: LANCOM 1722 VoIP (Annex B) / 7.20.0065 / 11.08.2007 (SerialNo=047150600092)

Server: dsl-home

Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS

Content-Length: 0





[SIP-Packet] 2007/08/15 13:26:52,350
Receiving datagram with length 388 from 192.168.99.13:5060 to 192.168.98.105:5060
ACK sip:0421491480@192.168.98.105:5060 SIP/2.0

Via: SIP/2.0/UDP 192.168.99.13:5060;branch=z9hG4bK1006932344-2163356

Max-Forwards: 70

From: <sip:41@raudonis.voip;user=phone>;tag=eicon_1006823344-2097820

To: <sip:0421491480@raudonis.voip;user=phone>;tag=-1797200894-779685667

Call-ID: 126758202@00a05711a64e

CSeq: 2 ACK

Contact: <sip:softip@192.168.99.13:5060>

Content-Length: 0





[SIP-Packet] 2007/08/15 13:26:52,350
Sending datagram with length 517 from 192.168.98.105:5060 to 192.168.99.13:5060
SIP/2.0 481 Call/Transaction Does Not Exist

Via: SIP/2.0/UDP 192.168.99.13:5060;branch=z9hG4bK1006932344-2163356

From: <sip:41@raudonis.voip;user=phone>;tag=eicon_1006823344-2097820

To: <sip:0421491480@raudonis.voip;user=phone>;tag=-1797200894-779685667

Call-ID: 126758202@00a05711a64e

CSeq: 2 ACK

Max-Forwards: 70

User-Agent: LANCOM 1722 VoIP (Annex B) / 7.20.0065 / 11.08.2007 (SerialNo=047150600092)

Server: dsl-home

Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS

Content-Length: 0





[SIP-Packet] 2007/08/15 13:27:49,860
Receiving datagram with length 346 from 192.168.99.13:5060 to 192.168.98.105:5060
BYE sip:0421491480@192.168.98.105:5060 SIP/2.0

Via: SIP/2.0/UDP 192.168.99.13:5060;branch=z9hG4bK1064494344-2228892

Max-Forwards: 70

From: <sip:41@raudonis.voip;user=phone>;tag=eicon_1006823344-2097820

To: <sip:0421491480@raudonis.voip;user=phone>;tag=-1797200894-779685667

Call-ID: 126758202@00a05711a64e

CSeq: 3 BYE

Content-Length: 0





[SIP-Packet] 2007/08/15 13:27:49,860
Sending datagram with length 517 from 192.168.98.105:5060 to 192.168.99.13:5060
SIP/2.0 481 Call/Transaction Does Not Exist

Via: SIP/2.0/UDP 192.168.99.13:5060;branch=z9hG4bK1064494344-2228892

From: <sip:41@raudonis.voip;user=phone>;tag=eicon_1006823344-2097820

To: <sip:0421491480@raudonis.voip;user=phone>;tag=-1797200894-779685667

Call-ID: 126758202@00a05711a64e

CSeq: 3 BYE

Max-Forwards: 70

User-Agent: LANCOM 1722 VoIP (Annex B) / 7.20.0065 / 11.08.2007 (SerialNo=047150600092)

Server: dsl-home

Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS

Content-Length: 0

Evtl. hat ja jemand einen Tipp für mich, wo es harkt...

Gruß
Stefan

Raudi · Beitrag von **Raudi** » 15 Aug 2007, 14:36

Ich habe ja mal etwas gesucht, und das einzige was ich da als Fehlermeldung sehe ist dieses:

SIP/2.0 404 Not Found

In einer Cisco Doku habe ich dieses gefunden: (Ich hoffe mal die Error Codes sind einheitlich.)

The SIP gateway generates this response if it is unable to locate the callee.

Nur was bedeutet hier callee?

Dazu findet man auch einiges im Internet:

The function or procedure being called by the caller; e.g. function 'bar' calls the function 'foo', making 'bar' the caller and 'foo' the callee. - Das würde bedeuten, die Gegenstelle fordert eine Funktion die das Gateway nicht unterstützt - T.38?

Oder einfach nur callee für "angerufener", das würede bedeuten, das der LANCOM die 41 nicht findet.

Gruß
Stefan

backslash · Beitrag von **backslash** » 15 Aug 2007, 18:08

Hi Raudi

Nur was bedeutet hier callee?

callee bedeutet: Angerufener...

Oder einfach nur callee für "angerufener", das würede bedeuten, das der LANCOM die 41 nicht findet.

nein, das LANCOM hat die 0421491480 nicht gefunden, warum auch immer... vielleicht mag das LANCOM ja nicht, wenn das T.38 Reeinvite von einem internen SIP-Gerät kommt, statt vom LANCOM selbst generiert zu werden...

Gruß
Backslash

Raudi · Beitrag von **Raudi** » 15 Aug 2007, 18:11

Also werde ich am besten das ganze mal an den Support weiterreichen...

Danke.

Gruß
Stefan

ittk · Beitrag von **ittk** » 15 Aug 2007, 20:57

Hallo Raudi,

um welche Applikation handelt es sich? Bitte den vollstaendigen trace # sip call an den Support senden. Bei T.38 muss u.U. noch einiges je nach Gegenstelle angepasst werden. Gegen den Cisco Call-Manager ist es bereits interoperabel.

Raudi · Beitrag von **Raudi** » 15 Aug 2007, 23:12

Hallo,

es handelt sich um Diva Server SoftIP - SIP enviroment http://www.eicon.com/worldwide/products ... p-sip.htm.

Dieses ist der Ersatz für eine aktive ISDN Karte die man ja nun z.B. unter VMware nicht hat, um aus Exchange mit z.B. dem GFI FaxMaker for Exchange zu faxen.

Gruß
Stefan