Pbx to Pbx .. issue v2.0.10 to 3.x

[Carl Johnson]

Pbx to Pbx we are having occasional issues that cause a fast busy. (IGNORE THE TIME DIFF, JUST THE DIFF IN LOG TIMEFRAMES)

 

** In the logs we are seeing this from the inititing side.

 

[9] 20080711170257: SIP Rx udp:192.168.40.101:5060:

SIP/2.0 500 Internal Server Error^M

Via: SIP/2.0/UDP 192.168.40.223:5060;branch=z9hG4bK-3ef7a6503ab575390a0d751789163028;rport^M

From: <sip:129@rcp.local>;tag=2978fafd1d^M

To: "Mike Bartholomew" <sip:129@rcp.local>;tag=EB61F973-117E0FA6^M

CSeq: 17957 NOTIFY^M

Call-ID: c77731ba-bdbff57d-eda0b710@192.168.40.101^M

Contact: <sip:129@192.168.40.101>^M

Event: dialog^M

User-Agent: PolycomSoundPointIP-SPIP_330-UA/2.2.2.0084^M

Content-Length: 0^M

 

[9] 20080711170257: SIP Rx udp:192.168.42.210:5060:

SIP/2.0 404 Not Found^M

Via: SIP/2.0/UDP 192.168.41.223:5060;branch=z9hG4bK-e63a0d74cb06515532654b055c7093a0;rport=5060^M

From: "Mike Bartholomew" <sip:129@rcp.local>;tag=1339920820^M

To: <sip:201@192.168.42.210;user=phone>;tag=f2c7ff55f1^M

Call-ID: b0bb6d18@pbx^M

CSeq: 31722 INVITE^M

Contact: <sip:201@192.168.42.210:5060>^M

Supported: 100rel, replaces, norefersub^M

Allow-Events: refer^M

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE^M

Accept: application/sdp^M

User-Agent: pbxnsip-PBX/3.0.0.2914^M

Content-Length: 0^M

 

** On the receving side we are getting.

 

6] 2008/07/11 18:34:07: Sending RTP for cfd3f4ff@pbx#43e834b4b2 to 192.168.41.223:57888

[5] 2008/07/11 18:34:07: Received incoming call without trunk information and user has not been found

[9] 2008/07/11 18:34:07: Resolve 2968215: aaaa udp 192.168.41.223 5060

[9] 2008/07/11 18:34:07: Resolve 2968215: a udp 192.168.41.223 5060

[9] 2008/07/11 18:34:07: Resolve 2968215: udp 192.168.41.223 5060

[7] 2008/07/11 18:34:07: SIP Tx udp:192.168.41.223:5060:

SIP/2.0 404 Not Found

Via: SIP/2.0/UDP 192.168.41.223:5060;branch=z9hG4bK-15edfc90358ac5d8fc15dcbf23546e46;rport=5060

From: "Mike Bartholomew" <sip:129@rcp.local>;tag=1942796874

To: <sip:201@192.168.42.210;user=phone>;tag=43e834b4b2

Call-ID: cfd3f4ff@pbx

CSeq: 14552 INVITE

Contact: <sip:201@192.168.42.210:5060>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: pbxnsip-PBX/3.0.0.2914

Content-Length: 0

[Vodia PBX]

[5] 2008/07/11 18:34:07: Received incoming call without trunk information and user has not been found

 

That smells like the problem. Could it be that DNS is instable and then the outbound proxy of the trunk is not clear? I guess you get the above log message only when it fails, but not when it works okay?

[Carl Johnson]

Wish the issue was that simple, but we are using IP address instead of hostnames on the trunks?

[Vodia PBX]

Wish the issue was that simple, but we are using IP address instead of hostnames on the trunks?

 

Also as outbound proxy?

 

If the IP config of the host changing during operations?

[Carl Johnson]

IP on the domain on proxy?

[Vodia PBX]

IP on the domain on proxy?

 

IP address on the outbound proxy. This makes sure you don't have a problem with DNS.

[Carl Johnson]

Oops, sorry for the confustion with the question mark .. we are using IP on Domain and Outbound Proxy.

[Vodia PBX]

Oops, sorry for the confustion with the question mark .. we are using IP on Domain and Outbound Proxy.

 

Well, but if the PBX cannot match the incoming request to a trunk then there is a problem. Remember that the outbound proxy is also the "inbound proxy" which helps the PBX to make a decision from what trunk the call comes from. There must be something wrong with the IP address where the request came from and the outbound proxy of that trunk.