vermehrt SIP Fehler 500 Internal Server Error auf Telekom Sip-Trunk

1 year ago

hallo,

 

hier ein ausschnitt unseres SWYX Server jetzt Enreach genennt, heute morgen ist der fehler 2 mal aufgetreten innerhalb von 2 min. bei unterschiedlichen zielen an unterschiedlichen durchwahlen.

 

26 11:39:52.298 000a34 Inf2 SIP 02642088 00000000 DnsResult.cxx:199 () Whitelisting _sip._tcp.reg.sip-trunk.telekom.de(33): h-ipr-a04.edns.t-ipnet.de:5060
26 11:39:52.298 000a34 Inf2 SIP 02642088 00000000 RRVip.cxx:128 () updating an existing vip: h-ipr-a04.edns.t-ipnet.de:5060 with h-ipr-a04.edns.t-ipnet.de:5060
26 11:39:52.298 000a34 Inf2 SIP 02642088 00000000 DnsResult.cxx:199 () Whitelisting reg.sip-trunk.telekom.de(1): 217.0.129.182
26 11:39:52.298 000a34 Inf2 SIP 02642088 00000000 RRVip.cxx:128 () updating an existing vip: 217.0.129.182 with 217.0.129.182
26 11:39:52.298 000a34 Inf2 SIP 02642088 00000000 TransactionState.cxx:2155 () Send to default TU: SipResp: 183 tid=3d4d75249619a701 cseq=INVITE contact=IDPNRZX9c4qbOBwFpMVO0IcfHA434ux/kEyEuU1cRyaPdHbiD6O7485bfaghE8zswTIX@th1 / 3 from(wire)
26 11:39:52.298 000a34 Inf2 SIP 02642088 00000000 SipStack.cxx:516 () RECV: SipResp: 183 tid=3d4d75249619a701 cseq=INVITE contact=IDPNRZX9c4qbOBwFpMVO0IcfHA434ux/kEyEuU1cRyaPdHbiD6O7485bfaghE8zswTIX@th1 / 3 from(wire)


~SIP/2.0 500 Server Internal Error
~Via: SIP/2.0/TCP 192.168.2.200:65002;rport=36975;received=87.139.XXX.XXX;branch=z9hG4bK-d8754z-3d4d75249619a701-1---d8754z-
~Contact: <sip:IDPNRZX9c4qbOBwFpMVO0IcfHA434ux/kEyEuU1cRyaPdHbiD6O7485bfaghE8zswTIX@th1>
~To: <sip:+49171477XXXX@sip-trunk.telekom.de;user=phone>;tag=48dbb642
~From: "Robert" <sip:+49171350XXXX@sip-trunk.telekom.de;user=phone>;tag=a16ab514
~Call-ID: ZDM4ZWY5ZDFjY2I4NmJkZGMzODY0NzJjYWVkNTRmMjY.
~CSeq: 3 INVITE
~Allow: ACK, BYE, CANCEL, INVITE, OPTIONS, REGISTER
~Server: SIP/2.0
~Reason: TSSI;cause=0
~Content-Length: 0

187

9

    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...
    Loading...

    This could help you too

    Solved

    in  

    3319

    0

    3

    Solved

    in  

    924

    2

    5

    Solved

    in  

    387

    0

    2

    Solved

    in  

    1561

    0

    6