Quote:
Originally Posted by ricardojpereira
Thanks for the prompt answer.
Is it possible to supply me a snippet of the REGISTER message that Voxalot sends to the VSP....
|
Code:
REGISTER sip:sip.blueface.ie SIP/2.0..Via: SIP/2.0/UDP 85.17.19.194:5061;branch=z9hG4bK563a0c81;rport..From: <sip:J*****c
@sip.blueface.ie>;tag=as370807de..To: <sip:J*****c@sip.blueface.ie>..Call-ID: 4627589a1a0fe6b5702f52e9605971e6@85.17.19.1
94..CSeq: 370 REGISTER..User-Agent: voxaLot..Max-Forwards: 70..Authorization: Digest username="J*****c", realm="sip.bluef
ace.ie", algorithm=MD5, uri="sip:sip.blueface.ie", nonce="2127466425", response="f979d65********************05aa1", opaqu
e=""..Expires: 3600..Contact: <sip:xxxxxx@85.17.19.194:5061>..Event: registration..Content-Length: 0....
See the header field in bold above. This is for a REGISTER request sent to sip.blueface.ie and as you can see the
Contact header field is
Contact: <sip:xxxxxx@85.17.19.194:5061> which is meant to be where the VSP sends the inbound INVITE message.
BTW Blueface are an example of a VSP that does do this properly.
.
.