Jump to content

Receive PBXNSIP call not working in Communicator


Marcel V
 Share

Recommended Posts

I have sucessfully implemented the OCS connection in one direction (OCS -> PBXNSIP)

 

Now i can not get the direction PBXNSIP extension towards OCS to work.

 

It each time tells me it can not find a trunk ?? The OCS Gateway trunk is configured.

 

The logging shows me this:

 

[9] 2008/12/16 15:14:16: UDP: Opening socket on port 64050

[9] 2008/12/16 15:14:16: UDP: Opening socket on port 64051

[8] 2008/12/16 15:14:16: Could not find a trunk (2 trunks)

[8] 2008/12/16 15:14:16: Using outbound proxy sip:195.73.157.235:31268;transport=udp because UDP packet source did not match the via header

[9] 2008/12/16 15:14:16: Resolve 3120: udp 195.73.157.235 31268

[9] 2008/12/16 15:14:16: Resolve 3121: udp 195.73.157.235 31268

[8] 2008/12/16 15:14:17: Tagging request with existing tag

[6] 2008/12/16 15:14:17: Sending RTP for NWI3OWE1NmI5OTE1OWYxZTQ5MWM0ZTc2NWU3Yjc1NTY.#ed8b1b78e7 to 192.168.3.221:21376

[9] 2008/12/16 15:14:17: Resolve 3122: udp 195.73.157.235 31268

[7] 2008/12/16 15:14:17: Attendant: Calling extension 40

[8] 2008/12/16 15:14:17: Play audio_moh/noise.wav

[9] 2008/12/16 15:14:17: UDP: Opening socket on port 63544

[9] 2008/12/16 15:14:17: UDP: Opening socket on port 63545

[9] 2008/12/16 15:14:17: Resolve 3123: url sip:+31883382840@195.73.157.236;transport=tcp

[9] 2008/12/16 15:14:17: Resolve 3123: a tcp 195.73.157.236 5060

[9] 2008/12/16 15:14:17: Resolve 3123: tcp 195.73.157.236 5060

[9] 2008/12/16 15:14:17: UDP: Opening socket on port 58876

[9] 2008/12/16 15:14:17: UDP: Opening socket on port 58877

[9] 2008/12/16 15:14:17: Using outbound proxy sip:91.151.216.19:53282;transport=udp because of flow-label

[9] 2008/12/16 15:14:17: Resolve 3124: url sip:91.151.216.19:53282;transport=udp

[9] 2008/12/16 15:14:17: Resolve 3124: a udp 91.151.216.19 53282

[9] 2008/12/16 15:14:17: Resolve 3124: udp 91.151.216.19 53282

[8] 2008/12/16 15:14:17: Play audio_nl/ringback.wav

[9] 2008/12/16 15:14:17: Resolve 3125: udp 195.73.157.235 31268

[6] 2008/12/16 15:14:17: Sending RTP for NWI3OWE1NmI5OTE1OWYxZTQ5MWM0ZTc2NWU3Yjc1NTY.#ed8b1b78e7 to 195.73.157.235:21376

[9] 2008/12/16 15:14:20: Resolve 3126: udp 195.73.157.235 31268

[6] 2008/12/16 15:14:21: SIP TCP/TLS timeout on 195.73.157.236:5060, closing connection

[9] 2008/12/16 15:14:30: Resolve 3127: aaaa udp 91.151.216.19 53282

[9] 2008/12/16 15:14:30: Resolve 3127: a udp 91.151.216.19 53282

[9] 2008/12/16 15:14:30: Resolve 3127: udp 91.151.216.19 53282

[9] 2008/12/16 15:14:35: Resolve 3128: udp 195.73.157.235 61639

[9] 2008/12/16 15:14:35: Message repetition, packet dropped

[8] 2008/12/16 15:14:37: Attendant: Timeout (mailbox)

[9] 2008/12/16 15:14:37: Resolve 3129: tcp 195.73.157.236 5060

[8] 2008/12/16 15:14:37: Play audio_nl/aa_no_answer.wav space10 audio_nl/aa_receive_callback.wav audio_nl/aa_leave_message.wav space50

[9] 2008/12/16 15:14:37: Resolve 3130: udp 91.151.216.19 53282

