Author Topic: SIP Routing Issue: Hangup reason='Proxy Authentication Required'  (Read 1430 times)

Vinsmoke Sanji

  • Newbie
  • *
  • Posts: 12
    • View Profile
I have a config issue which has me perplexed ( new Yate user). Any assistance from an experienced Yate admin would be greatly appreciated!!!
im trying to use Zadarma for SIP sever on Yate. Yate configuration based on tutorial
https://zadarma.com/en/support/instructions/yate/
When i ran Yate i received the result:
2018-08-09_08:26:00.518415 <ybts/8:CALL> Hangup reason='Proxy Authentication Required' [0x7fac24003d80]
2018-08-09_08:26:00.518480 <ybts/8:CALL> Destroyed [0x7fac24003d80]
Please tell me where i was wrong?

This is detailed:
--------------------------
------
2018-08-09_08:28:05.489081 <sip:CALL> SIP line 'outbound' logon success to 185.45.152.174:5060
2018-08-09_08:28:31.001555 <sip:ALL> Sending UDP keepalive to 185.45.152.174:5060 for 'outbound'
2018-08-09_08:28:31.176373 <bladerf/1:ALL> RX DC offset I set to 5 (from 5) reg=0x85 [0x7fac18000eb0]
2018-08-09_08:28:33.077124 <gsmtrx:INFO> ARFCN[0]: Slot 0. Receiver clipping 1.73261 dB (FN=502114) count=1 [0x7fac1802b400]
-----
Primitive: PhysicalInfo
Info: 0
Connection: 7

<PhysicalInfo>TA=0 TE=3.000 UpRSSI=1 TxPwr=33 DnRSSIdBm=-48 time=1533778113.093</PhysicalInfo>
-----
2018-08-09_08:28:33.343797 <ybts-signalling:INFO> Received [0x1fb06c0]
-----
Primitive: L3Message
Info: 0
Connection: 7
<MM>
  <SkipIndicator>0</SkipIndicator>
  <NSD>0</NSD>
  <Message type="CMServiceRequest">
    <CMServiceType>MO-call-establishment-or-PM-connection-establishment</CMServiceType>
    <CKSN>no-key/reserved</CKSN>
    <MSClassmark2>
      <RFPowerCapability>class4</RFPowerCapability>
      <RevisionLevel>GSM-phase2</RevisionLevel>
      <SSScreeningIndicator>ellipsis-notation-and-phase2-error-handling</SSScreeningIndicator>
      <Flags>ES-IND,E-GSM-and-R-GSM-support,MT-sms-point-to-point-capability,pseudo-sync-capability,A5/3-support,CMSP-support,CM3-support</Flags>
    </MSClassmark2>
    <MobileIdentity>
      <TMSI>007b0002</TMSI>
    </MobileIdentity>
  </Message>
</MM>
-----
2018-08-09_08:28:33.343887 <ybts-signalling:ALL> Added connection (0x7fac24001990,7) [0x1fb06c0]
2018-08-09_08:28:33.343923 <ybts-mm:ALL> Handling CMServiceRequest conn=7: ident=TMSI/007b0002 type=MO-call-establishment-or-PM-connection-establishment [0x1fb0aa0]
2018-08-09_08:28:33.343953 <ybts-mm:ALL> Added UE (0x7fac24001410) TMSI=007b0002 IMSI= [0x1fb0aa0]
2018-08-09_08:28:33.343984 <ybts-signalling:ALL> Connection 7 set UE (0x7fac24001410) TMSI=007b0002 IMSI= [0x7fac24001990]
2018-08-09_08:28:33.344033 <ybts-signalling:INFO> Sending [0x1fb06c0]
-----
Primitive: L3Message
Info: 0
Connection: 7

<MM>
  <Message type="CMServiceAccept"/>
</MM>
-----
2018-08-09_08:28:33.462712 <mbts:NOTE> proc 4208 DCCHDispatch.cpp:82:connDispatchRR: thread 139996392388352:  not handled GPRS suspension request on connection 7
2018-08-09_08:28:33.703210 <ybts-signalling:INFO> Received [0x1fb06c0]
-----
Primitive: PhysicalInfo
Info: 0
Connection: 7

