Blind transfer on Cisco phones fails

FreeSentral > FreeSentral - Yate based IP PBX

(1/4) > >>

lewis:
Hi,

I've been trying Yate and FreeSentral as a possible replacement for our current Asterisk SIP server. Unfortunately I'm having trouble whilst testing compatibility with our Cisco SPA504G phones.

I use extension 1056 to call extension 1024. I answer the call and use the phone's blind transfer button to try transferring the call to extension 1052. When I select the blind xfer button on handset 1024, enter extension 1052 and press 'dial', it says the transfer failed and puts the call back on hold.

An extract from Yate's debug log show this:

------
20150312131235.896679 <sip:INFO> 'udp:0.0.0.0:5060' received 462 bytes SIP message from 192.168.16.62:5060 [0x80211d900]
------
REFER sip:1024@x.x.x.166:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.16.62:5060;branch=z9h0000-000034c
From: <sip:1056@192.168.16.62>;tag=e07bbfb000000ca1i0
To: "1024" <sip:1024@x.x.x.166>;tag=770492463
Referred-By: "1056" <sip:1056@x.x.x.166>
Call-ID: 641670369@x.x.x.166
CSeq: 102 REFER
Max-Forwards: 70
Contact: "1056" <sip:1056@192.168.16.62:5060>
Refer-To: <sip:1052@x.x.x.166>
User-Agent: Cisco/SPA504G-7.5.6a
Content-Length: 0

------
20150312131235.907558 <sip:INFO> 'udp:0.0.0.0:5060' sending code 100 0x8020db600 to 192.168.16.62:5060 [0x80211d900]
------
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.16.62:5060;branch=z9hG4bK-f39a34c;received=192.168.16.62
From: <sip:1056@192.168.16.62>;tag=e07bbfb0419d8ca1i0
To: "1024" <sip:1024@x.x.x.166>;tag=770492463
Call-ID: 641670369@x.x.x.166
CSeq: 102 REFER
Server: YATE/5.4.0
Content-Length: 0

20150312131235.907776 <sip/3:STUB> initTransfer. Possible incomplete NOTIFY party creation [0x80e0b9800]
20150312131235.913491 <sip:INFO> 'udp:0.0.0.0:5060' sending code 481 0x80e061700 to 192.168.16.62:5060 [0x80211d900]
------
SIP/2.0 481 Call/Transaction Does Not Exist
Via: SIP/2.0/UDP 192.168.16.62:5060;branch=z9hG000-f390000;received=192.168.16.62
From: <sip:1056@192.168.16.62>;tag=e07bbfb000000ca1i0
To: "1024" <sip:1024@x.x.x.166>;tag=770492463
Call-ID: 641670369@x.x.x.166
CSeq: 102 REFER
Server: YATE/5.4.0
Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
Content-Length: 0

With kind assistance from a few people in the #yate IRC channel, I have tried all kinds of things to figure out why this isn't working all without success :(

I've made sure to set a *98 trigger in the [transfer] subsection (to match the phone) in pbxassist.conf. I've set transfer=enable in ysipchan.conf. I changed the phone to send $OPTIONS messages instead of $NOTIFY messages because Yate said NOTIFY messages were not allowed despite adding NOTIFY=no to [methods] in ysipchan.conf.

Help or advice from anyone here please would be very much appreciated. Thank you in advance for your time and consideration.

Kind regards,
Lewis

marian:
Hi,
A possible failure reason may be call route failure.
Can you post a log with sniffer enabled?

lewis:
Hi,

Thanks for your help.

Centurion_Dan helped with setting up the sniffer. Apparently the route fails because of a 'noauth' error. I'm not sure why that would happen though?

20150313112643.981270 <sip:INFO> 'udp:0.0.0.0:5060' received 464 bytes SIP message from 192.168.16.62:5060 [0x80210c900]
------
REFER sip:1024@x.x.x.166:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.16.62:5060;branch=z9hG4bK-c4b373f8
From: <sip:1056@192.168.16.62>;tag=c1e180a16e76fb2fi0
To: "1024" <sip:1024@x.x.x.166>;tag=679522944
Referred-By: "1056" <sip:1056@x.x.x.166>
Call-ID: 1117126792@x.x.x.166
CSeq: 102 REFER
Max-Forwards: 70
Contact: "1056" <sip:1056@192.168.16.62:5060>
Refer-To: <sip:1052@x.x.x.166>
User-Agent: Cisco/SPA504G-7.5.6a
Content-Length: 0

