[Blink] SIP/2.0 405 Method Not Allowed

David Herring dh at htarch.com
Thu Jan 24 14:26:48 CET 2013


We have just started experiencing a problem with Blink Pro v2.0.2.  When an incoming call is routed to an extension from the virtual receptionist, immediately after accepting the call, the call is disconnected. We have spent an hour with our SIP provider, Vocalocity.  They have tested XLite and have no such problem.  We have also tested XLite without this problem.  This problem does not occur when the call is answered by using the desk phone instead of Blink. Incoming calls directly dialing an extension's phone number work fine.

The problem is captured from the log below. (Account specifics replaced with • for security reasons.)

SENDING: Packet 40027, +1 day, 17:54:49.800569
2013-01-24 08:09:02.861111: •.•.•.•:5060 -(SIP over UDP)-> 205.139.46.210:5060
PUBLISH sip:•@sip-•.accounts.vocalocity.com SIP/2.0
Via: SIP/2.0/UDP •.•.•.•:5060;rport;branch=z9hG4bKPjxrS-GATA9O4nXe-vVvMK-O6SkIsIOTX7
Max-Forwards: 70
From: "•" <sip:•@sip-•.accounts.vocalocity.com>;tag=0NVSFFvbKyG5CJHxgswosi-pALG4n1Jk
To: "•" <sip:•@sip-•.accounts.vocalocity.com>
Call-ID: ICQzNe1PChbGCZA7zwN2sCmY0S166hpT
CSeq: 1 PUBLISH
Event: presence
Expires: 3600
User-Agent: Blink Pro 2.0.2 (MacOSX)
Content-Type: application/pidf+xml
Content-Length:  1950

<?xml version='1.0' encoding='UTF-8'?>
<presence xmlns:c="urn:ietf:params:xml:ns:pidf:cipid" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:agp-caps="urn:ag-projects:xml:ns:pidf:caps" xmlns:caps="urn:ietf:params:xml:ns:pidf:caps" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" xmlns:agp-pidf="urn:ag-projects:xml:ns:pidf" xmlns="urn:ietf:params:xml:ns:pidf" entity="sip%3A•%40sip-•.accounts.vocalocity.com"><tuple id="SID-a552b104-0b23-4552-9b11-308ff00014eb"><status><basic>open</basic><agp-pidf:extended>available</agp-pidf:extended></status><c:display-name>•</c:display-name><c:map>United%20States/Herndon</c:map><c:homepage>http%3A//•</c:homepage><agp-pidf:device-info id="a552b104-0b23-4552-9b11-308ff00014eb"><agp-pidf:description>i703</agp-pidf:description><agp-pidf:user-agent>Blink Pro 2.0.2 (MacOSX)</agp-pidf:user-agent><agp-pidf:time-offset>1140</agp-pidf:time-offset></agp-pidf:device-info><caps:servcaps><caps:audio>true</caps:audio><caps:message>true</caps:message><caps:text>true</caps:text><agp-caps:file-transfer>true</agp-caps:file-transfer><agp-caps:screen-sharing>true</agp-caps:screen-sharing></caps:servcaps><rpid:user-input idle-threshold="600">active</rpid:user-input><dm:deviceID>a552b104-0b23-4552-9b11-308ff00014eb</dm:deviceID><contact>sip%3AVH247501%40sip-•.accounts.vocalocity.com</contact><note></note><timestamp>2013-01-24T08:09:02.803051-05:00</timestamp></tuple><dm:person id="PID-1f93cb79fb8026924246c92e0d520ded"><rpid:time-offset>1140</rpid:time-offset><rpid:activities><rpid:other>available</rpid:other></rpid:activities><dm:timestamp>2013-01-24T08:09:02.803051-05:00</dm:timestamp></dm:person><dm:device id="DID-a552b104-0b23-4552-9b11-308ff00014eb"><dm:deviceID>a552b104-0b23-4552-9b11-308ff00014eb</dm:deviceID><dm:note>Blink Pro 2.0.2 (MacOSX) at •i703</dm:note><dm:timestamp>2013-01-24T08:09:02.803051-05:00</dm:timestamp></dm:device></presence>

RECEIVED: Packet 40028, +1 day, 17:54:49.817541
2013-01-24 08:09:02.878083: •.•.•.•:5060 -(SIP over UDP)-> •.•.•.•:5060
SIP/2.0 405 Method Not Allowed
Via: SIP/2.0/UDP •.•.•.•:5060;received=98.172.25.60;rport=43982;branch=z9hG4bKPjxrS-GATA9O4nXe-vVvMK-O6SkIsIOTX7
From: "•" <sip:•@sip-•.accounts.vocalocity.com>;tag=0NVSFFvbKyG5CJHxgswosi-pALG4n1Jk
To: "•" <sip-•.accounts.vocalocity.com>;tag=c97b4d1cb1f3d0da549e06a8d482ef63.6b79
Call-ID: ICQzNe1PChbGCZA7zwN2sCmY0S166hpT
CSeq: 1 PUBLISH
Server: Vocalocity SIP (1.7.2-notls (x86_64/linux))
Content-Length: 0  

Needless to say, this is of extreme importance to us as hanging up on our clients is not acceptable.  Any help would be greatly appreciated.  Thanks!

Mister H

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ag-projects.com/pipermail/blink/attachments/20130124/f6d018c2/attachment.html>


More information about the Blink mailing list