[9] 2008/12/16 15:14:37: Resolve 3131: udp 195.73.157.235 31268

[7] 2008/12/16 15:14:37: Call 301e49a7@pbx#43757: Clear last request

[7] 2008/12/16 15:14:37: Call 301e49a7@pbx#43757: Clear last INVITE

[9] 2008/12/16 15:14:37: Resolve 3132: url sip:91.151.216.19:53282;transport=udp

[9] 2008/12/16 15:14:37: Resolve 3132: a udp 91.151.216.19 53282

[9] 2008/12/16 15:14:37: Resolve 3132: udp 91.151.216.19 53282

[5] 2008/12/16 15:14:37: INVITE Response: Terminate 301e49a7@pbx

[7] 2008/12/16 15:14:37: Other Ports: 2

[7] 2008/12/16 15:14:37: Call Port: 74c67bbc@pbx#62603

[7] 2008/12/16 15:14:37: Call Port: NWI3OWE1NmI5OTE1OWYxZTQ5MWM0ZTc2NWU3Yjc1NTY.#ed8b1b78e7

 

 

 

 

(Great document by the way)

Link to comment
Share on other sites

Hello Marcel,

 

did you following the guide in the pbxnsip-wiki? http://wiki.pbxnsip.com/index.php/Office_C...ications_Server

 

In your trace is a strange switch from tcp to udp. I can't see, whats causing this. Did you add a static registration with transport=tcp to your pbxnsip accounts?

 

btw: whats your pbxnsip version?

 

Best regards,

 

Jan

Link to comment
Share on other sites

Hello Marcel,

 

did you following the guide in the pbxnsip-wiki? http://wiki.pbxnsip.com/index.php/Office_C...ications_Server

 

In your trace is a strange switch from tcp to udp. I can't see, whats causing this. Did you add a static registration with transport=tcp to your pbxnsip accounts?

 

btw: whats your pbxnsip version?

 

Best regards,

 

Jan

 

HI Jan,

 

Yes i followed the ocs stuff. It works from OCS to an PBXNSIP extensie but not the other way around.

 

Yes i add an static registration with transport=tcp to my pbxnsip account

 

The version is: 3.0.1.3023 (Win32)

 

By now we suddenly can't even call from OCS to pbxnsip (this after i added one user with the same functionality ?)

 

I have to inform you we are using TLS towards the OCS clients

 

If there is anything you like me to try of log please let me know, any help is very appreciated.

 

Thanks,

Link to comment
Share on other sites

I have to inform you we are using TLS towards the OCS clients

 

AFAIK OCS is strict on the certificates in TLS. The PBX uses just a default certificate, and probably OCS does not like it. In order to get things working I would start with TCP first. Then if that works you can try using TLS and you might have to import a valid certificate (and the respective private key).

Link to comment
Share on other sites

AFAIK OCS is strict on the certificates in TLS. The PBX uses just a default certificate, and probably OCS does not like it. In order to get things working I would start with TCP first. Then if that works you can try using TLS and you might have to import a valid certificate (and the respective private key).

 

Ok we will try to start with TCP which is difficut for us due tohe fact we are testing with an external OCS hoster on TLS. I believe TCP is only allowed if internally used.

 

Another question:

 

When i call from OCS to an XLITE client the XLITE client rings, i pickup, XLITE tells me CALL Established but OCS tells me connecting call and that's it. No connection. Any feedback on this ?

Link to comment
Share on other sites

Ok we will try to start with TCP which is difficut for us due tohe fact we are testing with an external OCS hoster on TLS. I believe TCP is only allowed if internally used.

 

We have changed this to TCP and this is the result:

 

We do not have OCS ringing but this is the LOG:

 

[9] 2008/12/24 15:11:27: UDP: Opening socket on port 63522

[9] 2008/12/24 15:11:27: UDP: Opening socket on port 63523

[8] 2008/12/24 15:11:27: Could not find a trunk (2 trunks)

[9] 2008/12/24 15:11:27: Resolve 109085: aaaa udp 213.10.70.170 9448

[9] 2008/12/24 15:11:27: Resolve 109085: a udp 213.10.70.170 9448

[9] 2008/12/24 15:11:27: Resolve 109085: udp 213.10.70.170 9448

[9] 2008/12/24 15:11:27: Resolve 109086: aaaa udp 213.10.70.170 9448