------
20150313112643.992061 <sip:INFO> 'udp:0.0.0.0:5060' sending code 100 0x80dc84980 to 192.168.16.62:5060 [0x80210c900]
------
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.16.62:5060;branch=z9hG4bK-c4b373f8;received=192.168.16.62
From: <sip:1056@192.168.16.62>;tag=c1e180a16e76fb2fi0
To: "1024" <sip:1024@x.x.x.166>;tag=679522944
Call-ID: 1117126792@x.x.x.166
CSeq: 102 REFER
Server: YATE/5.4.0
Content-Length: 0

------
20150313112643.992276 <sip/12:STUB> initTransfer. Possible incomplete NOTIFY party creation [0x80e108800]
Sniffed 'call.route' time=1426246003.992221
thread=0x80e434020 'YSIP Transfer'
data=0x0
retval='(null)'
param['id'] = 'sip/11'
param['billid'] = '1426244789-8'
param['caller'] = '1024'
param['callername'] = '1024'
param['called'] = '1052'
param['calledname'] = ''
param['diverter'] = '1056'
param['divertername'] = '1056'
param['reason'] = 'transfer'
param['sip_referred-by'] = '"1056" <sip:1056@x.x.x.166>'
param['sip_contact'] = '"1056" <sip:1056@192.168.16.62:5060>'
param['sip_refer-to'] = '<sip:1052@x.x.x.166>'
param['sip_user-agent'] = 'Cisco/SPA504G-7.5.6a'
Returned false 'call.route' delay=0.010829
thread=0x80e434020 'YSIP Transfer'
data=0x0
retval='(null)'
param['id'] = 'sip/11'
param['billid'] = '1426244789-8'
param['caller'] = '1024'
param['callername'] = '1024'
param['called'] = '1052'
param['calledname'] = ''
param['diverter'] = '1056'
param['divertername'] = '1056'
param['reason'] = 'transfer'
param['sip_referred-by'] = '"1056" <sip:1056@x.x.x.166>'
param['sip_contact'] = '"1056" <sip:1056@192.168.16.62:5060>'
param['sip_refer-to'] = '<sip:1052@x.x.x.166>'
param['sip_user-agent'] = 'Cisco/SPA504G-7.5.6a'
param['handlers'] = 'javascript:15,cdrbuild:50,fileinfo:90,regexroute:95,iax:100,jingle:100,subscription:100,sip:100,sig:100,analog:100,regfile:100'
param['copyparams'] = 'maxcall,call_type,already-auth,trusted-auth'
param['pbxparams'] = 'maxcall,call_type,already-auth,trusted-auth,copyparams'
param['error'] = 'noauth'
20150313112644.003786 <sip:INFO> 'udp:0.0.0.0:5060' sending code 481 0x80e065c40 to 192.168.16.62:5060 [0x80210c900]
------
SIP/2.0 481 Call/Transaction Does Not Exist
Via: SIP/2.0/UDP 192.168.16.62:5060;branch=z9hG4bK-c4b373f8;received=192.168.16.62
From: <sip:1056@192.168.16.62>;tag=c1e180a16e76fb2fi0
To: "1024" <sip:1024@x.x.x.166>;tag=679522944
Call-ID: 1117126792@x.x.x.166
CSeq: 102 REFER
Server: YATE/5.4.0
Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO, NOTIFY
Content-Length: 0

marian:
You have somewhere a rule setting error='noauth'.
Check it.

lewis:
Oh right! I don't think I've created any rules yet though, everything should be using the default configuration for Yate / FreeSentral. Do you have any pointers for where I might find what is causing the 'noauth' problem please?

Navigation

[0] Message Index

[#] Next page

Go to full version