Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

on run of b2bua_simple : AttributeError: 'unicode' object has no attribute 'localStr' #30

Open
arvoshift opened this issue Jun 4, 2018 · 3 comments
Open

on run of b2bua_simple : AttributeError: 'unicode' object has no attribute 'localStr' #30

arvoshift opened this issue Jun 4, 2018 · 3 comments

Comments

@arvoshift
Copy link

Background info:

I'm trying to do a proof of concept where My Softphone at 192.168.44.1 registers to SIPpy at 192.168.44.3(test VM) using the realm 7385@192.168.44.3.
SIPpy then passes on the register, modifying the realm to 7385@sip.example.net.au (1.2.3.X)
rtpproxy is running, using unix socket.

The scenario I'm trying to solve is that I have some legacy sip servers that customers directly register to. I want to be able to simply drop sippy in as a replacement to these old servers and b2bua all traffic to new kamailio infrastructure. This way the client devices need no reconfiguration and I can make the move independent of them.

Issue:
Registration works fine however the invite seems to raise a Unicode error.
I'm running a fresh install of Centos7 (latest updates), python 2.7.5
selinux is permissive, no firewall

Log output
`[root@legacyproxy ~]# b2bua_otw_simple -f -l 192.168.44.3 -p 5060 -n sip.example.net.au -L /var/log/sippy.log
('sip.example.net.au', 5060)
04 Jun 06:16:36.319/GLOBAL/b2bua: RECEIVED message from 192.168.44.1:55245:
REGISTER sip:192.168.44.3 SIP/2.0
Via: SIP/2.0/UDP 192.168.44.1:55245;rport;branch=z9hG4bKPj8f0d561a94c5444eb42a5652cd0da4c9
Route: sip:192.168.44.3;lr
Max-Forwards: 70
From: sip:7385@192.168.44.3;tag=5458100f2dc44fdcb065314900298768
To: sip:7385@192.168.44.3
Call-ID: 2b4f54b175bd4c4ebdde62d8847553c7
CSeq: 28989 REGISTER
User-Agent: MicroSIP/3.18.2
Contact: sip:7385@192.168.44.1:55245;ob
Expires: 0
Content-Length: 0

REGISTER sip:192.168.44.3 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK39fb4807071a0178d7a4657b62accaa1;rport
Via: SIP/2.0/UDP 192.168.44.1:55245;branch=z9hG4bKPj8f0d561a94c5444eb42a5652cd0da4c9;rport=55245
Route: sip:192.168.44.3;lr
Max-Forwards: 70
From: sip:7385@192.168.44.3;tag=5458100f2dc44fdcb065314900298768
To: sip:7385@192.168.44.3
Call-ID: 2b4f54b175bd4c4ebdde62d8847553c7
CSeq: 28989 REGISTER
User-Agent: MicroSIP/3.18.2
Contact: sip:7385@192.168.44.1:55245;ob
Expires: 0
Content-Length: 0

04 Jun 06:16:36.327/GLOBAL/b2bua: SENDING message to sip.example.net.au:5060:
REGISTER sip:192.168.44.3 SIP/2.0
Via: SIP/2.0/UDP 192.168.44.3:5060;branch=z9hG4bK39fb4807071a0178d7a4657b62accaa1;rport
Via: SIP/2.0/UDP 192.168.44.1:55245;branch=z9hG4bKPj8f0d561a94c5444eb42a5652cd0da4c9;rport=55245
Route: sip:192.168.44.3;lr
Max-Forwards: 70
From: sip:7385@192.168.44.3;tag=5458100f2dc44fdcb065314900298768
To: sip:7385@192.168.44.3
Call-ID: 2b4f54b175bd4c4ebdde62d8847553c7
CSeq: 28989 REGISTER
User-Agent: MicroSIP/3.18.2
Contact: sip:7385@192.168.44.1:55245;ob
Expires: 0
Content-Length: 0

04 Jun 06:16:36.385/GLOBAL/b2bua: RECEIVED message from 1.2.3.68:5060:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.44.3:5060;branch=z9hG4bK39fb4807071a0178d7a4657b62accaa1;rport=63230;received=203.55.174.123
Via: SIP/2.0/UDP 192.168.44.1:55245;branch=z9hG4bKPj8f0d561a94c5444eb42a5652cd0da4c9;rport=55245
From: sip:7385@192.168.44.3;tag=5458100f2dc44fdcb065314900298768
To: sip:7385@192.168.44.3;tag=9dd61ff61e802d8e2bef5f14621ef3c2.5c34
Call-ID: 2b4f54b175bd4c4ebdde62d8847553c7
CSeq: 28989 REGISTER
WWW-Authenticate: Digest realm="sip.example.net.au", nonce="WxTacFsU2USCyjLoANeeeoVhbKEUpMQs"
User-Agent: example-LB
Content-Length: 0

04 Jun 06:16:36.387/GLOBAL/b2bua: SENDING message to 192.168.44.1:55245:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.44.1:55245;rport=55245;branch=z9hG4bKPj8f0d561a94c5444eb42a5652cd0da4c9
From: sip:7385@192.168.44.3;tag=5458100f2dc44fdcb065314900298768
To: sip:7385@192.168.44.3;tag=9dd61ff61e802d8e2bef5f14621ef3c2.5c34
Call-ID: 2b4f54b175bd4c4ebdde62d8847553c7
CSeq: 28989 REGISTER
WWW-Authenticate: Digest realm="sip.example.net.au", nonce="WxTacFsU2USCyjLoANeeeoVhbKEUpMQs"
User-Agent: example-LB
Content-Length: 0

04 Jun 06:16:36.394/GLOBAL/b2bua: RECEIVED message from 192.168.44.1:55245:
REGISTER sip:192.168.44.3 SIP/2.0
Via: SIP/2.0/UDP 192.168.44.1:55245;rport;branch=z9hG4bKPj425267067e5f437ca66867b560c7efba
Route: sip:192.168.44.3;lr
Max-Forwards: 70
From: sip:7385@192.168.44.3;tag=5458100f2dc44fdcb065314900298768
To: sip:7385@192.168.44.3
Call-ID: 2b4f54b175bd4c4ebdde62d8847553c7
CSeq: 28990 REGISTER
User-Agent: MicroSIP/3.18.2
Contact: sip:7385@192.168.44.1:55245;ob
Expires: 0
Authorization: Digest username="7385", realm="sip.example.net.au", nonce="WxTacFsU2USCyjLoANeeeoVhbKEUpMQs", uri="sip:192.168.44.3", response="6cc3f02a9a62f8647eaa79dbbc
dc4d89"
Content-Length: 0

REGISTER sip:192.168.44.3 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bKf05857b0f7d8d29cce0b4981cfaeff7d;rport
Via: SIP/2.0/UDP 192.168.44.1:55245;branch=z9hG4bKPj425267067e5f437ca66867b560c7efba;rport=55245
Route: sip:192.168.44.3;lr
Max-Forwards: 70
From: sip:7385@192.168.44.3;tag=5458100f2dc44fdcb065314900298768
To: sip:7385@192.168.44.3
Call-ID: 2b4f54b175bd4c4ebdde62d8847553c7
CSeq: 28990 REGISTER
User-Agent: MicroSIP/3.18.2
Contact: sip:7385@192.168.44.1:55245;ob
Expires: 0
Authorization: Digest username="7385", realm="sip.example.net.au", nonce="WxTacFsU2USCyjLoANeeeoVhbKEUpMQs", uri="sip:192.168.44.3", response="6cc3f02a9a62f8647eaa79dbbc
dc4d89"
Content-Length: 0

04 Jun 06:16:36.398/GLOBAL/b2bua: SENDING message to sip.example.net.au:5060:
REGISTER sip:192.168.44.3 SIP/2.0
Via: SIP/2.0/UDP 192.168.44.3:5060;branch=z9hG4bKf05857b0f7d8d29cce0b4981cfaeff7d;rport
Via: SIP/2.0/UDP 192.168.44.1:55245;branch=z9hG4bKPj425267067e5f437ca66867b560c7efba;rport=55245
Route: sip:192.168.44.3;lr
Max-Forwards: 70
From: sip:7385@192.168.44.3;tag=5458100f2dc44fdcb065314900298768
To: sip:7385@192.168.44.3
Call-ID: 2b4f54b175bd4c4ebdde62d8847553c7
CSeq: 28990 REGISTER
User-Agent: MicroSIP/3.18.2
Contact: sip:7385@192.168.44.1:55245;ob
Expires: 0
Authorization: Digest username="7385", realm="sip.example.net.au", nonce="WxTacFsU2USCyjLoANeeeoVhbKEUpMQs", uri="sip:192.168.44.3", response="6cc3f02a9a62f8647eaa79dbbc
dc4d89"
Content-Length: 0

04 Jun 06:16:36.410/GLOBAL/b2bua: RECEIVED message from 1.2.3.4:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.44.3:5060;received=203.55.174.123;branch=z9hG4bKf05857b0f7d8d29cce0b4981cfaeff7d;rport=63230
Via: SIP/2.0/UDP 192.168.44.1:55245;branch=z9hG4bKPj425267067e5f437ca66867b560c7efba;rport=55245
From: sip:7385@192.168.44.3;tag=5458100f2dc44fdcb065314900298768
To: sip:7385@192.168.44.3;tag=290f473369cc3c154b744fae3269e66d.b590
Call-ID: 2b4f54b175bd4c4ebdde62d8847553c7
CSeq: 28990 REGISTER
User-Agent: example-Registrar
Content-Length: 0

04 Jun 06:16:36.419/GLOBAL/b2bua: SENDING message to 192.168.44.1:55245:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.44.1:55245;rport=55245;branch=z9hG4bKPj425267067e5f437ca66867b560c7efba
From: sip:7385@192.168.44.3;tag=5458100f2dc44fdcb065314900298768
To: sip:7385@192.168.44.3;tag=290f473369cc3c154b744fae3269e66d.b590
Call-ID: 2b4f54b175bd4c4ebdde62d8847553c7
CSeq: 28990 REGISTER
User-Agent: example-Registrar
Content-Length: 0

04 Jun 06:16:39.544/GLOBAL/b2bua: RECEIVED message from 192.168.44.1:55245:
REGISTER sip:192.168.44.3 SIP/2.0
Via: SIP/2.0/UDP 192.168.44.1:55245;rport;branch=z9hG4bKPjfb7460593f7c45d598c42d2074a0f9b3
Route: sip:192.168.44.3;lr
Max-Forwards: 70
From: sip:7385@192.168.44.3;tag=9dac76b5f7da472d92012e31bebf2f8d
To: sip:7385@192.168.44.3
Call-ID: 3803c3ce93cc4fccac17f3369eb05984
CSeq: 27006 REGISTER
User-Agent: MicroSIP/3.18.2
Contact: sip:7385@192.168.44.1:55245;ob
Expires: 300
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Content-Length: 0

REGISTER sip:192.168.44.3 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK400626d679516986c7c9c675e171be5e;rport
Via: SIP/2.0/UDP 192.168.44.1:55245;branch=z9hG4bKPjfb7460593f7c45d598c42d2074a0f9b3;rport=55245
Route: sip:192.168.44.3;lr
Max-Forwards: 70
From: sip:7385@192.168.44.3;tag=9dac76b5f7da472d92012e31bebf2f8d
To: sip:7385@192.168.44.3
Call-ID: 3803c3ce93cc4fccac17f3369eb05984
CSeq: 27006 REGISTER
User-Agent: MicroSIP/3.18.2
Contact: sip:7385@192.168.44.1:55245;ob
Expires: 300
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Content-Length: 0

04 Jun 06:16:39.546/GLOBAL/b2bua: SENDING message to sip.example.net.au:5060:
REGISTER sip:192.168.44.3 SIP/2.0
Via: SIP/2.0/UDP 192.168.44.3:5060;branch=z9hG4bK400626d679516986c7c9c675e171be5e;rport
Via: SIP/2.0/UDP 192.168.44.1:55245;branch=z9hG4bKPjfb7460593f7c45d598c42d2074a0f9b3;rport=55245
Route: sip:192.168.44.3;lr
Max-Forwards: 70
From: sip:7385@192.168.44.3;tag=9dac76b5f7da472d92012e31bebf2f8d
To: sip:7385@192.168.44.3
Call-ID: 3803c3ce93cc4fccac17f3369eb05984
CSeq: 27006 REGISTER
User-Agent: MicroSIP/3.18.2
Contact: sip:7385@192.168.44.1:55245;ob
Expires: 300
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Content-Length: 0

04 Jun 06:16:39.549/GLOBAL/b2bua: RECEIVED message from 103.26.174.4:5060:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.44.3:5060;branch=z9hG4bK400626d679516986c7c9c675e171be5e;rport=63230;received=203.55.174.123
Via: SIP/2.0/UDP 192.168.44.1:55245;branch=z9hG4bKPjfb7460593f7c45d598c42d2074a0f9b3;rport=55245
From: sip:7385@192.168.44.3;tag=9dac76b5f7da472d92012e31bebf2f8d
To: sip:7385@192.168.44.3;tag=b27e1a1d33761e85846fc98f5f3a7e58.9813
Call-ID: 3803c3ce93cc4fccac17f3369eb05984
CSeq: 27006 REGISTER
WWW-Authenticate: Digest realm="sip.example.net.au", nonce="WxTac1sU2Uc6VhynGRfYBXUahzmR1xhY"
User-Agent: example-LB
Content-Length: 0

04 Jun 06:16:39.557/GLOBAL/b2bua: SENDING message to 192.168.44.1:55245:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.44.1:55245;rport=55245;branch=z9hG4bKPjfb7460593f7c45d598c42d2074a0f9b3
From: sip:7385@192.168.44.3;tag=9dac76b5f7da472d92012e31bebf2f8d
To: sip:7385@192.168.44.3;tag=b27e1a1d33761e85846fc98f5f3a7e58.9813
Call-ID: 3803c3ce93cc4fccac17f3369eb05984
CSeq: 27006 REGISTER
WWW-Authenticate: Digest realm="sip.example.net.au", nonce="WxTac1sU2Uc6VhynGRfYBXUahzmR1xhY"
User-Agent: example-LB
Content-Length: 0

04 Jun 06:16:39.558/GLOBAL/b2bua: RECEIVED message from 192.168.44.1:55245:
REGISTER sip:192.168.44.3 SIP/2.0
Via: SIP/2.0/UDP 192.168.44.1:55245;rport;branch=z9hG4bKPj7b2c654661d64ddfb76cf3d38c141065
Route: sip:192.168.44.3;lr
Max-Forwards: 70
From: sip:7385@192.168.44.3;tag=9dac76b5f7da472d92012e31bebf2f8d
To: sip:7385@192.168.44.3
Call-ID: 3803c3ce93cc4fccac17f3369eb05984
CSeq: 27007 REGISTER
User-Agent: MicroSIP/3.18.2
Contact: sip:7385@192.168.44.1:55245;ob
Expires: 300
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Authorization: Digest username="7385", realm="sip.example.net.au", nonce="WxTac1sU2Uc6VhynGRfYBXUahzmR1xhY", uri="sip:192.168.44.3", response="5553b819c94df53a65f1a3e887
6d6168"
Content-Length: 0

REGISTER sip:192.168.44.3 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK89a0fe9928c4e9fab00f2ec7d98e4a01;rport
Via: SIP/2.0/UDP 192.168.44.1:55245;branch=z9hG4bKPj7b2c654661d64ddfb76cf3d38c141065;rport=55245
Route: sip:192.168.44.3;lr
Max-Forwards: 70
From: sip:7385@192.168.44.3;tag=9dac76b5f7da472d92012e31bebf2f8d
To: sip:7385@192.168.44.3
Call-ID: 3803c3ce93cc4fccac17f3369eb05984
CSeq: 27007 REGISTER
User-Agent: MicroSIP/3.18.2
Contact: sip:7385@192.168.44.1:55245;ob
Expires: 300
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Authorization: Digest username="7385", realm="sip.example.net.au", nonce="WxTac1sU2Uc6VhynGRfYBXUahzmR1xhY", uri="sip:192.168.44.3", response="5553b819c94df53a65f1a3e887
6d6168"
Content-Length: 0

04 Jun 06:16:39.568/GLOBAL/b2bua: SENDING message to sip.example.net.au:5060:
REGISTER sip:192.168.44.3 SIP/2.0
Via: SIP/2.0/UDP 192.168.44.3:5060;branch=z9hG4bK89a0fe9928c4e9fab00f2ec7d98e4a01;rport
Via: SIP/2.0/UDP 192.168.44.1:55245;branch=z9hG4bKPj7b2c654661d64ddfb76cf3d38c141065;rport=55245
Route: sip:192.168.44.3;lr
Max-Forwards: 70
From: sip:7385@192.168.44.3;tag=9dac76b5f7da472d92012e31bebf2f8d
To: sip:7385@192.168.44.3
Call-ID: 3803c3ce93cc4fccac17f3369eb05984
CSeq: 27007 REGISTER
User-Agent: MicroSIP/3.18.2
Contact: sip:7385@192.168.44.1:55245;ob
Expires: 300
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Authorization: Digest username="7385", realm="sip.example.net.au", nonce="WxTac1sU2Uc6VhynGRfYBXUahzmR1xhY", uri="sip:192.168.44.3", response="5553b819c94df53a65f1a3e887
6d6168"
Content-Length: 0

04 Jun 06:16:39.589/GLOBAL/b2bua: RECEIVED message from 103.26.174.36:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.44.3:5060;received=203.55.174.123;branch=z9hG4bK89a0fe9928c4e9fab00f2ec7d98e4a01;rport=63230
Via: SIP/2.0/UDP 192.168.44.1:55245;branch=z9hG4bKPj7b2c654661d64ddfb76cf3d38c141065;rport=55245
From: sip:7385@192.168.44.3;tag=9dac76b5f7da472d92012e31bebf2f8d
To: sip:7385@192.168.44.3;tag=38a879c93a4c4105a45c2bf6407aed55.9192
Call-ID: 3803c3ce93cc4fccac17f3369eb05984
CSeq: 27007 REGISTER
Contact: sip:7385@192.168.44.1:55245;ob;received="sip:203.55.174.123:63230";expires=300
User-Agent: example-Registrar
Content-Length: 0

04 Jun 06:16:39.598/GLOBAL/b2bua: SENDING message to 192.168.44.1:55245:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.44.1:55245;rport=55245;branch=z9hG4bKPj7b2c654661d64ddfb76cf3d38c141065
From: sip:7385@192.168.44.3;tag=9dac76b5f7da472d92012e31bebf2f8d
To: sip:7385@192.168.44.3;tag=38a879c93a4c4105a45c2bf6407aed55.9192
Call-ID: 3803c3ce93cc4fccac17f3369eb05984
CSeq: 27007 REGISTER
Contact: sip:7385@192.168.44.1:55245;ob;received="sip:203.55.174.123:63230";expires=300
User-Agent: example-Registrar
Content-Length: 0

04 Jun 06:16:53.769/GLOBAL/b2bua: RECEIVED message from 192.168.44.1:55245:
INVITE sip:61449082568@192.168.44.3 SIP/2.0
Via: SIP/2.0/UDP 192.168.44.1:55245;rport;branch=z9hG4bKPj39262faf126e4dcba1d898a0e561bdd1
Max-Forwards: 70
From: sip:7385@192.168.44.3;tag=d37cfda85b554070869b0285abb41685
To: sip:61449082568@192.168.44.3
Contact: sip:7385@192.168.44.1:55245;ob
Call-ID: f588507ff3c64fc5bed33710e960410d
CSeq: 26283 INVITE
Route: sip:192.168.44.3;lr
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Supported: replaces, 100rel, timer, norefersub
Session-Expires: 1800
Min-SE: 90
User-Agent: MicroSIP/3.18.2
Content-Type: application/sdp
Content-Length: 340

v=0
o=- 3737117813 3737117813 IN IP4 192.168.44.1
s=pjmedia
b=AS:84
t=0 0
a=X-nat:0
m=audio 4000 RTP/AVP 8 0 101
c=IN IP4 192.168.44.1
b=TIAS:64000
a=rtcp:4001 IN IP4 192.168.44.1
a=sendrecv
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ssrc:1495688157 cname:192b28e72d4a16ce

04 Jun 06:16:53.779/GLOBAL/b2bua: SENDING message to 192.168.44.1:55245:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.44.1:55245;rport=55245;branch=z9hG4bKPj39262faf126e4dcba1d898a0e561bdd1
From: sip:7385@192.168.44.3;tag=d37cfda85b554070869b0285abb41685
To: sip:61449082568@192.168.44.3
Call-ID: f588507ff3c64fc5bed33710e960410d
CSeq: 26283 INVITE
Content-Length: 0

2018-06-04 06:16:53.779857 Udp_server: unhandled exception when processing incoming data

Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/sippy/Udp_server.py", line 252, in handle_read
self.uopts.data_callback(data, address, self, rtime)
File "/usr/lib/python2.7/site-packages/sippy/SipTransactionManager.py", line 330, in handleIncoming
self.incomingRequest(req, checksum, tids, server)
File "/usr/lib/python2.7/site-packages/sippy/SipTransactionManager.py", line 616, in incomingRequest
rval = self.req_cb(msg, t)
File "/usr/lib/python2.7/site-packages/sippy/b2bua_simple.py", line 87, in recvRequest
return cc.uaA.recvRequest(req, sip_t)
File "/usr/lib/python2.7/site-packages/sippy/UA.py", line 171, in recvRequest
self.emitPendingEvents()
File "/usr/lib/python2.7/site-packages/sippy/UA.py", line 267, in emitPendingEvents
self.event_cb(event, self)
File "/usr/lib/python2.7/site-packages/sippy/b2bua_simple.py", line 62, in recvEvent
self.uaO.recvEvent(event)
File "/usr/lib/python2.7/site-packages/sippy/UA.py", line 217, in recvEvent
newstate = self.state.recvEvent(event)
File "/usr/lib/python2.7/site-packages/sippy/UacStateIdle.py", line 80, in recvEvent
laddress = self.ua.source_address, cb_ifver = 2, compact = self.ua.compact_sip)
File "/usr/lib/python2.7/site-packages/sippy/SipTransactionManager.py", line 354, in newTransaction
t.data = msg.localStr(*t.userv.uopts.getSIPaddr(), compact = t.compact)
File "/usr/lib/python2.7/site-packages/sippy/SipMsg.py", line 169, in localStr
mbody = self.body.localStr(local_addr, local_port)
File "/usr/lib/python2.7/site-packages/sippy/MsgBody.py", line 62, in localStr
return self.content.localStr(local_addr, local_port)
AttributeError: 'unicode' object has no attribute 'localStr'

04 Jun 06:17:27.821/GLOBAL/b2bua: RECEIVED message from 192.168.44.1:55245:
CANCEL sip:61449082568@192.168.44.3 SIP/2.0
Via: SIP/2.0/UDP 192.168.44.1:55245;rport;branch=z9hG4bKPj39262faf126e4dcba1d898a0e561bdd1
Max-Forwards: 70
From: sip:7385@192.168.44.3;tag=d37cfda85b554070869b0285abb41685
To: sip:61449082568@192.168.44.3
Call-ID: f588507ff3c64fc5bed33710e960410d
CSeq: 26283 CANCEL
Route: sip:192.168.44.3;lr
Content-Length: 0

04 Jun 06:17:27.830/GLOBAL/b2bua: SENDING message to 192.168.44.1:55245:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.44.1:55245;rport=55245;branch=z9hG4bKPj39262faf126e4dcba1d898a0e561bdd1
From: sip:7385@192.168.44.3;tag=d37cfda85b554070869b0285abb41685
To: sip:61449082568@192.168.44.3
Call-ID: f588507ff3c64fc5bed33710e960410d
CSeq: 26283 CANCEL
Content-Length: 0

04 Jun 06:17:27.830/GLOBAL/b2bua: SENDING message to 192.168.44.1:55245:
SIP/2.0 487 Request Terminated
Via: SIP/2.0/UDP 192.168.44.1:55245;rport=55245;branch=z9hG4bKPj39262faf126e4dcba1d898a0e561bdd1
From: sip:7385@192.168.44.3;tag=d37cfda85b554070869b0285abb41685
To: sip:61449082568@192.168.44.3;tag=45313239068d7168de0659f93f0137c1
Call-ID: f588507ff3c64fc5bed33710e960410d
CSeq: 26283 INVITE
Content-Length: 0

04 Jun 06:17:27.831/GLOBAL/b2bua: RECEIVED message from 192.168.44.1:55245:
ACK sip:61449082568@192.168.44.3 SIP/2.0
Via: SIP/2.0/UDP 192.168.44.1:55245;rport;branch=z9hG4bKPj39262faf126e4dcba1d898a0e561bdd1
Max-Forwards: 70
From: sip:7385@192.168.44.3;tag=d37cfda85b554070869b0285abb41685
To: sip:61449082568@192.168.44.3;tag=45313239068d7168de0659f93f0137c1
Call-ID: f588507ff3c64fc5bed33710e960410d
CSeq: 26283 ACK
Route: sip:192.168.44.3;lr
Content-Length: 0

`
@soccertack
Copy link

I'm having the same issue. Any solution for it?

@soccertack
Copy link

soccertack commented Aug 31, 2018 •
edited
Loading

Something like this would make it work, at least for me.
https://pastebin.com/CYmitZSB

@twmobius twmobius mentioned this issue Oct 24, 2020
Open
@sobomax
Copy link
Member

sobomax commented Oct 26, 2020

@arvoshift @twmobius @arvoshift thanks folks, somehow I've overlooked it. I've reproduced the issue here, so fix is coming soon:

https://travis-ci.com/github/sippy/voiptests/jobs/407842818#L2369

sobomax added a commit that referenced this issue Oct 26, 2020
@sobomax
Fix regression with python2, now that content can be "unicode",
b5038e9 
not "str".

Issue: #30
sobomax added a commit that referenced this issue Oct 26, 2020
@sobomax
Fix regression with python2, now that content can be "unicode",
f1c375b 
not "str".

Issue:	#30
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sobomax @arvoshift @soccertack