Jump to content

Eingehende Anrufe werde verbunden, ausgehende Anrufe enden mit Fehler


Steffen
 Share

Recommended Posts

Hallo,

 

wir können mit der Anlage intern telefonieren.

Anrufe nach extern enden mit Fehler 403 oder 503. Anrufe von extern werden verbunden, wobei der interne Teilnehmer gehört wird der externe jedoch nicht gehört wird.

 

Kann man aus dem Log sehen welche Einstellungen nicht zusammen passen?

Danke im Voraus.

 

[5] 2012/05/15 11:45:29: SIP Rx udp:88.79.233.153:5060:

INVITE sip:03575660395@192.168.178.20:5060;transport=udp;line=eccbc87e SIP/2.0

Via: SIP/2.0/UDP 88.79.233.153:5060;branch=z9hG4bK6do1qg308ou0e35ij321.1

To: <sip:03575660395@arcor.de;user=phone>

From: "01712622030" <sip:01712622030@arcor.de;user=phone>;tag=ffc4dd28

Call-ID: b86efdc11baaa45-0016-0348-0000-0000@82.82.17.24

CSeq: 1 INVITE

Max-Forwards: 69

Contact: <sip:01712622030@88.79.233.153:5060;transport=udp>

Date: Tue, 15 May 2012 11:45:29 GMT

Allow: INVITE, ACK, PRACK, CANCEL, BYE, OPTIONS, MESSAGE, NOTIFY, UPDATE, REGISTER, INFO, REFER, SUBSCRIBE

P-Asserted-Identity: <sip:01712622030@arcor.de>

Accept: application/sdp, application/isup, application/xml, application/media_control+xml, application/dtmf-relay

Content-Type: application/sdp

Content-Length: 204

 

v=0

o=- 0 202423208 IN IP4 88.79.233.153

s=IMSS

c=IN IP4 88.79.233.153

t=0 0

m=audio 15428 RTP/AVP 8 101 18 106

a=rtpmap:101 G726-32/8000

a=rtpmap:106 telephone-event/8000

a=sendrecv

a=ptime:20

[1] 2012/05/15 11:45:29: UDP: TOS could not be set

[1] 2012/05/15 11:45:29: Last message repeated 2 times

[5] 2012/05/15 11:45:29: SIP Tx udp:88.79.233.153:5060:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 88.79.233.153:5060;branch=z9hG4bK6do1qg308ou0e35ij321.1

From: "01712622030" <sip:01712622030@arcor.de;user=phone>;tag=ffc4dd28

To: <sip:03575660395@arcor.de;user=phone>;tag=1d12031c99

Call-ID: b86efdc11baaa45-0016-0348-0000-0000@82.82.17.24

CSeq: 1 INVITE

Content-Length: 0

 

[1] 2012/05/15 11:45:29: UDP: TOS could not be set

[1] 2012/05/15 11:45:29: Last message repeated 2 times

[5] 2012/05/15 11:45:29: SIP Tx udp:192.168.178.152:5060:

INVITE sip:41@192.168.178.152:5060 SIP/2.0

Via: SIP/2.0/UDP 192.168.178.20:5060;branch=z9hG4bK-d09f66999b604f36292fe5db6a749835;rport

From: "01712622030" <sip:01712622030@jwk.net;user=phone>;tag=365777152

To: "Petra Jannasch" <sip:41@jwk.net>

Call-ID: fe9e302c@pbx

CSeq: 25134 INVITE

Max-Forwards: 70

Contact: <sip:41@192.168.178.20:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: snomONE/4.5.0.1075 Delta Aurigids

Alert-Info: <http://127.0.0.1/Bellcore-dr3>

Content-Type: application/sdp

Content-Length: 353

 

v=0

o=- 1580263973 1580263973 IN IP4 192.168.178.20

s=-

c=IN IP4 192.168.178.20

t=0 0

m=audio 49434 RTP/AVP 8 0 9 3 2 101

a=rtpmap:8 pcma/8000

a=rtpmap:0 pcmu/8000

a=rtpmap:9 g722/8000

a=rtpmap:3 gsm/8000

a=rtpmap:2 g726-32/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=ptime:30

a=rtcp-xr:rcvr-rtt=all voip-metrics

