[Home]

Summary:ASTERISK-24654: Cant Register when extra data is added to Registers URI using PJSIP
Reporter:Allen Ford (cyford33)Labels:
Date Opened:2015-01-02 08:54:33.000-0600Date Closed:2015-01-15 15:38:42.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:pjproject/pjsip
Versions:12.1.0 13.1.0 Frequency of
Occurrence		Constant
Related
Issues:
is a clone ofASTERISK-24694 CLONE - Cant Register when extra data is added to Registers URI using PJSIP
Environment:centos 6.6 asterisk 13 freepbx 12 pjsips 2.2.1Attachments:( 0) pjsip-debug.txt
( 1) pjsip-trace.txt
Description:when trying to get Push notifications to work  our soft phones on the mobile device  sends uri like the following:
{noformat}
'0.0.0.4:12345:3600:3003:sip:3003@192.168.111.34:48574,rinstance=1d02f625bec01f51,transport=UDP,X-PUSH-URI=http://s.notify.live.net/u/1/bn1/HmQAAABIJvDa7TlcHYdOD8P8GKw5K14l7MmE_eS_NeuMzo4h-AF32Y-pf_8Ux0XF24N5AIY1fV3InvnglTNyjJlFRByH/d2luZG93c3Bob25lZGVmYXVsdA/EW_BnIu3fUOH7FePoWYHNw/mdWiTaGBmvmq8Bc6a1kHWu41kJ4
{noformat}
If i disable push and remove extra uri headers it registers fine, Also registers fine with chan_sip.
full debug log is here:  http://pastebin.com/raw.php?i=7e8Bm9Hi    (searching for X-PUSH-URI  would help see what i mean)

After recompiling Pjsips to disable strict registration i am sometime able to register with
{noformat}
0.0.0.4:12345:3600:3003:sip:3003@192.168.111.34:48574,rinstance=1d02f625bec01f51,transport=UDP,X-PUSH-URI
{noformat}
(somehow it cuts  the rest of the data off starting with =)

but when it doesn't cut the data off i get errors like this
{noformat}
[2015-01-02 14:41:55] ERROR[9487]: res_pjsip_registrar.c:504 rx_task: Unable to bind contact 'sip:3003@76.122.73.37:40300;rinstance=4e9e15dba6b67bf4;X-PUSH-URI=▒94' to AOR '3003'
[2015-01-02 14:41:55] WARNING[9487]: res_pjsip_pubsub.c:2858 pubsub_on_rx_publish_request: No registered publish handler for event presence
[2015-01-02 14:41:55] WARNING[9487]: res_pjsip_pubsub.c:608 subscription_get_handler_from_rdata: No registered subscribe handler for event presence.winfo

   -- Attempted to remove non-existent contact 'sip:3003@76.122.73.37:40300;rinstance=4e9e15dba6b67bf4;X-PUSH-URI=if' from AOR '3003' by request

{noformat}

Comments:By: Richard Mudgett (rmudgett) 2015-01-02 12:43:17.958-0600

Please attach log files as {{.txt}} files to the issue itself rather than linking them to a third party site.  Pastebin does not keep posts for very long.

Attach files using {{More --> Attach files}}
By: Allen Ford (cyford33) 2015-01-05 18:58:31.281-0600

Sorry file has been attached
By: Rusty Newton (rnewton) 2015-01-06 14:38:48.482-0600

Can you go ahead and test with pjsip 2.3 from http://www.pjsip.org/download.htm ?
By: Allen Ford (cyford33) 2015-01-06 15:09:08.832-0600

{noformat}
cd /usr/src
wget http://www.pjsip.org/release/2.3/pjproject-2.3.tar.bz2
tar -xjvf pjproject-2.3.tar.bz2
cdpjproject-2.3
CFLAGS='-DPJ_HAS_IPV6=1' ./configure --prefix=/usr --enable-shared --disable-sound\
 --disable-resample --disable-video --disable-opencore-amr --libdir=/usr/lib64
make dep
make
make install
{noformat}
___________________________________________________