[9] 2008/12/24 15:11:27: Resolve 109086: a udp 213.10.70.170 9448

[9] 2008/12/24 15:11:27: Resolve 109086: udp 213.10.70.170 9448

[8] 2008/12/24 15:11:27: Tagging request with existing tag

[6] 2008/12/24 15:11:27: Sending RTP for MjIwMGIxMzRhMzAxNzUwY2RkMzExMmUzNmY2ZDljMDI.#8dcfa04848 to 213.10.70.170:9452

[9] 2008/12/24 15:11:27: Resolve 109087: aaaa udp 213.10.70.170 9448

[9] 2008/12/24 15:11:27: Resolve 109087: a udp 213.10.70.170 9448

[9] 2008/12/24 15:11:27: Resolve 109087: udp 213.10.70.170 9448

[7] 2008/12/24 15:11:27: Attendant: Calling extension 40

[8] 2008/12/24 15:11:27: Play audio_moh/noise.wav

[9] 2008/12/24 15:11:27: UDP: Opening socket on port 60160

[9] 2008/12/24 15:11:27: UDP: Opening socket on port 60161

[9] 2008/12/24 15:11:27: Resolve 109088: url +31883382840@195.73.157.236;transport=tcp

[9] 2008/12/24 15:11:27: Resolve 109088: a tcp 195.73.157.236 5060

[9] 2008/12/24 15:11:27: Resolve 109088: tcp 195.73.157.236 5060

[9] 2008/12/24 15:11:27: UDP: Opening socket on port 49280

[9] 2008/12/24 15:11:27: UDP: Opening socket on port 49281

[9] 2008/12/24 15:11:27: Using outbound proxy sip:195.73.157.236:59435;transport=udp because of flow-label

[9] 2008/12/24 15:11:27: Resolve 109089: url sip:195.73.157.236:59435;transport=udp

[9] 2008/12/24 15:11:27: Resolve 109089: a udp 195.73.157.236 59435

[9] 2008/12/24 15:11:27: Resolve 109089: udp 195.73.157.236 59435

[8] 2008/12/24 15:11:27: Play audio_nl/ringback.wav

[9] 2008/12/24 15:11:27: Resolve 109090: aaaa udp 213.10.70.170 9448

[9] 2008/12/24 15:11:27: Resolve 109090: a udp 213.10.70.170 9448

[9] 2008/12/24 15:11:27: Resolve 109090: udp 213.10.70.170 9448

[3] 2008/12/24 15:11:40: Source address for sip:41@195.73.157.237 has changed to udp:213.10.70.170:9448

[9] 2008/12/24 15:11:40: Resolve 109091: aaaa udp 213.10.70.170 9448

[9] 2008/12/24 15:11:40: Resolve 109091: a udp 213.10.70.170 9448

[9] 2008/12/24 15:11:40: Resolve 109091: udp 213.10.70.170 9448

[9] 2008/12/24 15:11:41: Resolve 109092: udp 195.73.157.236 59431

[9] 2008/12/24 15:11:41: Message repetition, packet dropped

[6] 2008/12/24 15:11:41: SIP TCP/TLS timeout on 195.73.157.236:5060, closing connection

[8] 2008/12/24 15:11:47: Attendant: Timeout (mailbox)

[9] 2008/12/24 15:11:47: Resolve 109093: tcp 195.73.157.236 5060

[8] 2008/12/24 15:11:47: Play audio_nl/aa_no_answer.wav space10 audio_nl/aa_receive_callback.wav audio_nl/aa_leave_message.wav space50

[9] 2008/12/24 15:11:47: Resolve 109094: udp 195.73.157.236 59435

[9] 2008/12/24 15:11:47: Resolve 109095: aaaa udp 213.10.70.170 9448

[9] 2008/12/24 15:11:47: Resolve 109095: a udp 213.10.70.170 9448

[9] 2008/12/24 15:11:47: Resolve 109095: udp 213.10.70.170 9448

[7] 2008/12/24 15:11:47: Call 99780d33@pbx#17828: Clear last request

[7] 2008/12/24 15:11:47: Call 99780d33@pbx#17828: Clear last INVITE

[9] 2008/12/24 15:11:47: Resolve 109096: url sip:195.73.157.236:59435;transport=udp