a=sendrecv

[5] 2012/05/15 11:45:29: SIP Rx udp:192.168.178.152:5060:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 192.168.178.20:5060;branch=z9hG4bK-d09f66999b604f36292fe5db6a749835;rport=5060

From: "01712622030" <sip:01712622030@jwk.net;user=phone>;tag=365777152

To: "Petra Jannasch" <sip:41@jwk.net>;tag=2527840751

Call-ID: fe9e302c@pbx

CSeq: 25134 INVITE

Contact: <sip:41@192.168.178.152:5060>

Content-Length: 0

 

[5] 2012/05/15 11:45:31: SIP Rx udp:192.168.178.152:5060:

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 192.168.178.20:5060;branch=z9hG4bK-d09f66999b604f36292fe5db6a749835;rport=5060

From: "01712622030" <sip:01712622030@jwk.net;user=phone>;tag=365777152

To: "Petra Jannasch" <sip:41@jwk.net>;tag=2527840751

Call-ID: fe9e302c@pbx

CSeq: 25134 INVITE

Contact: <sip:41@192.168.178.152:5060>

Allow-Events: message-summary, refer, ua-profile

Content-Length: 0

 

[5] 2012/05/15 11:45:31: SIP Tx udp:88.79.233.153:5060:

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 88.79.233.153:5060;branch=z9hG4bK6do1qg308ou0e35ij321.1

From: "01712622030" <sip:01712622030@arcor.de;user=phone>;tag=ffc4dd28

To: <sip:03575660395@arcor.de;user=phone>;tag=1d12031c99

Call-ID: b86efdc11baaa45-0016-0348-0000-0000@82.82.17.24

CSeq: 1 INVITE

Contact: <sip:03575660395@192.168.178.20:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: snomONE/4.5.0.1075 Delta Aurigids

Content-Length: 0

 

[5] 2012/05/15 11:45:33: SIP Rx udp:192.168.178.152:5060:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 192.168.178.20:5060;branch=z9hG4bK-d09f66999b604f36292fe5db6a749835;rport=5060

From: "01712622030" <sip:01712622030@jwk.net;user=phone>;tag=365777152

To: "Petra Jannasch" <sip:41@jwk.net>;tag=2527840751

Call-ID: fe9e302c@pbx

CSeq: 25134 INVITE

Contact: <sip:41@192.168.178.152:5060>

Supported: replaces

Allow-Events: message-summary, refer, ua-profile

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

Content-Type: application/sdp

Content-Length: 200

 

v=0

o=41 5048 22 IN IP4 192.168.178.152

s=Mapping

c=IN IP4 192.168.178.152

t=0 0

m=audio 5048 RTP/AVP 8 101

a=rtpmap:8 PCMA/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=sendrecv

[5] 2012/05/15 11:45:33: set codec: codec pcma/8000 is set to call-leg 47

[5] 2012/05/15 11:45:33: SIP Tx udp:192.168.178.152:5060:

ACK sip:41@192.168.178.152:5060 SIP/2.0

Via: SIP/2.0/UDP 192.168.178.20:5060;branch=z9hG4bK-49535a1612927a8f434d9105a4dac180;rport

From: "01712622030" <sip:01712622030@jwk.net;user=phone>;tag=365777152

To: "Petra Jannasch" <sip:41@jwk.net>;tag=2527840751

Call-ID: fe9e302c@pbx

CSeq: 25134 ACK

Max-Forwards: 70

Contact: <sip:41@192.168.178.20:5060;transport=udp>

Content-Length: 0

 

[4] 2012/05/15 11:45:33: select returns error 60 (rtp)

[5] 2012/05/15 11:45:33: set codec: codec pcma/8000 is set to call-leg 46

[5] 2012/05/15 11:45:33: SIP Tx udp:88.79.233.153:5060:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 88.79.233.153:5060;branch=z9hG4bK6do1qg308ou0e35ij321.1

From: "01712622030" <sip:01712622030@arcor.de;user=phone>;tag=ffc4dd28

To: <sip:03575660395@arcor.de;user=phone>;tag=1d12031c99

Call-ID: b86efdc11baaa45-0016-0348-0000-0000@82.82.17.24

CSeq: 1 INVITE