<PhysicalInfo>TA=0 TE=0.000 UpRSSI=1 TxPwr=33 DnRSSIdBm=-48 time=1533778113.080</PhysicalInfo>
-----
2018-08-09_08:28:33.703452 <ybts-signalling:INFO> Received [0x1fb06c0]
-----
Primitive: L3Message
Info: 0
Connection: 7

<CC>
  <TID TIFlag="false">0</TID>
  <NSD>1</NSD>
  <Message type="Setup">
    <BearerCapability1>
      <ITC>speech</ITC>
      <TransferMode>circuit-mode</TransferMode>
      <CodingStandard>GSM</CodingStandard>
      <RadioChannelRequirement>FR-and-HR-speech-version1-supported/FR-speech-preferred</RadioChannelRequirement>
      <SpeechVersions>GSM-FR-speech-version3,GSM-FR-speech-version2,GSM-FR-speech-version1,GSM-HR-speech-version3,GSM-HR-speech-version1</SpeechVersions>
    </BearerCapability1>
    <CalledPartyBCDNumber nature="international" plan="isdn">84985889588</CalledPartyBCDNumber>
    <CCCapabilities>
      <Flags>DTMF</Flags>
      <MaxSupportedBearers>0</MaxSupportedBearers>
      <MaxSpeechBearers>0</MaxSpeechBearers>
    </CCCapabilities>
  </Message>
</CC>
-----
2018-08-09_08:28:33.703711 <ybts/10:CALL> Incoming address=TMSI007b0002 conn=7 [0x7fac24003d80]
2018-08-09_08:28:33.703827 <ybts-signalling:INFO> Sending [0x1fb06c0]
-----
Primitive: AllocMedia
Info: 0
Connection: 7
-----
2018-08-09_08:28:33.703904 <ybts/10:INFO> Call 'i0' changed state Null -> CallProceeding [0x7fac24003d80]
2018-08-09_08:28:33.704018 <ybts-signalling:INFO> Sending [0x1fb06c0]
-----
Primitive: L3Message
Info: 0
Connection: 7

<CC>
  <TID TIFlag="true">0</TID>
  <Message type="CallProceeding"/>
</CC>
-----
2018-08-09_08:28:33.704100 <ybts/10:INFO> Added call 'i0' [0x7fac24003d80]
2018-08-09_08:28:33.704136 <ybts-signalling:INFO> Sending [0x1fb06c0]
-----
Primitive: StartMedia
Info: 1
Connection: 7
-----
2018-08-09_08:28:33.704187 <ybts-signalling:ALL> Connection 7 waiting for traffic channel allocation mode=1 ... [0x1fb06c0]
2018-08-09_08:28:33.706880 <register:INFO> On account 'yateadmin' performing query 'INSERT INTO cdr VALUES(TIMESTAMP 'EPOCH' + INTERVAL '1533778113.704 s', 'ybts/10', 'TMSI007b0002', 'incoming', '1533775795-12', 'TMSI007b0002', '84985889588', INTERVAL '0.002 s', INTERVAL '0.000 s', INTERVAL '0.000 s', 'incoming', '', false)' expects results
2018-08-09_08:28:33.984488 <ybts-signalling:INFO> Received [0x1fb06c0]
-----
Primitive: PhysicalInfo
Info: 0
Connection: 7