{noformat}
   -- Added contact 'sip:3003@76.122.73.37:49320;rinstance=32ef8869166cacee' to AOR '3003' with expiration of 7200 seconds
   -- Unregistered SIP '3004'
   -- Removed contact 'sip:3003@76.122.73.37:49320;rinstance=32ef8869166cacee' from AOR '3003' due to request
   -- Added contact 'sip:3003@76.122.73.37:49320;rinstance=a94550d0f1513591' to AOR '3003' with expiration of 7200 seconds
[2015-01-06 21:01:51] WARNING[9053]: res_pjsip_pubsub.c:2858 pubsub_on_rx_publish_request: No registered publish handler for event presence
[2015-01-06 21:01:51] WARNING[9053]: res_pjsip_pubsub.c:608 subscription_get_handler_from_rdata: No registered subscribe handler for event presence.winfo
   -- Removed contact 'sip:3003@76.122.73.37:49320;rinstance=a94550d0f1513591' from AOR '3003' due to request
   -- Registered SIP '3004' at 76.122.73.37:49320
failed to extend from 256 to 371
   -- Added contact 'sip:3003@76.122.73.37:49320;rinstance=50642915820d2265;X-PUSH-URI=' to AOR '3003' with expiration of 7200 seconds
[2015-01-06 21:02:06] WARNING[9054]: res_pjsip_pubsub.c:2858 pubsub_on_rx_publish_request: No registered publish handler for event presence
[2015-01-06 21:02:06] WARNING[9054]: res_pjsip_pubsub.c:608 subscription_get_handler_from_rdata: No registered subscribe handler for event presence.winfo
   -- Attempted to remove non-existent contact 'sip:3003@76.122.73.37:49320;rinstance=50642915820d2265;X-PUSH-URI=' from AOR '3003' by request
{noformat}

______________________________________________________________

{noformat}
shutdown -r now
{noformat}
______________________________________________________________

{noformat}
   -- Added contact 'sip:3003@76.122.73.37:49320;rinstance=6373f168fb6f5fe9;X-PUSH-URI=' to AOR '3003' with expiration of 7200 seconds
[2015-01-06 21:07:40] WARNING[1748]: res_pjsip_pubsub.c:2858 pubsub_on_rx_publish_request: No registered publish handler for event presence
[2015-01-06 21:07:40] WARNING[1748]: res_pjsip_pubsub.c:608 subscription_get_handler_from_rdata: No registered subscribe handler for event presence.winfo
   -- Attempted to remove non-existent contact 'sip:3003@76.122.73.37:49320;rinstance=6373f168fb6f5fe9;X-PUSH-URI=' from AOR '3003' by request
   -- Added contact 'sip:3003@76.122.73.37:49320;rinstance=e5bfd96f7d2cfeb1;X-PUSH-URI=' to AOR '3003' with expiration of 7200 seconds
[2015-01-06 21:07:48] WARNING[1748]: res_pjsip_pubsub.c:2858 pubsub_on_rx_publish_request: No registered publish handler for event presence
[2015-01-06 21:07:48] WARNING[1748]: res_pjsip_pubsub.c:608 subscription_get_handler_from_rdata: No registered subscribe handler for event presence.winfo
[2015-01-06 21:07:54] WARNING[1774]: chan_sip.c:4047 retrans_pkt: Retransmission timeout reached on transmission 2839e0ea56cd18a3149450951af919c8@191.237.69.118:5061 for seqno 102 (Critical Request) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
Packet timed out after 32000ms with no response
{noformat}


By: Allen Ford (cyford33) 2015-01-10 19:23:27.965-0600

Rejection of registration was always intermittent but i do not see that now. however it is still cutting the actual url out.. i was told there may be a string limit on registration uri.. it should look like this

76.122.73.37:49320:3600:3004:sip:3004@76.122.73.37:49320;rinstance=ed8c3a6e0b6ff9eb;transport=UDP;X-PUSH-URI=http://s.notify.live.net/u/1/bn1/HmQAAAAnPaZLw5iXFKlswddMoQFYZeIgMq0tItShUKyvP8QfPWx-7wlyOLH38qv5e5WyHzDEex980OfLJIJHPCMK4jkG/d2luZG93c3Bob25lZGVmYXVsdA/EW_BnIu3fUOH7FePoWYHNw/mdWiTaGBmvmq8Bc6a1kHWu41kJ4