Contact: <sip:03575660395@192.168.178.20:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: snomONE/4.5.0.1075 Delta Aurigids

Content-Type: application/sdp

Content-Length: 286

 

v=0

o=- 2070734628 2070734628 IN IP4 192.168.178.20

s=-

c=IN IP4 192.168.178.20

t=0 0

m=audio 56596 RTP/AVP 8 101 106

a=rtpmap:8 pcma/8000

a=rtpmap:101 g726-32/8000

a=rtpmap:106 telephone-event/8000

a=fmtp:106 0-16

a=ptime:20

a=rtcp-xr:rcvr-rtt=all voip-metrics

a=sendrecv

[5] 2012/05/15 11:45:33: SIP Rx udp:88.79.233.153:5060:

ACK sip:03575660395@192.168.178.20:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 88.79.233.153:5060;branch=z9hG4bKuqosus00a0ng55lum2o0.1

To: <sip:03575660395@arcor.de;user=phone>;tag=1d12031c99

From: "01712622030" <sip:01712622030@arcor.de;user=phone>;tag=ffc4dd28

Call-ID: b86efdc11baaa45-0016-0348-0000-0000@82.82.17.24

CSeq: 1 ACK

Max-Forwards: 69

Content-Length: 0

 

[5] 2012/05/15 11:45:41: SIP Rx udp:192.168.178.152:5060:

BYE sip:41@192.168.178.20:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 192.168.178.152:5060;branch=z9hG4bK62e46466c8144f50649f464b9bf46c9a;rport

From: "Petra Jannasch" <sip:41@jwk.net>;tag=2527840751

To: "01712622030" <sip:01712622030@jwk.net;user=phone>;tag=365777152

Call-ID: fe9e302c@pbx

CSeq: 25135 BYE

Contact: <sip:41@192.168.178.152:5060>

Max-Forwards: 70

User-Agent: N510 IP PRO/42.051.01.000.000

Content-Length: 0

 

[5] 2012/05/15 11:45:41: SIP Tx udp:192.168.178.152:5060:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 192.168.178.152:5060;branch=z9hG4bK62e46466c8144f50649f464b9bf46c9a;rport=5060

From: "Petra Jannasch" <sip:41@jwk.net>;tag=2527840751

To: "01712622030" <sip:01712622030@jwk.net;user=phone>;tag=365777152

Call-ID: fe9e302c@pbx

CSeq: 25135 BYE

Contact: <sip:41@192.168.178.20:5060;transport=udp>

User-Agent: snomONE/4.5.0.1075 Delta Aurigids

Content-Length: 0

 

[4] 2012/05/15 11:45:41: select returns error 60 (rtp)

[5] 2012/05/15 11:45:41: SIP Tx udp:88.79.233.153:5060:

BYE sip:01712622030@88.79.233.153:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 192.168.178.20:5060;branch=z9hG4bK-215a1fa12e60b70b7d0ac816cce23a7c;rport

From: <sip:03575660395@arcor.de;user=phone>;tag=1d12031c99

To: "01712622030" <sip:01712622030@arcor.de;user=phone>;tag=ffc4dd28

Call-ID: b86efdc11baaa45-0016-0348-0000-0000@82.82.17.24

CSeq: 22935 BYE

Max-Forwards: 70

Contact: <sip:03575660395@192.168.178.20:5060;transport=udp>

Content-Length: 0

 

[5] 2012/05/15 11:45:41: SIP Rx udp:88.79.233.153:5060:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 192.168.178.20:5060;received=192.168.178.20;branch=z9hG4bK-215a1fa12e60b70b7d0ac816cce23a7c;rport=5060

From: <sip:03575660395@arcor.de;user=phone>;tag=1d12031c99

To: "01712622030" <sip:01712622030@arcor.de;user=phone>;tag=ffc4dd28

Call-ID: b86efdc11baaa45-0016-0348-0000-0000@82.82.17.24

CSeq: 22935 BYE

Accept: application/sdp, application/isup, application/xml, application/media_control+xml

Allow: INVITE, ACK, PRACK, CANCEL, BYE, OPTIONS, MESSAGE, NOTIFY, UPDATE, REGISTER, INFO, REFER, SUBSCRIBE

