LCOS-Watchdog (10.20) beim Wählen

Forum zu LANCOM Systems VoIP Router/Gateways und zur LANCOM VoIP Option

Moderator: Lancom-Systems Moderatoren

Antworten
Benutzeravatar
Björn
Beiträge: 65
Registriert: 14 Sep 2010, 12:32
Kontaktdaten:

LCOS-Watchdog (10.20) beim Wählen

Beitrag von Björn »

Hallo zusammen,

ich stehe im Moment etwas auf dem Schlauch.
Seitdem ich ein Backup in meine Telefonanlage zurückgespielt habe, harmoniert sie nicht mehr wirklich mit dem VCM
und bringt aktuell die Büchse zum Absturz. (Wenn ich raus rufe oder angerufen werde)

Die 10.12 stürzt zwar nicht ab, Gespräche kommen aber trotzdem nicht zustande. (Verbidnung läuft über Netz-Netz VPN)
(MEDIA sagt, es könne keine QOS Bandbreite in der FW reservieren "failed, effective rate (tx/rx) 80/80 kBit/s")

Bei der 10.20 gibts einen Watchdog (SSH):

Code: Alles auswählen

[SIP-Connection] 2018/10/28 01:06:13,860 [SIP TLS Transport (10.30.0.148:48232)]: VCM user agent server proceeds with non-REGISTER request
[Callmanager] 2018/10/28 01:06:13,860 [SIP-URI]: URI COMPARISON
[Callmanager] 2018/10/28 01:06:13,860 [Sip-UA] : -----[ INVITE INDICATION, call-id=0099a4510297dc1b0a52fa4622d53234@10.20.0.1, Configured CLIR=no
[Callmanager] 2018/10/28 01:06:13,860 [Sip-UA] : - info       : privacy detected, type is:
[Callmanager] 2018/10/28 01:06:13,860 [Sip-UA] : FindBinding  --  ContactValid: yes,  HasContact: yes,  FromValid: yes
[Callmanager] 2018/10/28 01:06:13,860 [Sip-UA] : FindBinding  --  OrigName: "xxxx", OrigDomain: "10.20.0.1", ContactName: "xxxx"
[Callmanager] 2018/10/28 01:06:13,860 [Registration Registry]: Registration Registry: FindRegistration  --  Name: "xxxx",  Domain: "xxxx.zz"
[Callmanager] 2018/10/28 01:06:13,860 [Registration Registry]: FindRegistration  -->  It's a match!
[Callmanager] 2018/10/28 01:06:13,860 [SIP Registration]: xxxx@xxxx.zz: SIP Registration: FindBinding  --  Find Uri: <sip:xxxx@10.30.0.148:5061;transport=TLS>
[Callmanager] 2018/10/28 01:06:13,860 [SIP Registration]: xxxx@xxxx.zz: SIP Registration: FindBinding  --  isTrunkUser: no,  Binding Uri: <sip:xxxx@10.30.0.148:5061;transport=TLS>
[Callmanager] 2018/10/28 01:06:13,860 [SIP-URI]: URI COMPARISON
[Callmanager] 2018/10/28 01:06:13,860 [CALL-INFO] : Construct CallInfo(05ee3760) A  --  m_mediaStub: 05ee3c88
[Callmanager] 2018/10/28 01:06:13,860 [VCM] : Construct CmCall(08124380)
[Callmanager] 2018/10/28 01:06:13,862 [SIP-CALL] : cSipCall::SetToTag  NewTag:1120226870--1366368792, m_ToTag:, m_FromTag:as05dbe8ce
[Callmanager] 2018/10/28 01:06:13,862 [SIP-CALL] : cSipCall constructor (type 1) --- call=05ee3760, pSipMessage=0810c800, MediaStub=05ee3c88, SIP call-id=0099a4510297dc1b0a52fa4622d53234@10.20.0.1,  Cld: 16
[Callmanager] 2018/10/28 01:06:13,862 [Sip-UA] : - info       : pCall-Dst: 16@10.20.0.1, pCall-Src: xxxx@10.20.0.1
[Callmanager] 2018/10/28 01:06:13,862 [Sip-UA] : - info       : Generated new call, call-id=43, SIP call=05ee3760
[Callmanager] 2018/10/28 01:06:13,862 [Sip-UA] : - info       : Generate trying response
[SIP-Packet] 2018/10/28 01:06:13,862 [Packet]:
Sending datagram (454 Bytes) from 10.20.0.1:5061 to 10.30.0.148:48232 using TLS (RtgTag 0):
[Callmanager] 2018/10/28 01:06:13,862 [Sip-UA] : - info       : user login/auth needed
[Callmanager] 2018/10/28 01:06:13,862 [SIP-CALL] : cSipCall::UpdateFromTag  2  Set FromTag  --  m_FromTag: as05dbe8ce,  m_ToTag: 1120226870--1366368792,  message.From.GetTag: as05dbe8ce
[Callmanager] 2018/10/28 01:06:13,862 [SIP]: SipMsgMakeCommonPart - Uri Type: sip
[SIP-Packet] 2018/10/28 01:06:13,862 [Packet]:
[SIP-Connection] 2018/10/28 01:06:13,863 [SIP Transceiver (10.30.0.148:48232)]: Triggered processing of 2 queued outbound message(s)
[SIP-Connection] 2018/10/28 01:06:13,864 [SIP Transceiver (10.30.0.148:48232)]: Transmitted 454/454 characters
[SIP-Connection] 2018/10/28 01:06:13,864 [SIP Transceiver (10.30.0.148:48232)]: Transmitted 615/615 characters
[SIP-Connection] 2018/10/28 01:06:13,874 [SIP Transceiver (10.30.0.148:48232)]: Triggered processing of 0 queued outbound message(s)
[SIP-Connection] 2018/10/28 01:06:13,935 [SIP TLS Transport (10.30.0.148:48232)]: Processing new inbound SIP message
[SIP-Packet] 2018/10/28 01:06:13,935 [Packet]:
Receiving datagram (391 Bytes) at 10.20.0.1:5061 from 10.30.0.148:48232 using TLS (RtgTag 0):
[SIP-Connection] 2018/10/28 01:06:13,936 [SIP TLS Transport (10.30.0.148:48232)]: VCM user agent server proceeds with non-REGISTER request
[Callmanager] 2018/10/28 01:06:13,936 [Sip-UA] : - info       : cSipUas -- RequestHndl --> Call found!
[Callmanager] 2018/10/28 01:06:13,936 [SIP-CALL] : -----[ ACK INDICATION
[Callmanager] 2018/10/28 01:06:13,936 [SIP-CALL] : - info       : call-id=43
[Callmanager] 2018/10/28 01:06:13,936 [SIP-CALL] : -----[ call is not connected  --  start aging
#### -> Watchdog  Task name = Voice-Media-Receiver  Type=PPC: DSI (protection error on load access @0x0)
Code=0x00000002 Thread=093d46d0 Task=093d46c0 Nest=0x00000000
So langsam gehen mir auch die Ideen aus, was man noch ändern / debuggen könnte. :G) Die Aushandlung sieht gut aus, alles ist registriert - scheint echt irgendwie am QOS zu hängen.

Dinge die ich probiert habe:
- Neustart
- Andere Firmware
- Firewall abschalten
- "Interne Dienste über Router schicken" An / Aus
- QOS Fragmentierung an / aus gestellt
- HardwareNAT aus kontrolliert
- Hardware getauscht

Gruß Björn

Code: Alles auswählen

Content of table: /Status/Voice-Call-Manager/Users

Index Number/Name Type     Ifc  Address                                      Display-Name Domain  Local-register Remote-register CFU-Active CFU-Target CFNR-Active CFNR-Target CFNR-Timeout CFB-Active CFB-Target Access-from-WAN Expires
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1     xxxxx60     SIP-User none <sip:xxxxx60@10.30.0.148:5061;transport=TLS>              xxxxx.zz Registered     Not-possible    No                    No                      0            No                    Vpn             60     
2     xxxxx62     SIP-User none <sip:xxxxx62@10.30.0.148:5061;transport=TLS>              xxxxx.zz Registered     Not-possible    No                    No                      0            No                    Vpn             60     
3     xxxxx6      SIP-User none <sip:xxxxx6@10.30.0.148:5061;transport=TLS>               xxxxx.zz Registered     Not-possible    No                    No                      0            No                    Vpn             60     

Content of table: /Status/Voice-Call-Manager/Lines

Index Name          Domain                      Remote-IP-Address Number Type         Reg-status   Reg-state Line-status Quality    
------------------------------------------------------------------------------------------------------------------------------------
1     UNITYMEDIA_62 ssl35.telefon.unitymedia.de 80.69.108.85             SIP-Provider Registered   Idle      Ready       Unspecified
2     UNITYMEDIA_60 ssl35.telefon.unitymedia.de 80.69.108.85             SIP-Provider Registered   Idle      Ready       Unspecified
3     XXXXXXXXXX_X6 10.1.1.91                   10.1.1.91                SIP-Provider Registered   Idle      Ready       Unspecified
4     ISDN          isdn                        not applicable           ISDN         Not-possible Idle      Ready       Unspecified
Antworten