[Spce-user] Some strange register requirements

[Serge Yuriev]

Hello,

One of our providers want us to construct REGISTER in way like this:

2015/05/21 00:12:04.878409 x.x.x.x:5060 -> y.y.y.y:5060
REGISTER sip:y.y.y.y SIP/2.0'
Via: SIP/2.0/UDP x.x.x.x;branch=z9hG4bKc346.c7a930b6a843cdc0e915b64b6a3922b0.0'
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKIF7QdaOq;rport=5080'
From: “auth-name” <sip:user-name at y.y.y.y>;tag=0E778EA1-555CF8A4000BB149-3F66F700'
To: “auth-name” <sip:user-name at x.y.y.y>'
CSeq: 51 REGISTER'
Call-ID: 77CDCF33-555CF8A4000BB167-3F770700'
Max-Forwards: 69'
Expires: 3600'
Authorization: Digest username=“auth-name", realm="SIP-REGISTRAR", nonce="504EADF5", uri="sip:y.y.y.y", response="c0f33835aacc3fbc7fe693865c54a103", algorithm=MD5'
Contact: <sip:user-name at x.x.x.x:5060;transport=udp>'
Content-Length: 0'

How we can achieve this?

-- 
Serge S. Yuriev