Contact: <sip:01712622030@88.79.233.153:5060;transport=udp>

Content-Length: 0

 

[5] 2012/05/15 11:45:41: BYE Response: Terminate b86efdc11baaa45-0016-0348-0000-0000@82.82.17.24

[4] 2012/05/15 11:45:41: select returns error 60 (rtp)

Link to comment
Share on other sites

Vom Log her sieht eigentlich alles gut aus... Die PBX ist ja offenbar auf einer Adresse die nicht öffentlich sichtbar ist (NAT), aber immerhin kommt der Anruf rein und das ist ein gutes Zeichen, dass der provider (Arcor) irgendeine NAT-Lösung in Einsatz hat. Wenn die SIP zustellen kann wird sie auch sicher in der Lage sein, RTP-Daten zu schicken, zumal ja dir Richtung zu Arcor funktioniert.

 

Die einzige Idee die ich hätte ist dass die RTCP-XR Entensions Arcor verwirren. Es gibt einige globale Settings rtcp_loss_rle, rtcp_dup_rle, rtcp_rcpt_times, rtcp_rcvr_rtt, rtcp_stat_summary, rtcp_voip_metrics die ich alle mal auf "false" setzen würde. Entweder manuell durch das Webinterface oder falls ein Neustart kein großes Problem darstellt, in der Datei pbx.xml editieren.

Link to comment
Share on other sites

Vom Log her sieht eigentlich alles gut aus... Die PBX ist ja offenbar auf einer Adresse die nicht öffentlich sichtbar ist (NAT), aber immerhin kommt der Anruf rein und das ist ein gutes Zeichen, dass der provider (Arcor) irgendeine NAT-Lösung in Einsatz hat. Wenn die SIP zustellen kann wird sie auch sicher in der Lage sein, RTP-Daten zu schicken, zumal ja dir Richtung zu Arcor funktioniert.

 

Die einzige Idee die ich hätte ist dass die RTCP-XR Entensions Arcor verwirren. Es gibt einige globale Settings rtcp_loss_rle, rtcp_dup_rle, rtcp_rcpt_times, rtcp_rcvr_rtt, rtcp_stat_summary, rtcp_voip_metrics die ich alle mal auf "false" setzen würde. Entweder manuell durch das Webinterface oder falls ein Neustart kein großes Problem darstellt, in der Datei pbx.xml editieren.

 

 

Ein Neustart der pbx ist kein Problem, aber was schreibe ich in die Datei pbx.xml ?

Link to comment
Share on other sites

Ein Neustart der pbx ist kein Problem, aber was schreibe ich in die Datei pbx.xml ?

 

In pbx.xml ist schon jede Menge XML. Einfach nach den Settings oben suchen, und bei denen "true" mit "false" ersetzen (am besten vorher ein backup machen damit nichts kaputt geht). Ist keine Erfolgsgarantie, aber alles andere sieht unverdächtig aus...

Link to comment
Share on other sites

In pbx.xml ist schon jede Menge XML. Einfach nach den Settings oben suchen, und bei denen "true" mit "false" ersetzen (am besten vorher ein backup machen damit nichts kaputt geht). Ist keine Erfolgsgarantie, aber alles andere sieht unverdächtig aus...

 

 

Das hat geholfen.

Es mussten nur noch die Settings "rtcp_rcvr_rtt, rtcp_voip_metrics" auf false gesetzt werden die anderen waren schon. Bei Anrufen von extern nach intern hören sich jetzt beide Anrufer.

 

Nun das andere Problem. Anrufe von intern nach extern enden mit der Fehlermeldung 403 oder 503, je nach Einstellung. Kann man aus dem Log erkennen welche Einstellungen ich ändern muss damit es geht?

 

 

 

[5] 2012/05/16 11:14:04: SIP Rx udp:192.168.178.152:5060:

INVITE sip:01712622030@N510;user=phone SIP/2.0

Via: SIP/2.0/UDP 192.168.178.152:5060;branch=z9hG4bK896e3c7ca925ea9d3e6ec90ea36be4e2;rport

From: "Petra" <sip:41@N510>;tag=2412608137

To: <sip:01712622030@N510;user=phone>

Call-ID: 2382582265@192_168_178_152