<PhysicalInfo>TA=3 TE=0.000 UpRSSI=1 TxPwr=33 DnRSSIdBm=-48 time=1533778113.080</PhysicalInfo>
-----
2018-08-09_08:28:33.984631 <ybts-signalling:INFO> Received [0x1fb06c0]
-----
Primitive: MediaStarted
Info: 0
Connection: 7
-----
2018-08-09_08:28:33.984688 <ybts-signalling:ALL> Connection 7 traffic channel set succeeded mode=1 [0x1fb06c0]
2018-08-09_08:28:33.984728 <ybts/10:ALL> Got media started notification [0x7fac24003d80]
2018-08-09_08:28:33.985004 <INFO> Could not classify call from 'TMSI007b0002', wasted 5 usec
2018-08-09_08:28:33.985251 <register:INFO> On account 'yateadmin' performing query 'SELECT * from getroute('84985889588','') as t(location text,called text,error text,line text,formats text,rtp_forward text,divert_busy text,divert_noanswer text,maxcall int4)' expects results
2018-08-09_08:28:33.985437 <nipc:INFO> onRoute TMSI007b0002 -> 84985889588
2018-08-09_08:28:33.985886 <register:INFO> On account 'yateadmin' performing query 'UPDATE cdr SET address='TMSI007b0002', direction='incoming', billid='1533775795-12', caller='TMSI007b0002', called='84985889588', duration=INTERVAL '0.281 s', billtime=INTERVAL '0.000 s', ringtime=INTERVAL '0.000 s', status='incoming', reason='' WHERE chan='ybts/10' AND time=TIMESTAMP 'EPOCH' + INTERVAL '1533778113.704 s'' expects results
2018-08-09_08:28:33.987878 <sip/5:ALL> YateSIPConnection::YateSIPConnection(0x7fac24001ee0,'+84985889588') [0x7fabdc00b8b0]
2018-08-09_08:28:33.988004 <sip/5:ALL> NAT address is '(null)' [0x7fabdc00b8b0]
2018-08-09_08:28:33.988159 <sip/5:ALL> Set media: audio=mulaw,alaw,gsm,slin,ilbc20,ilbc30,speex,speex/16000,speex/32000,isac/16000,isac/32000 [0x7fabdc00b8b0]
2018-08-09_08:28:33.988229 <yrtp:ALL> RTP/AVP message received
2018-08-09_08:28:33.988326 <yrtp:INFO> Guessed local IP '172.16.110.174' for remote '185.45.152.174'
2018-08-09_08:28:33.988362 <yrtp:ALL> YRTPWrapper::YRTPWrapper('172.16.110.174',0x7fabdc00b8b0,'audio',bidir,0x7fabdc009530,false) [0x7fabdc003ed0]
2018-08-09_08:28:33.988396 <yrtp:ALL> YRTPWrapper::setupRTP("172.16.110.174",true,true) [0x7fabdc003ed0]
2018-08-09_08:28:33.988468 <yrtp:INFO> Session 'yrtp/1307678654' 0x7fabdc00d8f0 bound to 172.16.110.174:29372 +RTCP [0x7fabdc003ed0]
2018-08-09_08:28:33.988505 <yrtp:ALL> YRTPSource::YRTPSource(0x7fabdc003ed0) [0x7fabdc0047d0]
2018-08-09_08:28:33.988550 <yrtp:ALL> YRTPConsumer::YRTPConsumer(0x7fabdc003ed0) [0x7fabdc0206d0]
2018-08-09_08:28:33.988641 <yrtp:ALL> YRTPWrapper::setupSRTP(false) [0x7fabdc003ed0]
2018-08-09_08:28:33.989167 <INFO> DataTranslator::attachChain [0x7fabdc020be0] 'gsm' -> [0x7fabdc0206d0] '(null)' not possible
2018-08-09_08:28:33.989210 <INFO> DataTranslator::attachChain [0x7fabdc0047d0] '(null)' -> [0x7fabdc020d90] 'gsm' not possible
2018-08-09_08:28:33.989874 <sip:INFO> 'udp:0.0.0.0:5060' sending 'INVITE sip:+84985889588@sip.zadarma.com' 0x7fabdc0032f0 to 185.45.152.174:5060 [0x1eba7b0]
------
INVITE sip:+84985889588@sip.zadarma.com SIP/2.0
Max-Forwards: 20
Via: SIP/2.0/UDP 192.168.1.254:8323;rport;branch=z9hG4bK1138920479
From: <sip:+842217580@192.168.1.254:8323>;tag=78462113
To: <sip:+84985889588@sip.zadarma.com>
Call-ID: 1470968614@192.168.1.254:8323
CSeq: 10 INVITE
User-Agent: YATE/6.1.1
Contact: <sip:+842217580@192.168.1.254:8323>
Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
Content-Type: application/sdp
Content-Length: 506

