search for: 2636146e0

...ue. here i have some debug logs. I see lot of requests from asterisk to sipgate.de, which 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/UD...

...xecuting [s at app-announcement-1:5] Playback("PJSIP/pjsip_sipgate-00000003", "custom/araz01&custom/07-polly,noanswer") in new stack -- <PJSIP/pjsip_sipgate-00000003> Playing 'custom/araz01.alaw' (language 'en') -- Contact pjsip_sipgate/sip:2636146e0 at sipgate.de:5060 is now Reachable. RTT: 493.094 msec == Endpoint pjsip_sipgate is now Reachable -- <PJSIP/pjsip_sipgate-00000003> Playing 'custom/07-polly.slin' (language 'en') -- Contact pjsip_sipgate/sip:2636146e0 at sipgate.de:5060 is now Unreachable. RT...

...don't see anything in asterisk verbose mode). Sending a pjsip unregister results in the following messages: [2016-10-15 10:03:22] WARNING[10162]: res_pjsip_outbound_registration.c:761 schedule_retry: No response received from 'sip:sipgate.de:5060' on registration attempt to 'sip:2636146e0 at sipgate.de:5060', retrying in '60' -- Contact pjsip_sipgate/sip:2636146e0 at sipgate.de:5060 is now Reachable. RTT: 434.393 msec == Endpoint pjsip_sipgate is now Reachable so it is somewhat clear, why i get a busy, because the endpoint is not reachable. But WHY is the end...