Displaying 2 results from an estimated 2 matches for "c519528374e3101a61791cf5a0ad1aae".
2016 Oct 15
2
Registered successfully, but after a minute or so no SIP messages anymore
...ch are not answered. but communication is going fine in
both directions (otherwise registration would not be possible?):
<--- Received SIP request (1302 bytes) from UDP:217.10.79.9:5060 --->
INVITE sip:2636146e0 at 80.142.13.32:55060 SIP/2.0
Via: SIP/2.0/UDP
217.10.79.9;branch=z9hG4bK56ac.c519528374e3101a61791cf5a0ad1aae.0
Via: SIP/2.0/UDP
172.20.40.6;branch=z9hG4bK56ac.2ecd3532ae51c927dabcc6e27eaa4cbe.0
Via: SIP/2.0/UDP
217.10.68.137;branch=z9hG4bK56ac.73e224299594933979fdfb5b036e6563.0
Via: SIP/2.0/UDP 217.10.77.115:5060;branch=z9hG4bK7b31f031
Record-Route: <sip:217.10.79.9;lr;ftag=as02fa8fcc>
Record-Rout...
2016 Oct 15
3
Registered successfully, but after a minute or so no SIP messages anymore
ping times are fine as well:
[root at freepbx asterisk]# ping sipgate.de
PING sipgate.de (217.10.79.9) 56(84) bytes of data.
64 bytes from sipgate.de (217.10.79.9): icmp_seq=1 ttl=57 time=46.7 ms
64 bytes from sipgate.de (217.10.79.9): icmp_seq=2 ttl=57 time=46.4 ms
64 bytes from sipgate.de (217.10.79.9): icmp_seq=3 ttl=57 time=46.7 ms
64 bytes from sipgate.de (217.10.79.9): icmp_seq=4 ttl=57