v=0
o=yate 1533778113 1533778113 IN IP4 192.168.1.254
s=SIP Call
c=IN IP4 192.168.1.254
t=0 0
m=audio 29372 RTP/AVP 0 8 3 11 98 97 102 103 104 105 106 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:3 GSM/8000
a=rtpmap:11 L16/8000
a=rtpmap:98 iLBC/8000
a=fmtp:98 mode=20
a=rtpmap:97 iLBC/8000
a=fmtp:97 mode=30
a=rtpmap:102 SPEEX/8000
a=rtpmap:103 SPEEX/16000
a=rtpmap:104 SPEEX/32000
a=rtpmap:105 iSAC/16000
a=rtpmap:106 iSAC/32000
a=rtpmap:101 telephone-event/8000
a=ptime:30
------
2018-08-09_08:28:33.991361 <register:INFO> On account 'yateadmin' performing query 'UPDATE cdr SET address='TMSI007b0002', direction='incoming', billid='1533775795-12', caller='TMSI007b0002', called='84985889588', duration=INTERVAL '0.283 s', billtime=INTERVAL '0.000 s', ringtime=INTERVAL '0.000 s', status='incoming', reason='' WHERE chan='ybts/10' AND time=TIMESTAMP 'EPOCH' + INTERVAL '1533778113.704 s'' expects results
2018-08-09_08:28:33.991582 <pbxassist:CALL> Created assistant for 'sip/5'
2018-08-09_08:28:33.991792 <register:INFO> On account 'yateadmin' performing query 'INSERT INTO cdr VALUES(TIMESTAMP 'EPOCH' + INTERVAL '1533778113.989 s', 'sip/5', '185.45.152.174:5060', 'outgoing', '1533775795-12', '+842217580', '+84985889588', INTERVAL '0.003 s', INTERVAL '0.000 s', INTERVAL '0.000 s', 'outgoing', '', false)' expects results
2018-08-09_08:28:34.226848 <sip:INFO> 'udp:0.0.0.0:5060' received 485 bytes SIP message from 185.45.152.174:5060 [0x1eba7b0]
------
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.1.254:8323;rport=8323;branch=z9hG4bK1138920479;received=192.168.1.254
From: <sip:+842217580@192.168.1.254:8323>;tag=78462113
To: <sip:+84985889588@sip.zadarma.com>;tag=5149c1126e702672db415b970eae4141.ed61
Call-ID: 1470968614@192.168.1.254:8323
CSeq: 10 INVITE
Proxy-Authenticate: Digest realm="sip.zadarma.com", nonce="W2uZ7ltrmMIkoFeEMFG57iAd5TDAuGcj", qop="auth"
Server: Zadarma server
Content-Length: 0

------
2018-08-09_08:28:34.228285 <sip:INFO> 'udp:0.0.0.0:5060' sending 'ACK sip:+84985889588@sip.zadarma.com' 0x7fac3402d690 to 185.45.152.174:5060 [0x1eba7b0]
------
ACK sip:+84985889588@sip.zadarma.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.254:8323;rport;branch=z9hG4bK1138920479
From: <sip:+842217580@192.168.1.254:8323>;tag=78462113
To: <sip:+84985889588@sip.zadarma.com>;tag=5149c1126e702672db415b970eae4141.ed61
Call-ID: 1470968614@192.168.1.254:8323
CSeq: 10 ACK
Max-Forwards: 20
Contact: <sip:+842217580@192.168.1.254:8323>
User-Agent: YATE/6.1.1
Content-Length: 0

------
2018-08-09_08:28:34.228642 <sip:INFO> 'udp:0.0.0.0:5060' sending 'INVITE sip:+84985889588@sip.zadarma.com' 0x7fac3402e460 to 185.45.152.174:5060 [0x1eba7b0]
------
INVITE sip:+84985889588@sip.zadarma.com SIP/2.0
Max-Forwards: 20
Via: SIP/2.0/UDP 192.168.1.254:8323;rport;branch=z9hG4bK1516968033
From: <sip:+842217580@192.168.1.254:8323>;tag=78462113
To: <sip:+84985889588@sip.zadarma.com>
Call-ID: 1470968614@192.168.1.254:8323
User-Agent: YATE/6.1.1
Contact: <sip:+842217580@192.168.1.254:8323>
Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
CSeq: 11 INVITE
Proxy-Authorization: Digest username="165653", realm="sip.zadarma.com", nonce="W2uZ7ltrmMIkoFeEMFG57iAd5TDAuGcj", uri="sip:+84985889588@sip.zadarma.com", response="64a1aa2a52012d0278e707631faf259e", algorithm=MD5, qop=auth, nc=0000001a, cnonce="88826a55bafade2f1d6cf4e04844276f"
Content-Type: application/sdp
Content-Length: 506