By: Matt Jordan (mjordan) 2015-01-12 09:43:58.513-0600

Why are you running {{chan_sip}} with {{chan_pjsip}}? Have you bound them to different ports?
By: Matt Jordan (mjordan) 2015-01-12 09:47:34.748-0600

Unfortunately, your log file was not generated correctly.

The error message is in the log file:

{noformat}
[2015-01-02 14:50:03] ERROR[9487]: res_pjsip_registrar.c:504 rx_task: Unable to bind contact 'sip:3004@76.122.73.37:50741;rinstance=be4082a6a865b7b8;X-PUSH-URI=�' to AOR '3004'
{noformat}

However, you had already turned off PJSIP logging by that point, so we don't have the capture of the {{REGISTER}} request that caused the problem.

Please capture in a DEBUG log file that REGISTER request, along with the resulting ERROR message.

You should probably make sure that {{chan_sip}} is disabled or at least listening on a different port than {{chan_pjsip}}, as that can cause interesting issues.
By: Allen Ford (cyford33) 2015-01-15 11:26:43.042-0600

here is a debug file,  i have used to re-register over an over with
pjsip set logger on
By: Allen Ford (cyford33) 2015-01-15 11:32:12.405-0600

I have attached the debug file.  and pjsip is port 5060 while sip_chan is port 5061...

I am able to register now,  and i see it in the sip request how ever it is not added to aor with X-PUSH-URI=
By: Matt Jordan (mjordan) 2015-01-15 15:38:34.258-0600

So, you cancelled PJSIP logging before actually getting the REGISTER request with the {{X-PUSH-URI}} in whatever header it was in.

{noformat}
[2015-01-02 14:50:03] DEBUG[15819]: pjsip:0 <?>:        tdta0x7f8da800 .Destroying txdata Response msg 401/REGISTER/cseq=2 (tdta0x7f8da8005280)
   -- Added contact 'sip:3003@76.122.73.37:50741;rinstance=9918078905ff9016;X-PUSH-URI=' to AOR '3003' with expiration of 7200 seconds
[2015-01-02 14:50:03] DEBUG[15819]: config.c:3501 ast_parse_arg: extract int from [60] in [0, 86400] gives [60](0)
{noformat}

That being said... this is a custom value being added to the header. I'm not sure what is special about it that PJSIP doesn't like - the log was once again truncated so we can't find that out - but even if it was there, it isn't going to be a bug. You're appending something custom. Asterisk isn't going to understand it. If you want Asterisk to support that header, that sound like an improvement or a feature request, not a bug.
By: Allen Ford (cyford33) 2015-01-15 16:11:31.751-0600

I think this was closed Prematurely ...  I am not asking asterisk to do anything special with it other than not cut it off.   It works with Sip_Chan,    it it is used for Push Notifications on mobile phones...  It is not my custom url it is what sip clients on mobile phones are using now.
 keeping this from getting cut off is making PJSIP channel not support WP 8.1  and maybe any other push notifications as well out there

Also the second logs uploaded today  pjsip set logger was not turned off before registration,  actually i registered many times in that debug file..  like 10 or more times

Plus i was directed to open a bug request by the leaders in the asterisk IRC
By: Matt Jordan (mjordan) 2015-01-15 19:41:40.333-0600

You were asked to open this issue by bug marshals in #asterisk (or any other IRC channel) because they couldn't determine what the problem was.

The problem is that Asterisk truncates your SIP URI in your Contact header when you append custom data to it. That's problematic for your implementation, but as a I said previously, that's not a bug. Asterisk doesn't support what your endpoint is doing. Changing that would be an improvement, but the fact that Asterisk's PJSIP channel driver doesn't support something that is custom to some other endpoint doesn't make it a bug. Nor is it a bug that {{chan_sip}} supports a longer string; that's merely a different implementation.

