RTP da, aber nicht hörbar, unter Umständen

Bronko · February 17, 2013

Hallo,

habe hier ver. 5.0.5 hinter NAT mit 3 Extensions: 1x snom 300, 1x Gigaset C475 IP, 1x C610A IP und Trunks zur DTAG und Sipgate.

Alles läuft seit über einem Jahren prima, bis sich bei ver. 5.0.3 ohne Änderungen am C475 IP plötzlich folgendes Verhalten zeigte:

Calls vom C475 IP nach extern lassen mich weder das Rufzeichen noch den Gesprächspartner hören;

Calls vom C475 IP nach snomone-intern verlaufen normal;

Transferiere ich ein zuvor vom snom 300 nach extern aufgebauten Call zum C475 IP läuft es ebenfalls normal;

Calls zum C475 IP von ex- oder intern verlaufen ebenfalls wie gewohnt.

Kurz, alles bis auf den externen Call vom C475 IP läuft wie es soll.

Habe die Traces für einen externen Call vom snom 300 mit dem vom C475 IP verglichen und keine relevanten Unterschiede erkannt; ohne aber ein SIP Profi zu sein.

Mit wireshark telephony analyse sehe ich, das selbst der RTP Stream zum C475 IP vorhanden ist und im player des wiresharks auch hörbar ist.

Welches Mobilteil ich am C475 IP benutze ist egal, stets das gleiche Ergebnis.

Mein Backup der ver. 4.5.0.1090 zeigt gleiches Bild.

Am C610A IP und snom 300 läuft alles wie gewohnt.

Beide pcap's wären bei Interesse verfügbar.

Kann jemand helfen?

Gruß...

Vodia PBX · February 17, 2013

Da es sich bei der PBX um einen B2BUA handelt, sollte man eigentlich ausschliessen können, dass irgendwas vom C475 auf den Trunk "durchschlägt". Klappt es denn wenn das snom sich auf der Extension von dem C475 registriert? Vielleicht liegt es einfach daran, dass das C475 auf CLIP steht und deswegen der Trunk-Provider streikt.

Bronko · February 17, 2013

Danke für die Antwort. Ein Wechsel der Extension bringt leider nichts, selbes Verhalten beider Telefone an der jeweils anderen Extension.

Nachtrag:

Die "audio_moh/noise.wav" höre ich noch am C475 IP bei externem Rufaufbau.

Bronko · February 19, 2013

So sieht der RTP debug log des C475 IP aus:

Feb 17 00:13:01 snomone Call limit reached. Call ports 1, g729 0 
Feb 17 00:13:01 snomone Call-leg 8: Sending RTP for 2399213226@192_168_6_68 to 192.168.6.68:5006, codec not set yet 
Feb 17 00:13:01 snomone Call port 8: set_codecs for 2399213226@192_168_6_68 codecs "", codec_preference count 6 
Feb 17 00:13:01 snomone Call port 9: set_codecs for 36979480@pbx codecs "", codec_preference count 6 
Feb 17 00:13:01 snomone call port 9: state code from 0 to 100 
Feb 17 00:13:01 snomone Call port 9: update_codecs for 36979480@pbx: adding codec PCMU/8000 to available list 
Feb 17 00:13:01 snomone Call port 9: update_codecs for 36979480@pbx: adding codec PCMA/8000 to available list 
Feb 17 00:13:01 snomone Call port 9: update_codecs for 36979480@pbx: adding codec G722/8000 to available list 
Feb 17 00:13:01 snomone Call port 9: update_codecs for 36979480@pbx: adding codec G726-32/8000 to available list 
Feb 17 00:13:01 snomone Call port 9: update_codecs for 36979480@pbx: adding codec GSM/8000 to available list 
Feb 17 00:13:01 snomone Call port 9: update_codecs for 36979480@pbx: codec_preference size 6, available codecs size 6 
Feb 17 00:13:01 snomone Play audio_moh/noise.wav, caching true 
Feb 17 00:13:01 snomone call port 8: state code from 0 to 183 
Feb 17 00:13:01 snomone Call port 8: update_codecs for 2399213226@192_168_6_68: adding codec PCMU/8000 to available list 
Feb 17 00:13:01 snomone Call port 8: update_codecs for 2399213226@192_168_6_68: adding codec PCMA/8000 to available list 
Feb 17 00:13:01 snomone Call port 8: update_codecs for 2399213226@192_168_6_68: Other side does not support codec G722/8000 
Feb 17 00:13:01 snomone Call port 8: update_codecs for 2399213226@192_168_6_68: adding codec G726-32/8000 to available list 
Feb 17 00:13:01 snomone Call port 8: update_codecs for 2399213226@192_168_6_68: Other side does not support codec GSM/8000 
Feb 17 00:13:01 snomone Call port 8: update_codecs for 2399213226@192_168_6_68: codec_preference size 6, available codecs size 4 
Feb 17 00:13:01 snomone Call-leg 8: Codec PCMU/8000 is chosen for call id 2399213226@192_168_6_68 
Feb 17 00:13:03 snomone Set packet length to 20 
Feb 17 00:13:03 snomone Call-leg 9: Codec PCMA/8000 is chosen for call id 36979480@pbx 
Feb 17 00:13:03 snomone Call-leg 9: Sending RTP for 36979480@pbx to 217.0.0.5:9036, codec PCMA/8000 
Feb 17 00:13:03 snomone call port 8: state code from 183 to 183 
Feb 17 00:13:03 snomone Last message repeated 2 times 
Feb 17 00:13:03 snomone 2399213226@192_168_6_68: RTP pass-through mode 
Feb 17 00:13:03 snomone 36979480@pbx: RTP pass-through mode 
Feb 17 00:13:03 snomone Call port 9: Different Codecs (local PCMU/8000, remote PCMA/8000), callid 2399213226@192_168_6_68, falling back to transcoding 
Feb 17 00:13:03 snomone Set packet length to 20 
Feb 17 00:13:03 snomone Determine pass-through mode after receiving response 
Feb 17 00:13:03 snomone 36979480@pbx: RTP pass-through mode 
Feb 17 00:13:03 snomone call port 9: state code from 100 to 200 
Feb 17 00:13:03 snomone Call port 9: Different Codecs (local PCMU/8000, remote PCMA/8000), callid 2399213226@192_168_6_68, falling back to transcoding 
Feb 17 00:13:03 snomone call port 8: state code from 183 to 200 
Feb 17 00:13:03 snomone 36979480@pbx: RTP pass-through mode 
Feb 17 00:13:03 snomone Call port 9: Different Codecs (local PCMU/8000, remote PCMA/8000), callid 2399213226@192_168_6_68, falling back to transcoding 
Feb 17 00:13:11 snomone call port 9: state code from 200 to 486