v=0
o=yate 1533778113 1533778113 IN IP4 192.168.1.254
s=SIP Call
c=IN IP4 192.168.1.254
t=0 0
m=audio 29372 RTP/AVP 0 8 3 11 98 97 102 103 104 105 106 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:3 GSM/8000
a=rtpmap:11 L16/8000
a=rtpmap:98 iLBC/8000
a=fmtp:98 mode=20
a=rtpmap:97 iLBC/8000
a=fmtp:97 mode=30
a=rtpmap:102 SPEEX/8000
a=rtpmap:103 SPEEX/16000
a=rtpmap:104 SPEEX/32000
a=rtpmap:105 iSAC/16000
a=rtpmap:106 iSAC/32000
a=rtpmap:101 telephone-event/8000
a=ptime:30
------
2018-08-09_08:28:34.316136 <gsmtrx:INFO> ARFCN[0]: Slot 4. Receiver clipping 1.53803 dB (FN=502382) count=206 [0x7fac1802b400]
2018-08-09_08:28:34.465860 <sip:INFO> 'udp:0.0.0.0:5060' received 485 bytes SIP message from 185.45.152.174:5060 [0x1eba7b0]
------
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.1.254:8323;rport=8323;branch=z9hG4bK1516968033;received=192.168.1.254
From: <sip:+842217580@192.168.1.254:8323>;tag=78462113
To: <sip:+84985889588@sip.zadarma.com>;tag=5149c1126e702672db415b970eae4141.6e7c
Call-ID: 1470968614@192.168.1.254:8323
CSeq: 11 INVITE
Proxy-Authenticate: Digest realm="sip.zadarma.com", nonce="W2uZ7ltrmMIkoFeEMFG57iAd5TDAuGcj", qop="auth"
Server: Zadarma server
Content-Length: 0

------
2018-08-09_08:28:34.467114 <sip/5:ALL> YateSIPConnection::hangup() state=1 trans=0x7fabdc021080 error='(null)' code=407 reason='Proxy Authentication Required' [0x7fabdc00b8b0]
2018-08-09_08:28:34.467225 <yrtp:ALL> RTP/AVP message received
2018-08-09_08:28:34.467286 <yrtp:ALL> Wrapper 0x7fabdc003ed0 found by ID 'yrtp/1307678654'
2018-08-09_08:28:34.467338 <yrtp:INFO> YRTPWrapper::terminate() [0x7fabdc003ed0]
2018-08-09_08:28:34.467394 >>> DataTranslator::detachChain(0x7fabdc0047d0,0x7fabdc020d90)
2018-08-09_08:28:34.467429 <<< DataTranslator::detachChain
2018-08-09_08:28:34.467461 >>> DataTranslator::detachChain(0x7fabdc020be0,0x7fabdc0206d0)
2018-08-09_08:28:34.467492 <<< DataTranslator::detachChain
2018-08-09_08:28:34.467531 <yrtp:ALL> YRTPSource::~YRTPSource() [0x7fabdc0047d0] wrapper=0x7fabdc003ed0 ts=0
2018-08-09_08:28:34.467583 <yrtp:ALL> YRTPConsumer::~YRTPConsumer() [0x7fabdc0206d0] wrapper=0x7fabdc003ed0 ts=0
2018-08-09_08:28:34.467620 <yrtp:ALL> YRTPWrapper::~YRTPWrapper() bidir 'audio' [0x7fabdc003ed0]
2018-08-09_08:28:34.467655 <ALL> Cleaning up RTP 0x7fabdc00d8f0 [0x7fabdc003ed0]
2018-08-09_08:28:34.467786 <ybts/10:ALL> Disconnected 'Proxy Authentication Required' [0x7fac24003d80]
2018-08-09_08:28:34.467923 <sip/5:ALL> YateSIPConnection::~YateSIPConnection() [0x7fabdc00b8b0]
2018-08-09_08:28:34.468063 <sip:INFO> 'udp:0.0.0.0:5060' sending 'ACK sip:+84985889588@sip.zadarma.com' 0x7fac3402f7a0 to 185.45.152.174:5060 [0x1eba7b0]
------
ACK sip:+84985889588@sip.zadarma.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.254:8323;rport;branch=z9hG4bK1516968033
From: <sip:+842217580@192.168.1.254:8323>;tag=78462113
To: <sip:+84985889588@sip.zadarma.com>;tag=5149c1126e702672db415b970eae4141.6e7c
Call-ID: 1470968614@192.168.1.254:8323
CSeq: 11 ACK
Max-Forwards: 20
Contact: <sip:+842217580@192.168.1.254:8323>
Proxy-Authorization: Digest username="165653", realm="sip.zadarma.com", nonce="W2uZ7ltrmMIkoFeEMFG57iAd5TDAuGcj", uri="sip:+84985889588@sip.zadarma.com", response="64a1aa2a52012d0278e707631faf259e", algorithm=MD5, qop=auth, nc=0000001a, cnonce="88826a55bafade2f1d6cf4e04844276f"
User-Agent: YATE/6.1.1
Content-Length: 0