CSeq: 2 INVITE

Contact: <sip:41@192.168.178.152:5060>

Max-Forwards: 70

User-Agent: N510 IP PRO/42.051.01.000.000

Supported: replaces

Allow-Events: message-summary, refer, ua-profile

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

Content-Type: application/sdp

Content-Length: 351

 

v=0

o=41 5028 9 IN IP4 192.168.178.152

s=Mapping

c=IN IP4 192.168.178.152

t=0 0

m=audio 5028 RTP/AVP 9 0 8 96 97 2 18 101

a=rtpmap:9 G722/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:96 G726-32/8000

a=rtpmap:97 AAL2-G726-32/8000

a=rtpmap:2 G726-32/8000

a=rtpmap:18 G729/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

[1] 2012/05/16 11:14:04: UDP: TOS could not be set

[1] 2012/05/16 11:14:04: Last message repeated 2 times

[5] 2012/05/16 11:14:04: SIP Tx udp:192.168.178.152:5060:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 192.168.178.152:5060;branch=z9hG4bK896e3c7ca925ea9d3e6ec90ea36be4e2;rport=5060

From: "Petra" <sip:41@N510>;tag=2412608137

To: <sip:01712622030@N510;user=phone>;tag=8b81b4c9ee

Call-ID: 2382582265@192_168_178_152

CSeq: 2 INVITE

Content-Length: 0

 

[5] 2012/05/16 11:14:04: SIP Tx udp:192.168.178.152:5060:

SIP/2.0 401 Authentication Required

Via: SIP/2.0/UDP 192.168.178.152:5060;branch=z9hG4bK896e3c7ca925ea9d3e6ec90ea36be4e2;rport=5060

From: "Petra" <sip:41@N510>;tag=2412608137

To: <sip:01712622030@N510;user=phone>;tag=8b81b4c9ee

Call-ID: 2382582265@192_168_178_152

CSeq: 2 INVITE

User-Agent: snomONE/4.5.0.1075 Delta Aurigids

WWW-Authenticate: Digest realm="n510",nonce="0cb76f6929489236be4d90847c745b72",domain="sip:01712622030@N510;user=phone",algorithm=MD5

Content-Length: 0

 

[5] 2012/05/16 11:14:04: SIP Rx udp:192.168.178.152:5060:

ACK sip:01712622030@N510;user=phone SIP/2.0

Via: SIP/2.0/UDP 192.168.178.152:5060;branch=z9hG4bK896e3c7ca925ea9d3e6ec90ea36be4e2;rport

From: "Petra" <sip:41@N510>;tag=2412608137

To: <sip:01712622030@N510;user=phone>;tag=8b81b4c9ee

Call-ID: 2382582265@192_168_178_152

CSeq: 2 ACK

Contact: <sip:41@192.168.178.152:5060>

Max-Forwards: 70

User-Agent: N510 IP PRO/42.051.01.000.000

Content-Length: 0

 

[5] 2012/05/16 11:14:04: SIP Rx udp:192.168.178.152:5060:

INVITE sip:01712622030@N510;user=phone SIP/2.0

Via: SIP/2.0/UDP 192.168.178.152:5060;branch=z9hG4bK97d9606b6ec9b4c8196e7cd3debdf86a;rport

From: "Petra" <sip:41@N510>;tag=2412608137

To: <sip:01712622030@N510;user=phone>

Call-ID: 2382582265@192_168_178_152

CSeq: 3 INVITE

Contact: <sip:41@192.168.178.152:5060>

Authorization: Digest username="41", realm="n510", algorithm=MD5, uri="sip:01712622030@N510;user=phone", nonce="0cb76f6929489236be4d90847c745b72", response="dd6ca28d13cf18f91cecf3cac093ba87"

Max-Forwards: 70

User-Agent: N510 IP PRO/42.051.01.000.000

Supported: replaces

Allow-Events: message-summary, refer, ua-profile

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

Content-Type: application/sdp

Content-Length: 351

 

v=0

o=41 5028 9 IN IP4 192.168.178.152

s=Mapping

c=IN IP4 192.168.178.152

t=0 0

m=audio 5028 RTP/AVP 9 0 8 96 97 2 18 101