You are free to do any of the following:
# Provide a patch to the PJSIP stack. As an open source project, we'd be happy to have improvements made to it.
# Use {{chan_sip}} instead. While the focus of the project is on the PJSIP stack, you're more than welcome to use whatever is in Asterisk that works for you.

If you do provide a patch for this improvement, feel free to comment here and I'll be happy to reopen it. Please don't open more issues for this however - that makes bug marshal's lives more difficult, and - as I said elsewhere - wasting their time is not very nice.
By: Allen Ford (cyford33) 2015-01-15 21:39:47.589-0600

Ok,  this will be my first time even attempting to create a patch of any sort,   and it do hurt that i get no support in this matter until i can do so ,  but im not the giving up type..  ill take the challenge..  just need to learn a whole lot more now lol ,   something that may take me months can take someone an hour. And in the end im sure more an more people will request it..  i just wanted to be apart of the first to get it working.
But ill respond back if i can find a solution to this.
By: Allen Ford (cyford33) 2015-01-16 01:51:19.786-0600

after changing the transpor to tcp  ,  it looks like i get more data in form of blob..   however it does not add register to aor but still sends me a SIP/2.0 200 OK

<--- Received SIP request (1211 bytes) from UDP:76.122.73.37:47303 --->
REGISTER sip:191.237.65.201:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 76.122.73.37:47303;branch=z9hG4bK-d8754z-14f2a3e15e4e464e-1---d8754z-;rport
Max-Forwards: 70
Contact: <sip:3003@76.122.73.37:47303;rinstance=4ec4a0f4350268c6;transport=UDP;X-PUSH-URI=http://s.notify.live.net/u/1/bn1/HmQAAAATDCA5qF7w--acBUvAWKFDdybpUdixN8IklFWFbirVNTZJukGAxJw4l0pnwIorzlRB1jw_IIBBo9T80z0-1wPw/d2luZG93c3Bob25lZGVmYXVsdA/EW_BnIu3fUOH7FePoWYHNw/mdWiTaGBmvmq8Bc6a1kHWu41kJ4>
To: "3003"<sip:3003@191.237.65.201:5060;transport=UDP>
From: "3003"<sip:3003@191.237.65.201:5060;transport=UDP>;tag=47014e4f
Call-ID: MDI2MjJjMmY3ZmMwZGFkMDlhMmI5MTgzODc3YjQ5NDA.
CSeq: 3 REGISTER
Expires: 86400
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri
User-Agent: Zoiper r28204
Authorization: Digest username="3003",realm="asterisk",nonce="1421381084/eebc565fcf3bbee7040226fd24ad5434",uri="sip:191.237.65.201;transport=UDP",response="c10f71c5d4955fa1c84ddd3b85e8cdc4",cnonce="7c281e3ac7327be44a797107f58972d2",nc=00000002,qop=auth,algorithm=md5,opaque="39d117ff1c2adb7b"
Allow-Events: presence, kpml
Content-Length: 0


<--- Received SIP request (977 bytes) from TCP:76.122.73.37:52404 --->
PUBLISH sip:3003@191.237.65.201;transport=TCP SIP/2.0
Via: SIP/2.0/TCP 76.122.73.37:52404;branch=z9hG4bK-d8754z-c8abe7bec5d45cd9-1---d8754z-;rport
Max-Forwards: 70
Contact: <sip:3003@76.122.73.37:52404;transport=TCP>
To: "3003"<sip:3003@191.237.65.201;transport=TCP>
From: "3003"<sip:3003@191.237.65.201;transport=TCP>;tag=8175d274
Call-ID: NzM1ODA3ZjBkMTI3YzY4YjU3MjZhZjI4NTI3ZTE3Njc.
CSeq: 1 PUBLISH
Expires: 60
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
Content-Type: application/pidf+xml
Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri
User-Agent: Zoiper r28204
Event: presence
Allow-Events: presence, kpml
Content-Length: 262

<?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf"
         entity="sip:3003@191.237.65.201;transport=TCP">
 <tuple id="3003" >
    <status><basic>open</basic></status>
    <note>Online</note>
 </tuple>
