Hi
We think we need some help with our Asterisk server.
We are using Asterisk 13.9.1 with Pjproject 2.5.5 on Ubuntu 16.04.
Server is located in the cloud, and test clients are on the local WiFi, behind the same router. We are, mostly successfully, making TLS calls between two clients.
However, we have been experiencing some problems, and we think we have traced their root to the specific invite message. It might be a configuration issue, and we would appreciate any help with resolving it.
We believe that source of the problems is "From" line in INVITE message forwarded to the callee, that contains "sip" , instead of "sips", address. In further course of the call, it likely propagates to "To" headers, and eventually ends up in "Contact" header, which causes call to end due "SIPS Required" error.
This is the INVITE message that is received by asterisk from the caller:
[Oct 18 15:47:13] VERBOSE[21198] res_pjsip_logger.c: <--- Received SIP request (1630 bytes) from TLS:217.169.223.250:50986 --->INVITE sips:zz2867@xxxxxxxxxxxxxxx:5060 SIP/2.0 Via: SIP/2.0/TLS 217.169.223.250:50986;rport;branch=z9hG4bKPjfc4612c5-1684- 465d-bc4e-3efe626e3f31;alias Max-Forwards: 70From: sips:yy0206@xxxxxxxxxxxxxxx;tag=382ff707-70d7-43e5-ad8c- ca3319e3d124 To: sips:zz2867@xxxxxxxxxxxxxxxContact: <sips:yy0206@217.169.223.250:50986;transport=TLS;ob> Call-ID: a62d94a3-17ba-4fd5-acb7-c3e6e9514f5a CSeq: 12748 INVITEAllow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONSSupported: replaces, 100rel, timer, norefersubSession-Expires: 1800Min-SE: 90Authorization: ******************************************************* Content-Type: application/sdpContent-Length: 650v=0o=- 3717323230 3717323230 IN IP4 192.168.15.207s=pjmediab=AS:30t=0 0m=audio 4000 RTP/SAVP 3 96c=IN IP4 192.168.15.207b=TIAS:13200a=rtcp:4001 IN IP4 192.168.15.207a=sendrecva=rtpmap:3 GSM/8000a=rtpmap:96 telephone-event/8000a=fmtp:96 0-16a=crypto:1 ******************************************************* a=crypto:2 ******************************************************* a=crypto:3 ******************************************************* a=crypto:4 *******************************************************
This is the INVITE message forwarded to the callee (note From line):
[Oct 18 15:47:14] VERBOSE[21718] res_pjsip_logger.c: <--- Transmitting SIP request (1048 bytes) to TLS:217.169.223.250:43122 --->INVITE sips:zz2867@217.169.223.250:43122;transport=TLS;ob SIP/2.0 Via: SIP/2.0/TLS xxx.xxx.xxx.xxx:5060;rport;branch=z9hG4bKPj76d12694-8316- 42c6-9c16-737dc1ce9c5d;alias From: <sip:yy0206@172.31.1.100>;tag=a2953819-10ab-4673-ad5f- ba31bf3d9d60 To: <sips:zz2867@217.169.223.250;ob> Contact: <sips:asterisk@xxxxxxxxxxxxxxx:5060;transport=TLS> Call-ID: 6c9e38cb-3515-421a-ae00-40636f1912ac CSeq: 31285 INVITEAllow: OPTIONS, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, MESSAGE, REGISTER, REFERSupported: timer, replaces, norefersubSession-Expires: 1800Min-SE: 90Max-Forwards: 70User-Agent: VoIPServerBetaContent-Type: application/sdpContent-Length: 339v=0o=- 54900247 54900247 IN IP4 172.31.1.100s=Asteriskc=IN IP4 xxx.xxx.xxx.xxxt=0 0m=audio 6016 RTP/SAVP 3 0 101a=crypto:1 ******************************************************* a=rtpmap:3 GSM/8000a=rtpmap:0 PCMU/8000a=rtpmap:101 telephone-event/8000a=fmtp:101 0-16a=ptime:20a=maxptime:150a=sendrecv
There are two defined transports:
[transport-udp]type=transportbind=0.0.0.0:5060protocol=udp
and
[transport-tls]type=transportbind=0.0.0.0:5060protocol=tlscert_file=***priv_key_file=***password=***cipher=***method=tlsv1local_net=172.31.1.0/255.255.255.0 external_media_address=xxx.xxx.xxx.xxx external_signaling_address=xxx.xxx.xxx.xxx external_signaling_port=5060
(We are aware that default port for TLS is 5061. 5060 also work, and binding to 5061 didn't help. Nether did removing UDP transport.)
All users have the same configuration. This is the example:
Endpoint: yy0206 Not in use 0 of infInAuth: yy0206/yy0206Aor: yy0206 1Contact: yy0206/sips:yy0206@217.169.223.250 3d00261b2b Unknown nanIdentify: yy0206/yy0206Match: 127.0.0.1/32ParameterName : ParameterValue========================================================= 100rel : noaccountcode :aggregate_mwi : trueallow : (gsm|ulaw)allow_subscribe : trueallow_transfer : trueaors : yy0206auth : yy0206bind_rtp_to_media_address : falsecall_group :callerid : <unknown>callerid_privacy : allowed_not_screenedcallerid_tag :connected_line_method : invitecontext : voip_testcos_audio : 0cos_video : 0device_state_busy_at : 0direct_media : falsedirect_media_glare_mitigation : none direct_media_method : invitedisable_direct_media_on_nat : falsedtls_ca_file :dtls_ca_path :dtls_cert_file :dtls_cipher :dtls_fingerprint : XXXdtls_private_key :dtls_rekey : 0dtls_setup : activedtls_verify : Nodtmf_mode : rfc4733fax_detect : falseforce_avp : falseforce_rport : truefrom_domain :from_user :g726_non_standard : falseice_support : falseidentify_by : usernameinband_progress : falselanguage :mailboxes :media_address :media_encryption : sdesmedia_encryption_optimistic : falsemedia_use_received_transport : falsemessage_context :moh_suggest : defaultmwi_from_user :mwi_subscribe_replaces_unsolicited : false named_call_group :named_pickup_group :one_touch_recording : falseoutbound_auth :outbound_proxy :pickup_group :record_off_feature : automixmonrecord_on_feature : automixmonrewrite_contact : falserpid_immediate : falsertp_engine : asteriskrtp_ipv6 : falsertp_keepalive : 0rtp_symmetric : truertp_timeout : 0rtp_timeout_hold : 0sdp_owner : -sdp_session : Asterisksend_diversion : truesend_pai : falsesend_rpid : falseset_var :srtp_tag_32 : falsesub_min_expiry : 0t38_udptl : falset38_udptl_ec : nonet38_udptl_ipv6 : falset38_udptl_maxdatagram : 0t38_udptl_nat : falsetimers : yestimers_min_se : 90timers_sess_expires : 1800tone_zone :tos_audio : 0tos_video : 0transport :trust_id_inbound : falsetrust_id_outbound : falseuse_avpf : falseuse_ptime : trueuser_eq_phone : falsevoicemail_extension :
We would very much appreciate any help with this issue.
Thank you.
Pozdrav/Best regards,
Mladen Mijatovic,
Technology Partnership.
_______________________________________________ Visit our blog: http://blog.pjsip.org pjsip mailing list pjsip@xxxxxxxxxxxxxxx http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org