a=rtpmap:9 G722/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:96 G726-32/8000

a=rtpmap:97 AAL2-G726-32/8000

a=rtpmap:2 G726-32/8000

a=rtpmap:18 G729/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

[5] 2012/05/16 11:14:04: SIP Tx udp:192.168.178.152:5060:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 192.168.178.152:5060;branch=z9hG4bK97d9606b6ec9b4c8196e7cd3debdf86a;rport=5060

From: "Petra" <sip:41@N510>;tag=2412608137

To: <sip:01712622030@N510;user=phone>;tag=8b81b4c9ee

Call-ID: 2382582265@192_168_178_152

CSeq: 3 INVITE

Content-Length: 0

 

[1] 2012/05/16 11:14:04: UDP: TOS could not be set

[1] 2012/05/16 11:14:04: Last message repeated 2 times

[5] 2012/05/16 11:14:04: SIP Tx udp:88.79.233.153:5060:

INVITE sip:01712622030@035756.sip.arcor.de;user=phone SIP/2.0

Via: SIP/2.0/UDP 192.168.178.20:5060;branch=z9hG4bK-6bc05dadf6f902a9121452101b28fd2d;rport

From: "Petra Jannasch" <sip:41@jwk.net>;tag=920009847

To: <sip:01712622030@jwk.net;user=phone>

Call-ID: ff9a9b51@pbx

CSeq: 17601 INVITE

Max-Forwards: 70

Contact: <sip:035756630067@192.168.178.20:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: snomONE/4.5.0.1075 Delta Aurigids

Remote-Party-ID: "Petra Jannasch" <sip:03575660395@jwk.net;user=phone>

Privacy: id

P-Charging-Vector: icid-value=;icid-generated-at=192.168.178.20;orig-ioi=jwk.net

Content-Type: application/sdp

Content-Length: 314

 

v=0

o=- 355758798 355758798 IN IP4 192.168.178.20

s=-

c=IN IP4 192.168.178.20

t=0 0

m=audio 60178 RTP/AVP 8 0 9 3 2 101

a=rtpmap:8 pcma/8000

a=rtpmap:0 pcmu/8000

a=rtpmap:9 g722/8000

a=rtpmap:3 gsm/8000

a=rtpmap:2 g726-32/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=ptime:30

a=sendrecv

[5] 2012/05/16 11:14:04: set codec: codec pcma/8000 is set to call-leg 24

[5] 2012/05/16 11:14:04: SIP Tx udp:192.168.178.152:5060:

SIP/2.0 183 Session Progress

Via: SIP/2.0/UDP 192.168.178.152:5060;branch=z9hG4bK97d9606b6ec9b4c8196e7cd3debdf86a;rport=5060

From: "Petra" <sip:41@N510>;tag=2412608137

To: <sip:01712622030@N510;user=phone>;tag=8b81b4c9ee

Call-ID: 2382582265@192_168_178_152

CSeq: 3 INVITE

Contact: <sip:41@192.168.178.20:5060>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: snomONE/4.5.0.1075 Delta Aurigids

Content-Type: application/sdp

Content-Length: 293

 

v=0

o=- 1746023247 1746023247 IN IP4 192.168.178.20

s=-

c=IN IP4 192.168.178.20

t=0 0

m=audio 59526 RTP/AVP 8 0 9 2 101

a=rtpmap:8 pcma/8000

a=rtpmap:0 pcmu/8000

a=rtpmap:9 g722/8000

a=rtpmap:2 g726-32/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=ptime:30

a=sendrecv

[4] 2012/05/16 11:14:04: select returns error 60 (rtp)

[5] 2012/05/16 11:14:04: SIP Rx udp:88.79.233.153:5060:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 192.168.178.20:5060;received=192.168.178.20;branch=z9hG4bK-6bc05dadf6f902a9121452101b28fd2d;rport=5060

From: "Petra Jannasch" <sip:41@jwk.net>;tag=920009847

To: <sip:01712622030@jwk.net;user=phone>

Call-ID: ff9a9b51@pbx

CSeq: 17601 INVITE

 

[5] 2012/05/16 11:14:04: SIP Rx udp:88.79.233.153:5060:

SIP/2.0 403 Forbidden

