Cisco 7960 Ring Tone / Huntgroup Melody

[jlumby]

I have noticed that if you specify a specific ring tone on a Cisco 7960 (other than the default chirp) it will not be played when calling the extension from the inside, or outside of the office. However if the phone is part of a hunt group where the ring melody is set to none, then the ring tone you selected on the phone will play. I am guessing that the PBXnSIP is sending a specific ring melody to the phone and overriding the user's selection. Is there a way to stop the PBXnSIP from sending a specific melody to the phone without needing to have it ring through a hunt group that is specifically set not to send one?

[Vodia PBX]

Hmm. We can send either Alert-Info or Call-Info header, I don't recall how the Cisco 7960 likes it. BTW what version are you running?

[jlumby]

I am running 2.1.8

The Cisco is POS3-8-9-00

Here is the packet

 

No. Time Source Destination Protocol Info

15 1.467275 75.146.173.69 192.168.3.134 SIP/SDP Request: INVITE sip:211@192.168.3.134:5060;transport=udp, with session description

 

Frame 15 (979 bytes on wire, 979 bytes captured)

Arrival Time: May 2, 2008 16:11:18.720178000

[Time delta from previous captured frame: 0.008953000 seconds]

[Time delta from previous displayed frame: 0.008953000 seconds]

[Time since reference or first frame: 1.467275000 seconds]

Frame Number: 15

Frame Length: 979 bytes

Capture Length: 979 bytes

[Frame is marked: False]

[Protocols in frame: eth:ip:udp:sip:sdp]

[Coloring Rule Name: UDP]

[Coloring Rule String: udp]

Ethernet II, Src: SoyoComp_a3:b7:df (00:50:2c:a3:b7:df), Dst: Cisco_3d:de:64 (00:15:c6:3d:de:64)

Destination: Cisco_3d:de:64 (00:15:c6:3d:de:64)

Address: Cisco_3d:de:64 (00:15:c6:3d:de:64)

.... ...0 .... .... .... .... = IG bit: Individual address (unicast)

.... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)

Source: SoyoComp_a3:b7:df (00:50:2c:a3:b7:df)

Address: SoyoComp_a3:b7:df (00:50:2c:a3:b7:df)

.... ...0 .... .... .... .... = IG bit: Individual address (unicast)

.... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)

Type: IP (0x0800)

Internet Protocol, Src: 75.146.173.69 (75.146.173.69), Dst: 192.168.3.134 (192.168.3.134)

Version: 4

Header length: 20 bytes

Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)

0000 00.. = Differentiated Services Codepoint: Default (0x00)

.... ..0. = ECN-Capable Transport (ECT): 0

.... ...0 = ECN-CE: 0

Total Length: 965

Identification: 0x108d (4237)

Flags: 0x00

0... = Reserved bit: Not set

.0.. = Don't fragment: Not set

..0. = More fragments: Not set

Fragment offset: 0

Time to live: 128

Protocol: UDP (0x11)

Header checksum: 0x6995 [correct]

[Good: True]

[bad : False]

Source: 75.146.173.69 (75.146.173.69)

Destination: 192.168.3.134 (192.168.3.134)

User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)

Source port: sip (5060)

Destination port: sip (5060)

Length: 945

Checksum: 0x1b58 [correct]

[Good Checksum: True]

[bad Checksum: False]

Session Initiation Protocol

Request-Line: INVITE sip:211@192.168.3.134:5060;transport=udp SIP/2.0

Method: INVITE

[Resent Packet: False]

Message Header

Via: SIP/2.0/UDP 75.146.173.69:5060;branch=z9hG4bK-f4f5c3c6421d1bc173750b474eb7a674;rport

Transport: UDP

Sent-by Address: 75.146.173.69

Sent-by port: 5060

Branch: z9hG4bK-f4f5c3c6421d1bc173750b474eb7a674

RPort: rport

From: "210" <sip:210@voip.office.twincitytelephone.com>;tag=14907

SIP Display info: "210"

SIP from address: sip:210@voip.office.twincitytelephone.com

SIP tag: 14907

To: <sip:211@voip.office.twincitytelephone.com;user=phone>

SIP to address: sip:211@voip.office.twincitytelephone.com

Call-ID: 4258dfdb@pbx

CSeq: 18541 INVITE

Sequence Number: 18541

Method: INVITE

Max-Forwards: 70

Contact: <sip:211@75.146.173.69:5060;transport=udp>

Contact Binding: <sip:211@75.146.173.69:5060;transport=udp>

URI: <sip:211@75.146.173.69:5060;transport=udp>

SIP contact address: sip:211@75.146.173.69:5060

Supported: 100rel, replaces, norefersub

Allow-Events: refer

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

Accept: application/sdp

User-Agent: PBXnSIP-PBX/2.1.8.2463

Alert-Info: <http://127.0.0.1/Bellcore-dr2>

Content-Type: application/sdp

Content-Length: 265

Message Body

Session Description Protocol

Session Description Protocol Version (v): 0

Owner/Creator, Session Id (o): - 48598 48598 IN IP4 75.146.173.69

Owner Username: -

Session ID: 48598

Session Version: 48598

Owner Network Type: IN

Owner Address Type: IP4

Owner Address: 75.146.173.69

Session Name (s): -

Connection Information ©: IN IP4 75.146.173.69

Connection Network Type: IN

Connection Address Type: IP4

Connection Address: 75.146.173.69

Time Description, active time (t): 0 0

Session Start Time: 0

Session Stop Time: 0

Media Description, name and address (m): audio 50752 RTP/AVP 0 8 18 101

Media Type: audio

Media Port: 50752

Media Proto: RTP/AVP

Media Format: ITU-T G.711 PCMU

Media Format: ITU-T G.711 PCMA

Media Format: ITU-T G.729

Media Format: 101

Media Attribute (a): rtpmap:0 pcmu/8000

Media Attribute Fieldname: rtpmap

Media Format: 0

MIME Type: pcmu

Media Attribute (a): rtpmap:8 pcma/8000

Media Attribute Fieldname: rtpmap

Media Format: 8

MIME Type: pcma

Media Attribute (a): rtpmap:18 g729/8000

Media Attribute Fieldname: rtpmap

Media Format: 18

MIME Type: g729

Media Attribute (a): fmtp:18 annexb=no

Media Attribute Fieldname: fmtp

Media Format: 18 [g729]

Media format specific parameters: annexb=no

Media Attribute (a): rtpmap:101 telephone-event/8000

Media Attribute Fieldname: rtpmap

Media Format: 101

MIME Type: telephone-event

Media Attribute (a): fmtp:101 0-16

Media Attribute Fieldname: fmtp

Media Format: 101 [telephone-event]

Media format specific parameters: 0-16

Media Attribute (a): sendrecv

[Vodia PBX]

I am running 2.1.8

The Cisco is POS3-8-9-00

Here is the packet

 

Probably the Cisco did not like the http in the alert info. Can you give the attached ringback.xml a try? You need to restart the service for that or load it through the special web interface page (Reload Configuration Files in admin/configuration).

ringtones.xml