</presence>
SUBSCRIBE sip:3003@191.237.65.201;transport=TCP SIP/2.0
Via: SIP/2.0/TCP 76.122.73.37:52404;branch=z9hG4bK-d8754z-62dc0eb431798193-1---d8754z-;rport
Max-Forwards: 70
Contact: <sip:3003@76.122.73.37:52404;transport=TCP>
To: "3003"<sip:3003@191.237.65.201;transport=TCP>
From: "3003"<sip:3003@191.237.65.201;transport=TCP>;tag=a93c4936
Call-ID: YTRkYjU5NDM5MTMwYmVhZmYwNWQzYjMxYzE5MzA3MTY.
CSeq: 1 SUBSCRIBE
Expires: 600
Accept: application/watcherinfo+xml
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri
User-Agent: Zoiper r28204
Event: presence.winfo
Allow-Events: presence, kpml
Content-Length: 0


<--- Transmitting SIP response (558 bytes) to TCP:76.122.73.37:52404 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/TCP 76.122.73.37:52404;rport=52404;received=76.122.73.37;branch=z9hG4bK-d8754z-c8abe7bec5d45cd9-1---d8754z-
Call-ID: NzM1ODA3ZjBkMTI3YzY4YjU3MjZhZjI4NTI3ZTE3Njc.
From: "3003" <sip:3003@191.237.65.201>;tag=8175d274
To: "3003" <sip:3003@191.237.65.201>;tag=z9hG4bK-d8754z-c8abe7bec5d45cd9-1---d8754z-
CSeq: 1 PUBLISH
WWW-Authenticate: Digest  realm="asterisk",nonce="1421393822/1a0e8a97eb38651fdf05ab18c6f0883d",opaque="3ba848a40f496b47",algorithm=md5,qop="auth"
Server: FPBX-12.0.25(13.1.0)
Content-Length:  0


<--- Received SIP request (725 bytes) from TCP:76.122.73.37:52404 --->
PUBLISH sip:3003@191.237.65.201;transport=TCP SIP/2.0
Via: SIP/2.0/TCP 76.122.73.37:52404;branch=z9hG4bK-d8754z-c8abe7bec5d45cd9-1---d8754z-;rport
Max-Forwards: 70
Contact: <sip:3003@76.122.73.37:52404;transport=TCP>
To: "3003"<sip:3003@191.237.65.201;transport=TCP>
From: "3003"<sip:3003@191.237.65.201;transport=TCP>;tag=8175d274
Call-ID: NzM1ODA3ZjBkMTI3YzY4YjU3MjZhZjI4NTI3ZTE3Njc.
CSeq: 1 PUBLISH
Expires: 60
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
Content-Type: application/pidf+xml
Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri
User-Agent: Zoiper r28204
Event: presence
Allow-Events: presence, kpml
Content-Length: 262

<?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf"
         entity="sip:3003@191.237.65.201;transport=TCP">
 <tuple id="3003" >
    <status><basic>open</basic></status>
    <note>Online</note>
 </tuple>
</presence>
SUBSCRIBE sip:3003@191.237.65.201;transport=TCP SIP/2.0
Via: SIP/2.0/TCP 76.122.73.37:52404;branch=z9hG4bK-d8754z-62dc0eb431798193-1---d8754z-;rport
Max-Forwards: 70
Contact: <sip:3003@76.122.73.37:52404;transport=TCP>
To: "3003"<sip:3003@191.237.65.201;transport=TCP>
From: "3003"<sip:3003@191.237.65.201;transport=TCP>;tag=a93c4936
Call-ID: YTRkYjU5NDM5MTMwYmVhZmYwNWQzYjMxYzE5MzA3MTY.
CSeq: 1 SUBSCRIBE
Expires: 600
Accept: application/watcherinfo+xml
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri
User-Agent: Zoiper r28204
Event: presence.winfo
Allow-Events: presence, kpml
Content-Length: 0