und zum Vergleich des snom 300:

Feb 17 00:18:45 snomone Dictionary: Item dom_sip_trunks.htm outbound en not found 
Feb 17 00:22:23 snomone Call limit reached. Call ports 1, g729 0 
Feb 17 00:22:23 snomone Set packet length to 20 
Feb 17 00:22:23 snomone Call-leg 10: Sending RTP for 512014a9a7f4-8w6q7ye2m462 to 192.168.6.69:63156, codec not set yet 
Feb 17 00:22:23 snomone Play audio_moh/noise.wav, caching true 
Feb 17 00:22:23 snomone Call port 10: set_codecs for 512014a9a7f4-8w6q7ye2m462 codecs "", codec_preference count 6 
Feb 17 00:22:23 snomone Call port 11: set_codecs for 5c1fcda6@pbx codecs "", codec_preference count 6 
Feb 17 00:22:23 snomone call port 11: state code from 0 to 100 
Feb 17 00:22:23 snomone Call port 11: update_codecs for 5c1fcda6@pbx: adding codec PCMU/8000 to available list 
Feb 17 00:22:23 snomone Call port 11: update_codecs for 5c1fcda6@pbx: adding codec PCMA/8000 to available list 
Feb 17 00:22:23 snomone Call port 11: update_codecs for 5c1fcda6@pbx: adding codec G722/8000 to available list 
Feb 17 00:22:23 snomone Call port 11: update_codecs for 5c1fcda6@pbx: adding codec G726-32/8000 to available list 
Feb 17 00:22:23 snomone Call port 11: update_codecs for 5c1fcda6@pbx: adding codec GSM/8000 to available list 
Feb 17 00:22:23 snomone Call port 11: update_codecs for 5c1fcda6@pbx: codec_preference size 6, available codecs size 6 
Feb 17 00:22:23 snomone call port 10: state code from 0 to 183 
Feb 17 00:22:23 snomone Set packet length to 20 
Feb 17 00:22:23 snomone Call port 10: update_codecs for 512014a9a7f4-8w6q7ye2m462: adding codec PCMU/8000 to available list 
Feb 17 00:22:23 snomone Call port 10: update_codecs for 512014a9a7f4-8w6q7ye2m462: adding codec PCMA/8000 to available list 
Feb 17 00:22:23 snomone Call port 10: update_codecs for 512014a9a7f4-8w6q7ye2m462: adding codec G722/8000 to available list 
Feb 17 00:22:23 snomone Call port 10: update_codecs for 512014a9a7f4-8w6q7ye2m462: adding codec G726-32/8000 to available list 
Feb 17 00:22:23 snomone Call port 10: update_codecs for 512014a9a7f4-8w6q7ye2m462: adding codec GSM/8000 to available list 
Feb 17 00:22:23 snomone Call port 10: update_codecs for 512014a9a7f4-8w6q7ye2m462: codec_preference size 6, available codecs size 6 
Feb 17 00:22:23 snomone Call-leg 10: Codec PCMU/8000 is chosen for call id 512014a9a7f4-8w6q7ye2m462 
Feb 17 00:22:25 snomone Set packet length to 20 
Feb 17 00:22:25 snomone Call-leg 11: Codec PCMA/8000 is chosen for call id 5c1fcda6@pbx 
Feb 17 00:22:25 snomone Call-leg 11: Sending RTP for 5c1fcda6@pbx to 217.0.0.3:14450, codec PCMA/8000 
Feb 17 00:22:25 snomone call port 10: state code from 183 to 183 
Feb 17 00:22:25 snomone Last message repeated 2 times 
Feb 17 00:22:25 snomone 512014a9a7f4-8w6q7ye2m462: RTP pass-through mode 
Feb 17 00:22:25 snomone 5c1fcda6@pbx: RTP pass-through mode 
Feb 17 00:22:25 snomone Call port 11: Different Codecs (local PCMU/8000, remote PCMA/8000), callid 512014a9a7f4-8w6q7ye2m462, falling back to transcoding 
Feb 17 00:22:25 snomone Set packet length to 20 
Feb 17 00:22:25 snomone Determine pass-through mode after receiving response 
Feb 17 00:22:25 snomone 5c1fcda6@pbx: RTP pass-through mode 
Feb 17 00:22:25 snomone call port 11: state code from 100 to 200 
Feb 17 00:22:25 snomone Call port 11: Different Codecs (local PCMU/8000, remote PCMA/8000), callid 512014a9a7f4-8w6q7ye2m462, falling back to transcoding 
Feb 17 00:22:25 snomone call port 10: state code from 183 to 200 
Feb 17 00:22:25 snomone 5c1fcda6@pbx: RTP pass-through mode 
Feb 17 00:22:25 snomone Call port 11: Different Codecs (local PCMU/8000, remote PCMA/8000), callid 512014a9a7f4-8w6q7ye2m462, falling back to transcoding 
Feb 17 00:22:29 snomone call port 11: state code from 200 to 486

