Is there a way to detect, via cli or any other way, that Asterisk is in "graceful shutdown" mode, not accepting any new calls? Or to put the question a different way, how can I know that Asterisk has restarted again after the command "core restart graceful" in an automated way?
Best regards, Jan Blom
I just ran into what seems to be an issue on re-invites. I'm not sure if it's a bug or as designed, so I thought I'd ask the question.
Here's my setup: - Asterisk 18.104.22.168 - Phone A: Polycom ip331, only allowed to use ulaw, canreinvite=yes - Phone B: Polycom ip330, only allowed to use alaw, canreinvite=yes
Phone A calls the extension of phone B.
After the normal call setup asterisk tries the reinvite: - To phone B it sends an SDP which asks alaw and connection information of phone A - To phone A it sends and SDP with only the connection…
I've been given a SIP hard phone pre-configured to work with another party's BroadWorks system. I want to use my Asterisk system to connect to this SIP service rather than the handset I've been given. I have extracted the authentication details from the phone and have successfully registered Asterisk with the gateway (incoming calls work fine) using a line like this in sip.conf:
register => email@example.com:password:firstname.lastname@example.org/441000123123
Outgoing calls are proving to be more challenging. I have this so far:
 callerid="My Name" <441000123123> type=peer host=nnn.nnn.nnn.nnn auth=authuser realm=auth.realm fromuser= 441000123123 secret=password insecure=invite context=from-sip nat=yes qualify=no canreinvite=no allow=all
The main part I'm confused about is that…