<--- Transmitting SIP response (560 bytes) to TCP:76.122.73.37:52404 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/TCP 76.122.73.37:52404;rport=52404;received=76.122.73.37;branch=z9hG4bK-d8754z-62dc0eb431798193-1---d8754z-
Call-ID: YTRkYjU5NDM5MTMwYmVhZmYwNWQzYjMxYzE5MzA3MTY.
From: "3003" <sip:3003@191.237.65.201>;tag=a93c4936
To: "3003" <sip:3003@191.237.65.201>;tag=z9hG4bK-d8754z-62dc0eb431798193-1---d8754z-
CSeq: 1 SUBSCRIBE
WWW-Authenticate: Digest  realm="asterisk",nonce="1421393822/1a0e8a97eb38651fdf05ab18c6f0883d",opaque="3c8d11405d1d6833",algorithm=md5,qop="auth"
Server: FPBX-12.0.25(13.1.0)
Content-Length:  0


<--- Received SIP request (1196 bytes) from TCP:76.122.73.37:52404 --->
REGISTER sip:191.237.65.201;transport=TCP SIP/2.0
Via: SIP/2.0/TCP 76.122.73.37:52404;branch=z9hG4bK-d8754z-eddccdf04f76f8f1-1---d8754z-;rport
Max-Forwards: 70
Contact: <sip:3003@76.122.73.37:52404;rinstance=3e6db54c4fe6cf2a;transport=TCP;X-PUSH-URI=http://s.notify.live.net/u/1/bn1/HmQAAAATDCA5qF7w--acBUvAWKFDdybpUdixN8IklFWFbirVNTZJukGAxJw4l0pnwIorzlRB1jw_IIBBo9T80z0-1wPw/d2luZG93c3Bob25lZGVmYXVsdA/EW_BnIu3fUOH7FePoWYHNw/mdWiTaGBmvmq8Bc6a1kHWu41kJ4>
To: "3003"<sip:3003@191.237.65.201;transport=TCP>
From: "3003"<sip:3003@191.237.65.201;transport=TCP>;tag=364fbc3a
Call-ID: MGQxYzYwMjQ4ZjEzMjAwZDAzYmYwOTE3NDk1ODFmZDU.
CSeq: 4 REGISTER
Expires: 86400
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri
User-Agent: Zoiper r28204
Authorization: Digest username="3003",realm="asterisk",nonce="1421393822/1a0e8a97eb38651fdf05ab18c6f0883d",uri="sip:191.237.65.201;transport=TCP",response="4599ff43e23d8c901987d31e16ab88d4",cnonce="bcaa8a5bb8f411d28d6213604ed6b592",nc=00000001,qop=auth,algorithm=md5,opaque="15b312297a0c81fc"
Allow-Events: presence, kpml
Content-Length: 0


[2015-01-16 07:37:02] ERROR[32886]: res_pjsip_registrar.c:504 rx_task: Unable to bind contact 'sip:3003@76.122.73.37:52404;transport=TCP;rinstance=3e6db54c4fe6cf2a;X-PUSH-URI=▒▒▒' to AOR '3003'
<--- Transmitting SIP response (439 bytes) to TCP:76.122.73.37:52404 --->
SIP/2.0 200 OK
Via: SIP/2.0/TCP 76.122.73.37:52404;rport=52404;received=76.122.73.37;branch=z9hG4bK-d8754z-eddccdf04f76f8f1-1---d8754z-
Call-ID: MGQxYzYwMjQ4ZjEzMjAwZDAzYmYwOTE3NDk1ODFmZDU.
From: "3003" <sip:3003@191.237.65.201>;tag=364fbc3a
To: "3003" <sip:3003@191.237.65.201>;tag=z9hG4bK-d8754z-eddccdf04f76f8f1-1---d8754z-
CSeq: 4 REGISTER
Date: Fri, 16 Jan 2015 07:37:02 GMT
Server: FPBX-12.0.25(13.1.0)
Content-Length:  0
By: Allen Ford (cyford33) 2015-01-16 09:34:46.814-0600

It actually seems that when installing pjsip 2.3  asterisk continoussly crashes.   earlier i had install pjsip 2.3 on the wrong server.

when i install pjsip 2.2  asterisk starts again..   i do have tcp enabled too