------
2018-08-09_08:28:34.468952 <pbxassist:INFO> Assistant for 'sip/5' hangup
2018-08-09_08:28:34.468999 <pbxassist:ALL> Assistant for 'sip/5' deleted
2018-08-09_08:28:34.469247 <ybts/10:INFO> Call 'i0' changed state CallProceeding -> Release [0x7fac24003d80]
2018-08-09_08:28:34.469365 <ybts-signalling:INFO> Sending [0x1fb06c0]
-----
Primitive: L3Message
Info: 0
Connection: 7

<CC>
  <TID TIFlag="true">0</TID>
  <Message type="Release">
    <Cause coding="GSM-PLMN" location="LPN">Proxy Authentication Required</Cause>
  </Message>
</CC>
-----
2018-08-09_08:28:34.469446 <ybts/10:CALL> Hangup reason='Proxy Authentication Required' [0x7fac24003d80]
2018-08-09_08:28:34.469508 <ybts/10:CALL> Destroyed [0x7fac24003d80]
2018-08-09_08:28:34.469729 <register:INFO> On account 'yateadmin' performing query 'UPDATE cdr SET address='185.45.152.174:5060', direction='outgoing', billid='1533775795-12', caller='+842217580', called='+84985889588', duration=INTERVAL '0.479 s', billtime=INTERVAL '0.000 s', ringtime=INTERVAL '0.000 s', status='outgoing', reason='Proxy Authentication Required', ended=true WHERE chan='sip/5' AND time=TIMESTAMP 'EPOCH' + INTERVAL '1533778113.989 s'' expects results
2018-08-09_08:28:34.470305 <javascript:ALL> Assistant for 'ybts/10' deleted
2018-08-09_08:28:34.470593 <register:INFO> On account 'yateadmin' performing query 'UPDATE cdr SET address='TMSI007b0002', direction='incoming', billid='1533775795-12', caller='TMSI007b0002', called='84985889588', duration=INTERVAL '0.765 s', billtime=INTERVAL '0.000 s', ringtime=INTERVAL '0.000 s', status='accepted', reason='Proxy Authentication Required', ended=true WHERE chan='ybts/10' AND time=TIMESTAMP 'EPOCH' + INTERVAL '1533778113.704 s'' expects results
2018-08-09_08:28:34.584756 <ybts-signalling:INFO> Received [0x1fb06c0]
-----
Primitive: PhysicalInfo
Info: 0
Connection: 7

<PhysicalInfo>TA=3 TE=0.000 UpRSSI=1 TxPwr=33 DnRSSIdBm=-111 time=1533778114.083</PhysicalInfo>
-----
2018-08-09_08:28:34.584887 <ybts-signalling:INFO> Received [0x1fb06c0]
-----
Primitive: L3Message
Info: 0
Connection: 7

<CC>
  <TID TIFlag="false">0</TID>
  <NSD>0</NSD>
  <Message type="ReleaseComplete"/>
