D80 Phone configuration Asterisk 13.13.1

Good Day!

We bought a couple of the new D80 phones to test. we can upgrade the firmware through DPMA, however, the phone is not successful completing a SIP registration. We are using CHAN SIP, not PJSIP. Config for the extension is below.

Thanks in advance for any help…Stan

We have upgraded to the latest DPMA. See below.

voip-abi*CLI> digium_phones show version
Digium Phone Module for Asterisk Version 13.0_3.4.1

We have also upgraded the firmware on the D80 to 1_4_1_D80_firmware.eff.

As the title states, we are on Asterisk 13.13.1.

SIP.CONF

[general]
bindaddr=xxx.xxx.xxx.xxx
bindport=5060
udpenable=yes
tcpenable=yes
preferred_codec_only=yes
disallow=all
allow=ulaw
sipdebug=yes
accept_outofcall_messages=yes
auth_messages_request=no
outofcall_message_context=dpma_message_context
callcounter=yes

mus-sip
context=mus
type=friend
host=dynamic
disallow=all
allow=ulaw
dtmfmode=auto
;qualify=yes
callevents=yes
;accept_outofcall_messages=yes
;auth_messages_request=no
;outofcall_message_context=dpma_message_context
allowsubscribe=yes
callcounter=yes
notifyringing=yes
notifyhold=yes
callevents=yes
limitonpeer=yes

StanMcHann
secret=xxxxxx
callerid=8946
mailbox = 8946@vm-mus

Extensions.conf

exten => StanMcHann,hint,SIP/StanMcHann
exten => 8946,1,Dial(SIP/StanMcHann,20)
same => n,VoiceMail(8946@vm-mus,u)
exten => 89469,1,VoiceMailMain(8946@vm-mus)

res_digium_phone.conf

[general]
server_uuid=Milasterisk4400
mdns_address=xxx.xxx.xxx.xxx
mdns_port=5060
mdns_transport=udp
service_name=Milsoft Digium Phones Config Server
service_discovery_enabled=yes
config_auth=mac

[network1]
type=network
alias=MilsoftAterisk
cidr=0.0.0.0/0
registration_address=xxx.xxx.xxx.xxx
registration_port=5060
transport=udp
public_firmware_url_prefix=http://dphone.dl.digium.com/firmware/asterisk/
file_url_prefix=http://xxx.xxx.xxx.xxx/digium_phones
ntp_server=0.digium.pool.ntp.org
udp_ka_interval=60

[StanMcHann]
;phone network and firmware
type=phone
network=network1
mac=000FD30AD930
;mac=000FD30ACC25
firmware=firmware-D80_1_4_1
;firmware=firmware-D65_2_2
active_locale=en_US
ntp_resync=86400
lan_port_mode=auto
pc_port_mode=auto
enable_check_sync=yes
;phone features
parking_exten=800
parking_transfer_type=blind
show_call_parking=yes
ringtone=fancytone
active_ringtone=GuitarStrum
alert=alert-fancytone
multicastpage=everyone
record_own_calls=yes
can_forward_calls=yes
show_call_log=yes
display_mc_notification=no
send_to_vm=yes
lock_preferences=no
;audio and headset
ringer_volume=5
speaker_volume=5
handset_volume=5
headset_volume=5
reset_call_volume=no
call_waiting_tone=yes
headset_answer=no
ehs=plantronics
timezone=America/Chicago
line=StanMcHann
full_name=StanMcHann
;phone display, xml
;blf_contact_group=EA Support
contact=Milsoftcontacts.xml
small_clock=yes
wallpaper_file=PhoneBackground.png
brightness=5
contrast=5
dim_backlight=yes
backlight_timeout=30
backlight_dim_level=2

[StanMcHann]
type=line
digit_map=[0-8]xxxx|911|9411|9611|9011xxx.T3|91xxxxxxxxxx|9[2-9]xxxxxx|*xxx.T3
line_label=StanMcHann
mailbox=8946@vm-mus
outboundproxy_address=xxx.xxx.xxx.xxx
outboundproxy_port=5060
transport=udp
reregistration_timeout=300
registration_retry_interval=25
registration_max_retries=5

[firmware-D80_1_4_1]
type=firmware
model=D80
version=1_4_1
file=1_4_1_D80_firmware.eff
public_firmware=yes

What does chan_sip’s debug say? Does the phone attempt to register?

chan_sip moved on to extended support and it’s not something we deal with on a daily basis within our various development teams.

Do you experience the same problem when using chan_pjsip?