Jump to content

Error: 400 Bad Request


penta s.r.l.
 Share

Recommended Posts

Could you help me to decode the error following this request to register?

Thank you.

 

[7] 2009/06/18 23:48:11: SIP Tx udp:83.211.227.21:5060:

REGISTER sip:voip.eutelia.it SIP/2.0

Via: SIP/2.0/UDP 192.168.xx.yy:5060;branch=z9hG4bK-8be9d4687e29492fe66a65a56eaba639;rport

From: "111222333" <sip:111222333@voip.eutelia.it>;tag=53223

To: "111222333" <sip:111222333@voip.eutelia.it>

Call-ID: bo8pfk8d@pbx

CSeq: 47528 REGISTER

Max-Forwards: 70

Contact: <sip:111222333@192.168.xx.yy:5060;transport=udp;line=d3d94468>;+sip.instance="<urn:uuid:290191a7-c420-4279-b874-d847a684834c>"

User-Agent: pbxnsip-PBX/3.3.0.3165

Authorization: Digest realm="voip.eutelia.it",nonce="4a392a5aea78754b2fea45340545c05306936a85",response="19b7a13e513d4ef2b41c81db67e62c97",username="111222333@83.211.227.21",uri="sip:voip.eutelia.it",qop=auth,nc=00001728,cnonce="49a6eb92",algorithm=MD5

Expires: 3600

Content-Length: 0

 

[7] 2009/06/18 23:48:11: SIP Rx udp:83.211.227.21:5060:

SIP/2.0 400 Bad Request

Via: SIP/2.0/UDP 192.168.xx.yy:5060;branch=z9hG4bK-8be9d4687e29492fe66a65a56eaba639;rport=5060;received=88.32.xx.yy

From: "111222333" <sip:111222333@voip.eutelia.it>;tag=53223

To: "111222333" <sip:111222333@voip.eutelia.it>;tag=d7cbdeb4f107ce82ed834cadd3d6dbb2.fcc2

Call-ID: bo8pfk8d@pbx

CSeq: 47528 REGISTER

Server: SPS EUT GW 01 (0.9.6 (i386/linux))

Content-Length: 0

Warning: 392 83.211.227.21:5060 "Noisy feedback tells: pid=3533 req_src_ip=88.32.xx.yy req_src_port=5060 in_uri=sip:voip.eutelia.it out_uri=sip:voip.eutelia.it via_cnt==1"

Link to comment
Share on other sites

Could you help me to decode the error following this request to register?

 

[...]

Authorization: Digest ...,nc=00001728,...

[...]

 

Not sure, but it seems that this is not the first request that the PBX sends to the provider.

 

I never heared about a server with the name "SPS EUT GW 01", maybe they have written their own little SIP software.

Link to comment
Share on other sites

Not sure, but it seems that this is not the first request that the PBX sends to the provider.

 

I never heared about a server with the name "SPS EUT GW 01", maybe they have written their own little SIP software.

 

The problem is that I can register to the provider using EyeBeam but not with pbxnsip. :)

Link to comment
Share on other sites

The problem is that I can register to the provider using EyeBeam but not with pbxnsip. :)

 

Well, that does not mean that the registrar is RFC compliant. I don't see why the REGISTER should be a Bad Request.

 

So far the pbxnsip trunk was able to register will all popular SIP providers. Maybe SPS EUT can tell what is bad in the register request... I don't see it.

Link to comment
Share on other sites

Well, that does not mean that the registrar is RFC compliant. I don't see why the REGISTER should be a Bad Request.

 

So far the pbxnsip trunk was able to register will all popular SIP providers. Maybe SPS EUT can tell what is bad in the register request... I don't see it.

Strangely enough, I've deleted the trunk and recreated it (using the same data) and now it works.. :)

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...