</CC>
-----
2018-08-09_08:28:34.584948 <ybts:NOTE> Removing terminated call 'i0' conn=7
2018-08-09_08:28:34.662334 <bladerf/1:ALL> RX DC offset I set to 6 (from 6) reg=0x86 [0x7fac18000eb0]
2018-08-09_08:28:35.322264 <gsmtrx:INFO> ARFCN[0]: Slot 4. Receiver clipping -1.21505 dB (FN=502600) count=210 [0x7fac1802b400]
2018-08-09_08:28:35.806506 <bladerf/1:ALL> RX DC offset I set to 7 (from 7) reg=0x87 [0x7fac18000eb0]
2018-08-09_08:28:36.328506 <gsmtrx:INFO> ARFCN[0]: Slot 4. Receiver clipping -1.6844 dB (FN=502818) count=209 [0x7fac1802b400]
2018-08-09_08:28:37.004213 <ybts-signalling:ALL> Connection 7 idle timeout [0x1fb06c0]
2018-08-09_08:28:37.004264 <ybts-signalling:ALL> Releasing connection (0x7fac24001990,7) [0x1fb06c0]
2018-08-09_08:28:37.004307 <ybts-signalling:INFO> Sending [0x1fb06c0]
-----
Primitive: ConnRelease
Info: 0
Connection: 7
-----
2018-08-09_08:28:37.334904 <gsmtrx:INFO> ARFCN[0]: Slot 4. Receiver clipping -1.63555 dB (FN=503036) count=208 [0x7fac1802b400]
2018-08-09_08:28:42.281328 <bladerf/1:ALL> RX DC offset I set to 6 (from 6) reg=0x86 [0x7fac18000eb0]
2018-08-09_08:28:49.068195 <gsmtrx:ALL> ARFCN[0]: Slot 6. Excessive TOA error=-4 peak/mean=3.051 count=1 [0x7fac1802b400]
2018-08-09_08:28:56.004556 <register:INFO> On account 'yateadmin' performing query 'UPDATE lines SET location=NULL,expires=NULL WHERE expires IS NOT NULL AND expires<=CURRENT_TIMESTAMP'
2018-08-09_08:28:57.002973 <sip:ALL> Sending UDP keepalive to 185.45.152.174:5060 for 'outbound'
2018-08-09_08:28:58.512528 <bladerf/1:ALL> RX DC offset I set to 5 (from 5) reg=0x85 [0x7fac18000eb0]
2018-08-09_08:29:04.903685 <gsmtrx:ALL> ARFCN[0]: Slot 6. Excessive TOA errors 1 [0x7fac1802b400]
2018-08-09_08:29:08.003415 <ybts-signalling:ALL> Removing released connection 7 [0x1fb06c0]
2018-08-09_08:29:08.003500 <ybts-mm:ALL> Removed UE (0x7fac24001410): destroyed [0x1fb0aa0]
2018-08-09_08:29:08.003526 <ybts:ALL> UE destroyed [0x7fac24001410]




marian

  • Hero Member
  • *****
  • Posts: 513
    • View Profile
Re: SIP Routing Issue: Hangup reason='Proxy Authentication Required'
« Reply #1 on: August 09, 2018, 12:39:18 AM »
The Proxy-Authorization header looks ok.
You should:
- re-check account settings. Make sure the password don't contain leading or trailing spaces
- try to use another sip client with same settings (to make sure everything is ok with credentials)
- ask Zadarma what happens (if possible)

Vinsmoke Sanji

  • Newbie
  • *
  • Posts: 12
    • View Profile
Re: SIP Routing Issue: Hangup reason='Proxy Authentication Required'
« Reply #2 on: August 10, 2018, 09:27:10 PM »
thank you for answering my question!
i have one more question:
i received a report follow "SIP/2.0 401 Unauthorized". Is this a error?
the following text is detail information:
2018-08-11_10:17:04.025795 <sip:INFO> 'udp:0.0.0.0:5060' received 454 bytes SIP message from 185.45.152.174:5060 [0x1934960]
------
SIP/2.0 401 Unauthorized
To: <sip:238867@sip.zadarma.com>;tag=5149c1126e702672db415b970eae4141.308e
Call-ID: 957299803@sip.zadarma.com
Via: SIP/2.0/UDP 192.168.1.254:55040;rport=55040;branch=z9hG4bK2130938351;received=192.168.1.254
From: <sip:238867@sip.zadarma.com>;tag=363392428
CSeq: 29 REGISTER
WWW-Authenticate: Digest realm="sip.zadarma.com", nonce="W25WW1tuVS8lFhnzrBDwHvHdP7bw6Y4T", qop="auth"
Server: Zadarma server
Content-Length: 0