Via: SIP/2.0/UDP 192.168.178.20:5060;received=192.168.178.20;branch=z9hG4bK-6bc05dadf6f902a9121452101b28fd2d;rport=5060

From: "Petra Jannasch" <sip:41@jwk.net>;tag=920009847

To: <sip:01712622030@jwk.net;user=phone>;tag=aprqngfrt-f2kv610000h2c

Call-ID: ff9a9b51@pbx

CSeq: 17601 INVITE

 

[5] 2012/05/16 11:14:04: SIP Tx udp:88.79.233.153:5060:

ACK sip:01712622030@035756.sip.arcor.de;user=phone SIP/2.0

Via: SIP/2.0/UDP 192.168.178.20:5060;branch=z9hG4bK-6bc05dadf6f902a9121452101b28fd2d;rport

From: "Petra Jannasch" <sip:41@jwk.net>;tag=920009847

To: <sip:01712622030@jwk.net;user=phone>;tag=aprqngfrt-f2kv610000h2c

Call-ID: ff9a9b51@pbx

CSeq: 17601 ACK

Max-Forwards: 70

Contact: <sip:035756630067@192.168.178.20:5060;transport=udp>

Remote-Party-ID: "Petra Jannasch" <sip:03575660395@jwk.net;user=phone>

Privacy: id

P-Charging-Vector: icid-value=;icid-generated-at=192.168.178.20;orig-ioi=jwk.net

Content-Length: 0

 

[5] 2012/05/16 11:14:04: INVITE Response 403 Forbidden: Terminate ff9a9b51@pbx

[4] 2012/05/16 11:14:04: select returns error 60 (rtp)

[5] 2012/05/16 11:14:04: SIP Tx udp:192.168.178.152:5060:

SIP/2.0 403 Forbidden

Via: SIP/2.0/UDP 192.168.178.152:5060;branch=z9hG4bK97d9606b6ec9b4c8196e7cd3debdf86a;rport=5060

From: "Petra" <sip:41@N510>;tag=2412608137

To: <sip:01712622030@N510;user=phone>;tag=8b81b4c9ee

Call-ID: 2382582265@192_168_178_152

CSeq: 3 INVITE

Contact: <sip:41@192.168.178.20:5060>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: snomONE/4.5.0.1075 Delta Aurigids

Content-Length: 0

 

[5] 2012/05/16 11:14:04: SIP Rx udp:192.168.178.152:5060:

ACK sip:01712622030@N510;user=phone SIP/2.0

Via: SIP/2.0/UDP 192.168.178.152:5060;branch=z9hG4bK97d9606b6ec9b4c8196e7cd3debdf86a;rport

From: "Petra" <sip:41@N510>;tag=2412608137

To: <sip:01712622030@N510;user=phone>;tag=8b81b4c9ee

Call-ID: 2382582265@192_168_178_152

CSeq: 3 ACK

Contact: <sip:41@192.168.178.152:5060>

Authorization: Digest username="41", realm="n510", algorithm=MD5, uri="sip:01712622030@N510;user=phone", nonce="0cb76f6929489236be4d90847c745b72", response="dd6ca28d13cf18f91cecf3cac093ba87"

Max-Forwards: 70

User-Agent: N510 IP PRO/42.051.01.000.000

Content-Length: 0

 

[4] 2012/05/16 11:14:04: select returns error 60 (rtp)

Link to comment
Share on other sites

Jetzt reden wir über die SIP-Header... So wie es aussieht mag Arcor Remote-Party nicht für die Authentifizierung. Es gibt einige drop-downs für die Header im trunk (Leitung), wenn wir die Zugangsdaten mal bekommen können wir gerne versuchen, die optimale Einstellung herauszufinden.

Link to comment
Share on other sites

Jetzt reden wir über die SIP-Header... So wie es aussieht mag Arcor Remote-Party nicht für die Authentifizierung. Es gibt einige drop-downs für die Header im trunk (Leitung), wenn wir die Zugangsdaten mal bekommen können wir gerne versuchen, die optimale Einstellung herauszufinden.

 

Jetzt funktioniert auch das Telefonieren nach extern (auf einmal auch mit Remote-Party-ID).

 

Danke und ich wünsche ein langes Wochenende.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...