Bronko · February 19, 2013

Und ein weiterer Nachtrag: Den SIP trunk (DTAG) direkt auf dem C475 IP eingerichtet führt zu normalen Verhalten...

Gruß

Vodia PBX · February 19, 2013

Hmm. Vielleicht kommt das C475 nicht mit dem Wechsel von ulaw zu alaw klar. Es gibt ein Setting "Lock codec during conversation" in den globalen Settings (Settings/SIP/Audio), das würde ich mal einschalten.

Bronko · February 19, 2013

!TOP! Das war's... Sind Nachteile zu erwarten?

Vielen Dank und viele Grüße.

PS: Warum dies unvermittelt auftrat, ist mir allerdings nicht klar.

Vodia PBX · February 19, 2013

Transcoding ist grundsätzlich nichts gutes. Wenn aber von ulaw nach alaw übersetzt wird, gehen keine Informationen verloren und es ist auch nicht besondern CPU-intensiv. Also alles okay.

Bronko · February 20, 2013

Der Vollständigkeit halber den media debug am nun wieder funktionierendem C475 IP:

Feb 20 12:48:52 snomone Call limit reached. Call ports 1, g729 0 
Feb 20 12:48:52 snomone Call-leg 193: Sending RTP for 1579004713@192_168_6_68 to 192.168.6.68:5004, codec not set yet 
Feb 20 12:48:52 snomone Call port 193: set_codecs for 1579004713@192_168_6_68 codecs "", codec_preference count 6 
Feb 20 12:48:52 snomone Call port 194: set_codecs for ea822fdf@pbx codecs "", codec_preference count 6 
Feb 20 12:48:52 snomone call port 194: state code from 0 to 100 
Feb 20 12:48:52 snomone Call port 194: update_codecs for ea822fdf@pbx: adding codec PCMU/8000 to available list 
Feb 20 12:48:52 snomone Call port 194: update_codecs for ea822fdf@pbx: adding codec PCMA/8000 to available list 
Feb 20 12:48:52 snomone Call port 194: update_codecs for ea822fdf@pbx: adding codec G722/8000 to available list 
Feb 20 12:48:52 snomone Call port 194: update_codecs for ea822fdf@pbx: adding codec G726-32/8000 to available list 
Feb 20 12:48:52 snomone Call port 194: update_codecs for ea822fdf@pbx: adding codec GSM/8000 to available list 
Feb 20 12:48:52 snomone Call port 194: update_codecs for ea822fdf@pbx: codec_preference size 6, available codecs size 6 
Feb 20 12:48:52 snomone Play audio_moh/noise.wav, caching true 
Feb 20 12:48:52 snomone call port 193: state code from 0 to 183 
Feb 20 12:48:52 snomone Call port 193: update_codecs for 1579004713@192_168_6_68: adding codec PCMU/8000 to available list 
Feb 20 12:48:52 snomone Call port 193: update_codecs for 1579004713@192_168_6_68: adding codec PCMA/8000 to available list 
Feb 20 12:48:52 snomone Call port 193: update_codecs for 1579004713@192_168_6_68: Other side does not support codec G722/8000 
Feb 20 12:48:52 snomone Call port 193: update_codecs for 1579004713@192_168_6_68: adding codec G726-32/8000 to available list 
Feb 20 12:48:52 snomone Call port 193: update_codecs for 1579004713@192_168_6_68: Other side does not support codec GSM/8000 
Feb 20 12:48:52 snomone Call port 193: update_codecs for 1579004713@192_168_6_68: codec_preference size 6, available codecs size 4 
Feb 20 12:48:52 snomone Call-leg 193: Codec PCMU/8000 is chosen for call id 1579004713@192_168_6_68 
Feb 20 12:48:54 snomone Set packet length to 20 
Feb 20 12:48:54 snomone Call-leg 194: Codec PCMA/8000 is chosen for call id ea822fdf@pbx 
Feb 20 12:48:54 snomone Call-leg 194: Sending RTP for ea822fdf@pbx to 217.0.0.2:13982, codec PCMA/8000 
Feb 20 12:48:54 snomone call port 193: state code from 183 to 183 
Feb 20 12:48:54 snomone Last message repeated 2 times 
Feb 20 12:48:54 snomone 1579004713@192_168_6_68: RTP pass-through mode 
Feb 20 12:48:54 snomone ea822fdf@pbx: RTP pass-through mode 
Feb 20 12:48:54 snomone Call port 194: Different Codecs (local PCMU/8000, remote PCMA/8000), callid 1579004713@192_168_6_68, falling back to transcoding 
Feb 20 12:48:54 snomone Call port 193: Different Codecs (local PCMA/8000, remote PCMU/8000), callid ea822fdf@pbx, falling back to transcoding 
Feb 20 12:48:54 snomone Set packet length to 20 
Feb 20 12:48:54 snomone Determine pass-through mode after receiving response 
Feb 20 12:48:54 snomone ea822fdf@pbx: RTP pass-through mode 
Feb 20 12:48:54 snomone 1579004713@192_168_6_68: RTP pass-through mode 
Feb 20 12:48:54 snomone Call port 193: Different Codecs (local PCMA/8000, remote PCMU/8000), callid ea822fdf@pbx, falling back to transcoding 
Feb 20 12:48:54 snomone call port 194: state code from 100 to 200 
Feb 20 12:48:54 snomone call port 193: state code from 183 to 200 
Feb 20 12:48:54 snomone 1579004713@192_168_6_68: RTP pass-through mode 
Feb 20 12:48:54 snomone Call port 194: Different Codecs (local PCMU/8000, remote PCMA/8000), callid 1579004713@192_168_6_68, falling back to transcoding 
Feb 20 12:48:54 snomone Call port 193: Different Codecs (local PCMA/8000, remote PCMU/8000), callid ea822fdf@pbx, falling back to transcoding 
Feb 20 12:48:59 snomone call port 194: state code from 200 to 486

Gibt es Anmerkungen zur Verständlichkeit?

Vodia PBX · February 20, 2013

Ja jetzt kann man schön sehen dass auf beiden Seiten transcoding eingeschaltet wird.

Sign In

RTP da, aber nicht hörbar, unter Umständen

Recommended Posts

Bronko

Link to comment

Share on other sites

Vodia PBX

Link to comment

Share on other sites

Bronko

Link to comment

Share on other sites

Bronko

Link to comment

Share on other sites

Bronko

Link to comment

Share on other sites

Vodia PBX

Link to comment

Share on other sites

Bronko

Link to comment

Share on other sites

Vodia PBX

Link to comment

Share on other sites

Bronko

Link to comment

Share on other sites

Vodia PBX

Link to comment

Share on other sites

Join the conversation

Browse

Activity