------
2018-08-11_10:17:04.029389 <sip:INFO> 'udp:0.0.0.0:5060' sending 'REGISTER sip:sip.zadarma.com' 0x7f9d20029850 to 185.45.152.174:5060 [0x1934960]
------
REGISTER sip:sip.zadarma.com SIP/2.0
Contact: <sip:238867@192.168.1.254:55040>
Expires: 0
To: <sip:238867@sip.zadarma.com>
Call-ID: 957299803@sip.zadarma.com
Via: SIP/2.0/UDP 192.168.1.254:55040;rport;branch=z9hG4bK1065785809
From: <sip:238867@sip.zadarma.com>;tag=363392428
User-Agent: YATE/6.1.1
Max-Forwards: 70
Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
CSeq: 30 REGISTER
Authorization: Digest username="238867", realm="sip.zadarma.com", nonce="W25WW1tuVS8lFhnzrBDwHvHdP7bw6Y4T", uri="sip:sip.zadarma.com", response="bfad0c72cdc590015716fd5a3d1ef5d2", algorithm=MD5, qop=auth, nc=0000000f, cnonce="23c173d53359e700f42335a361db0969"
Content-Length: 0

------
2018-08-11_10:17:04.268749 <sip:INFO> 'udp:0.0.0.0:5060' received 340 bytes SIP message from 185.45.152.174:5060 [0x1934960]
------
SIP/2.0 200 OK
To: <sip:238867@sip.zadarma.com>;tag=5149c1126e702672db415b970eae4141.2c89
Call-ID: 957299803@sip.zadarma.com
Via: SIP/2.0/UDP 192.168.1.254:55040;rport=55040;branch=z9hG4bK1065785809;received=192.168.1.254
From: <sip:238867@sip.zadarma.com>;tag=363392428
CSeq: 30 REGISTER
Server: Zadarma server
Content-Length: 0

marian

  • Hero Member
  • *****
  • Posts: 513
    • View Profile
Re: SIP Routing Issue: Hangup reason='Proxy Authentication Required'
« Reply #3 on: August 14, 2018, 01:11:13 AM »
The 401 reply means server challenge (requires the client to authenticate).

Vinsmoke Sanji

  • Newbie
  • *
  • Posts: 12
    • View Profile
Re: SIP Routing Issue: Hangup reason='Proxy Authentication Required'
« Reply #4 on: August 21, 2018, 01:52:07 AM »
Thank you, that is helpful.
I bought a SIP Zadarma account, i can connect internal calls to each other, i can make calls from my Yate network to the real GSM network, but my issue is being faced to the phone in the network "YateBTS" when callout the real GSM network, they can hear my voice but i can't hear them. And how to receiving inbound calls with YateBTS?

paulc

  • Newbie
  • *
  • Posts: 21
    • View Profile
Re: SIP Routing Issue: Hangup reason='Proxy Authentication Required'
« Reply #5 on: August 22, 2018, 11:40:19 AM »
One-way audio indicates usually a firewall or NAT problem.
To further diagnose look at the BYE message and its 200 OK response. Yate puts a P-RTP-Stat header indicating how many RTP (voice) packets it sent and received.

The received= tag in Via line of the answer to REGISTER is suspicious. I would expect a public IP address - the one on the outside of NAT - whose detection would allow Yate to build a proper SDP offer.
What kind of router you use for Internet access? Check if it has a SIP ALG (Application Layer Gateway) and try to turn it off.
If disabling ALG is impossible Zadarma may help if they support Symetric RTP.

Calls received over the registered account can be routed to one of the connected phones.
Add to regexroute.conf:

[contexts]
${called}^238867$=;called=MSISDN


Replace MSISDN with the number allocated to the phone you want to ring. I assumed the inbound call will be for 238867 which appears to be your account with Zadarma.

Vinsmoke Sanji

  • Newbie
  • *
  • Posts: 12
    • View Profile
Re: SIP Routing Issue: Hangup reason='Proxy Authentication Required'
« Reply #6 on: August 23, 2018, 06:47:47 PM »
paulc_Thank you again.
I have a much better understanding of how everything works.
I was able to configure everything properly.

kpz

  • Newbie
  • *
  • Posts: 11
    • View Profile
Re: SIP Routing Issue: Hangup reason='Proxy Authentication Required'
« Reply #7 on: September 25, 2018, 12:03:44 PM »
switch too voice pulse five SIP servers for yateBTS, config is easy and is very cheap.