[9] 2008/12/24 15:11:47: Resolve 109096: a udp 195.73.157.236 59435

[9] 2008/12/24 15:11:47: Resolve 109096: udp 195.73.157.236 59435

[5] 2008/12/24 15:11:47: INVITE Response: Terminate 99780d33@pbx

[7] 2008/12/24 15:11:47: Other Ports: 2

[7] 2008/12/24 15:11:47: Call Port: 2ae7d709@pbx#57535

[7] 2008/12/24 15:11:47: Call Port: MjIwMGIxMzRhMzAxNzUwY2RkMzExMmUzNmY2ZDljMDI.#8dcfa04848

[9] 2008/12/24 15:11:49: Resolve 109097: udp 195.73.157.236 59435

[5] 2008/12/24 15:11:55: Call 2ae7d709@pbx#57535: Last request not finished

[9] 2008/12/24 15:11:55: Resolve 109098: tcp 195.73.157.236 5060

[8] 2008/12/24 15:11:55: Hangup: Call 2ae7d709@pbx#57535 not found

[8] 2008/12/24 15:12:01: Play audio_nl/aa_no_answer.wav space10 audio_nl/aa_receive_callback.wav audio_nl/aa_leave_message.wav space50

[9] 2008/12/24 15:12:03: Resolve 109099: aaaa udp 213.10.70.170 9448

[9] 2008/12/24 15:12:03: Resolve 109099: a udp 213.10.70.170 9448

[9] 2008/12/24 15:12:03: Resolve 109099: udp 213.10.70.170 9448

[9] 2008/12/24 15:12:04: Resolve 109100: aaaa udp 213.10.70.170 9448

[9] 2008/12/24 15:12:04: Resolve 109100: a udp 213.10.70.170 9448

[9] 2008/12/24 15:12:04: Resolve 109100: udp 213.10.70.170 9448

[9] 2008/12/24 15:12:10: Resolve 109101: udp 195.73.157.236 59431

[9] 2008/12/24 15:12:10: Message repetition, packet dropped

[9] 2008/12/24 15:12:16: Resolve 109102: udp 195.73.157.236 59435

[6] 2008/12/24 15:12:19: SIP TCP/TLS timeout on 195.73.157.236:59459, closing connection

[3] 2008/12/24 15:12:31: Source address for sip:41@195.73.157.237 has changed to udp:213.10.70.170:9457

[9] 2008/12/24 15:12:31: Resolve 109103: aaaa udp 213.10.70.170 9457

[9] 2008/12/24 15:12:31: Resolve 109103: a udp 213.10.70.170 9457

[9] 2008/12/24 15:12:31: Resolve 109103: udp 213.10.70.170 9457

[9] 2008/12/24 15:12:39: Resolve 109104: udp 195.73.157.236 59431

[9] 2008/12/24 15:12:39: Message repetition, packet dropped

[9] 2008/12/24 15:12:40: Resolve 109105: udp 195.73.157.236 59435

Link to comment
Share on other sites

[3] 2008/12/24 15:12:31: Source address for sip:41@195.73.157.237 has changed to udp:213.10.70.170:9457

 

That might be a problem. Maybe that usse agent tries to be smart and there is a router in the path that does not support (too) smart devices. In other words, don't use STUN.

 

The TCP/TLS timeouts are probably okay, because the PBX initiates those connections and they are not kept alive with registrations.

Link to comment
Share on other sites

  • 1 month later...

Hi Marcel, :)

 

the OCS Enterprise Voice Integration has nothing to do with TLS or Certificates (regarding OCS 2007 R1, R2 is another special story).

 

In R1:

 

The connection between OCS Mediation Server and a Voip-PBX or VoIP gateway is Sip over TCP (no Certs no SSL) + Standard AudioCodecs (Mediation Server translates the MS RTA to e.g. G711)

 

Please do not change the OCS default TLS, SRTP security settings, especially for pbx integration tests. It is completly unnecessary !

 

You are using a OCS hoster. Please describe the details of the infrastructure! Where is the mediation server placed? At your location, next to pbxnsip on the same subnet???

 

For troubleshooting: please install Snooper from the OCS Resourcekit on your Mediation Server !

 

Best regards,

 

Jan

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...